How are attributes preserved?

As keys prefixed with `@`. ` a ` → `row: {"@id": "1", "#text": "a"}`.

What about multi-line text content?

YAML's `|` block literal preserves newlines faithfully. Long attribute values may stay inline; long element content uses block style.

Yes — element names keep their `prefix:tag` form in YAML. Consumers that care about namespaces can still route correctly.

The XML root becomes the top-level YAML key. Toggle 'strip root' to omit it when you know your consumer doesn't need the outer wrapper.

Convert XML to YAML format. Part of the DevTools Surf developer suite. Browse more tools in the Converters collection.

XML and YAML represent the same data model (trees) but with opposite verbosity: XML is explicit while YAML relies on whitespace.
Converting XML to YAML is common in Kubernetes migrations, where legacy XML configs are replaced with YAML manifests.
YAML's lack of attribute syntax means XML attributes must be converted to regular key-value pairs during transformation.

How are attributes preserved?: As keys prefixed with `@`. `<row id="1">a</row>` → `row: {"@id": "1", "#text": "a"}`.
What about multi-line text content?: YAML's `|` block literal preserves newlines faithfully. Long attribute values may stay inline; long element content uses block style.
Does namespace prefix information survive?: Yes — element names keep their `prefix:tag` form in YAML. Consumers that care about namespaces can still route correctly.
Can I control the root element?: The XML root becomes the top-level YAML key. Toggle 'strip root' to omit it when you know your consumer doesn't need the outer wrapper.

Convert XML to YAML format. Part of the DevTools Surf developer suite. Browse more tools in the Converters collection.

XML and YAML represent the same data model (trees) but with opposite verbosity: XML is explicit while YAML relies on whitespace.
Converting XML to YAML is common in Kubernetes migrations, where legacy XML configs are replaced with YAML manifests.
YAML's lack of attribute syntax means XML attributes must be converted to regular key-value pairs during transformation.

How are attributes preserved?: As keys prefixed with `@`. `<row id="1">a</row>` → `row: {"@id": "1", "#text": "a"}`.
What about multi-line text content?: YAML's `|` block literal preserves newlines faithfully. Long attribute values may stay inline; long element content uses block style.
Does namespace prefix information survive?: Yes — element names keep their `prefix:tag` form in YAML. Consumers that care about namespaces can still route correctly.
Can I control the root element?: The XML root becomes the top-level YAML key. Toggle 'strip root' to omit it when you know your consumer doesn't need the outer wrapper.