How are attributes represented?

By default attributes are prefixed (commonly with @) and placed in the same mapping as the element's child elements and text content.

Are namespaces preserved?

Namespace prefixes stay attached to element names. Resolving them to full URIs is not done automatically, which keeps the output reversible.

Is my XML sent to a server?

No. The conversion runs in the browser and the input is not transmitted.

What if an element has both text and children?

Mixed content is captured under a dedicated key (such as #text) so the children remain accessible as sibling fields.

xml → yaml · js-yaml · nested · arrays · live

Convert XML to YAML

Walk any XML document and emit equivalent YAML. Repeated tags collapse into arrays automatically. Runs locally in your browser.

XML → YAML

Input

98 B

6 lines

Output

0 B

1 lines

Status

parser…

Ratio

0.00×

out/in

input · xml

output · yaml

Loading parser…

Quick Start

How XML maps to YAML

The tool walks the XML tree: leaf elements become string values, parents become objects, and repeated sibling tags collapse into arrays.

01
Paste XML
Any well-formed XML document with elements you want as YAML keys.
Parsing runs through Prettier’s standalone bundle (or the language-specific equivalent) loaded lazily — no parser ships until the tool is opened.
inputPrettierASTstandalonelazy
input · sourcexml · AST
```
<book><title>Hi</title></book>
```
loaded · parsedAST · ready
02
Tree walk
Each child element becomes a key under its parent.
Indent width, tab style, and print-width re-format through a memoised pass — switching 2 → 4 spaces never re-parses, only re-prints.
treeindentprint-widthmemoisedlive
children · optionskeys · live
```
book:
  title: Hi
```
options applied · livelive
03
Repeated tags
Sibling tags with the same name collapse into a YAML array.
The formatter is deterministic and idempotent: running it twice produces byte-identical output, which keeps diffs and git noise to a minimum.
arraysidempotentdeterministicdiff-cleanstable
<tag>x2 · formattedlist · ready
```
tag:
  - fiction
  - short
```
formatted · liveidempotent
04
Copy or download
Use the YAML directly in config or hand off to a colleague.
Download writes a Blob with the language-appropriate extension; copy uses navigator.clipboard.writeText so the output preserves all whitespace exactly.
exportclipboardbloblanguage MIMEclient-side
✓ · copiedready · done
```
✓ Copied
```
shipped · ready to shipsuccess

Pro tips

Formatting tips that keep diffs sane

Pick one config and pin it

Inconsistent formatting causes diff churn. Commit .prettierrc / .editorconfig and enforce in CI.

Format on save

Editor integration is faster feedback than a pre-commit hook. Use both for belt-and-braces.

Idempotency matters

Running the formatter twice should produce identical output. Test this on a representative file.

Match the language community

Default to community conventions: 2 spaces for JS/CSS, 4 for Python, tabs for Go. Fights over indent are a productivity tax.

Print-width drives wrapping

80, 100, and 120 are the common targets. Wider lines parse fast but review slower side-by-side.

Don’t mix formatters and linters

Prettier handles whitespace; ESLint handles correctness. Disable overlapping rules to avoid fight-club configs.

Use Cases

When to convert XML to YAML

Legacy data, config migration, readability.

Legacy migration

Move old XML configs to readable YAML. Idempotent: running the formatter twice produces byte-identical output, which is the foundation of a clean CI gate. Pair with a pre-commit hook so PRs arrive already formatted, focusing review on logic.

idempotent

API responses

Inspect verbose XML feeds in concise YAML form. Pairs with EditorConfig + .prettierrc for end-to-end consistency. Whitespace-only changes vanish so reviewers see real diffs, and git blame stays honest about who wrote what.

CI-ready

Documentation

Embed sample data in docs without XML noise. Output respects your indent width, tab style, and print-width — settings carry over for repeat runs. Switching 2-space to 4-space costs nothing in CPU but standardises an entire codebase.

diff-clean

Tests

Define test fixtures in YAML from XML sources. Format-on-save is the fastest feedback loop; CI is the safety net. Together they make inconsistent indentation a thing of the past and free up review cycles for genuine concerns.

PR-friendly

CI configs

Convert old build XML into modern YAML pipelines. Whitespace-only changes don't trigger downstream content-hash invalidations, so CDN cache keys and CI cache layers stay warm. Real changes get all the rebuild budget.

review-ready

K8s manifests

Translate XML inventories into YAML manifests. Pairs with linters (ESLint, Stylelint, pylint) that catch what formatting alone can't — bugs, unused imports, dead code. Each tool stays in its lane, and the codebase stays clean.

k8s

FAQ

Frequently asked questions

Are attributes converted?

Currently only element text is read. Attribute-only data needs a pre-processing step.

Are namespaces kept?

Tag names include any prefix you used (e.g., ns:tag), but YAML doesn't carry namespace metadata.

What if my XML has CDATA?

CDATA text is read as plain string content.

Empty elements?

Render as empty strings in YAML — change to nulls in your follow-up step if needed.

Is anything sent to a server?

No. Parsing and YAML dump run locally in your browser.

Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

47 in queue·8 shipped this month

Request queued. Thanks!