Input (YAML)
user:
id: 1
name: Ada
roles:
- admin
- authorThe YAML ↔ XML converter transforms data between YAML and XML in either direction. Mapping keys become element names, sequences become repeated elements, and nested structures translate into nested markup; converting back reverses the process. This is handy when a human-friendly YAML config must feed a system that only accepts XML, or when you want to read an XML document in the more readable YAML form.
YAML is an indentation-based, human-readable data serialization format that supports mappings, sequences, scalars, and comments, and it is a superset of JSON. XML is a tag-based markup language built from nested elements, attributes, and a single root. Both can express hierarchical data, but their syntaxes differ greatly; the converter bridges YAML's whitespace structure and XML's explicit tags so the same data can live in either world.
The main file is the entry point for each run.
Use the Input panel to pipe standard input to your program when it needs data.
Run sends your code to a fresh hosted runtime and streams the result into the output panel.
Your draft stays in this browser, and Share creates a separate snapshot link.
user:
id: 1
name: Ada
roles:
- admin
- author<user>
<id>1</id>
<name>Ada</name>
<roles>admin</roles>
<roles>author</roles>
</user><book>
<title>SQL</title>
<pages>120</pages>
</book>book:
title: SQL
pages: "120"order:
id: 7
customer:
name: Ada<order>
<id>7</id>
<customer>
<name>Ada</name>
</customer>
</order><list>
<item>a</item>
<item>b</item>
</list>list:
item:
- a
- bconfig:
enabled: true
retries: 3<config>
<enabled>true</enabled>
<retries>3</retries>
</config>note:
text: a & b < c<note>
<text>a & b < c</text>
</note><team>
<member><name>Ada</name></member>
<member><name>Linus</name></member>
</team>team:
member:
- name: Ada
- name: LinusThe editor uses Monaco, the engine behind VS Code, with language-aware editing tools and familiar keyboard controls.
Paste YAML to produce nested XML markup, or paste XML to read it as YAML.
Mapping keys become element names and sequences become repeated elements.
Nested YAML structures translate into nested XML and back again.
YAML's indentation hierarchy maps to XML's explicit nested tags.
Sequence items become repeated sibling elements since XML lacks a list type.
A single root element wraps the document as XML requires.
Feeding a human-friendly YAML config into a system that only accepts XML.
Viewing a dense XML document in the more readable YAML form.
Both directions run in your browser — config data is never transmitted.
Paste sensitive YAML settings without them leaving the page.
Output
XML output