Convert XML to Markdown
Convert XML to Markdown in your browser: load your XML, choose Markdown as the target, and download the result. The converter reports exactly what it could not carry across, and nothing is uploaded to a server.
Convert XML to MarkdownRuns in your browser. Nothing uploaded.
When you need this
Getting an XML payload into a document, a ticket or a code review, where the reason for showing it is that a person has to read it. Also a fast way to eyeball whether a feed contains what you expect.
How to convert XML to Markdown
- Load your XML
- Drag the .xml file in, or paste the document. A response captured from a SOAP or REST endpoint can go straight in as text. Nothing leaves your browser at this or any later step.
- Choose the target format
- Press Ctrl+Shift+K (Cmd+Shift+K on a Mac) to open the conversion panel, then pick Markdown as the target. The source and the result sit side by side.
- Read the loss report
- The panel shows whether the conversion is lossless for your particular data, and lists every value it had to transform. Adjust indentation, key sorting and null handling if you need to.
- Take the Markdown
- Download the .md file, copy it, or open it as a new tab to keep working on it in the Markdown views.
What survives the conversion
XML to Markdown cannot be lossless, because the two formats express different things. Produces a table for a flat list of repeated elements.
- A flat list of repeated elements becomes a table. Other documents become a fenced code block, which is more honest than a table with one column per level of nesting.
- Attribute columns keep their
@_prefix, which is correct but ugly in a document — rename the headers by hand if the table is going somewhere public. - Pipes inside text values are escaped so the table structure holds.
- A single repeated element is not a list. One
<item>parses as an object rather than an array, so a one-row document comes out as a fenced code block instead of a table.
A worked example
A feed as a readable table:
<items>
<item><sku>A1</sku><qty>2</qty></item>
</items>```json
{
"items": {
"item": {
"sku": "A1",
"qty": 2
}
}
}
```Privacy
The conversion runs in your browser — in a Web Worker for anything above a quarter of a megabyte, so the page stays responsive. Your data is not uploaded, not logged and not stored. There is no account, and the whole thing works offline.
Questions
Can I get rid of the @_ prefixes in the headers?
Not automatically — the prefix is what records that a value came from an attribute rather than an element, and dropping it in the converter would make two different things look identical. In a document it is safe to rename the header by hand, because nothing is going to parse it back.
Is converting XML to Markdown lossless?
No, and no tool can make it so. Produces a table for a flat list of repeated elements. The converter lists every affected value rather than silently dropping it.
Is my XML uploaded to a server?
No. The file is read and converted by your browser. Nothing about its contents is sent anywhere, which you can verify in your browser’s network panel or by using the tool with the network disconnected.