XML to CSV Converter

The XML to CSV Converter is for one common situation: you have XML records and you need them as spreadsheet rows. That covers a developer pulling a sample API response or export into a table for review, an analyst loading an XML feed of orders, products or contacts into Excel or a database staging table, and an admin who received an XML export from an older system and needs columns they can read.

Because everything runs in your browser, it is also a reasonable choice for data you would rather not upload anywhere: internal exports, draft records, anything mid-pipeline. The file is parsed locally, and nothing persists once the tab is closed.

Paste XML, open an .xml file or drop one on the input, then run it. The document is parsed strictly, so a missing end tag, a bare & or a second root element stops the run with the line, the column and the reason instead of a partial table.

The converter then looks for the record: the element that repeats most often directly under the root. Each record becomes a row. Its attributes become columns such as @id, its simple child elements become columns named after them, and deeper fields are named by their path, such as address.city. When a field repeats inside one record, the extra values get numbered columns (tag, tag_2) rather than being merged.

Standard CSV escaping is applied: values containing commas, quotes or line breaks are wrapped in double quotes with embedded quotes doubled, so the file opens cleanly in any spreadsheet. If the XML has no repeating element, the whole document becomes one row.

Records that differ in shape produce sparse columns. If one <order> has a <coupon> and the others do not, there is a coupon column that is empty for most rows, which is correct but worth recognising.

Very deep XML gives long path-named columns. That keeps every value, but if you only need a few fields, delete the other columns in your spreadsheet rather than trying to reshape the XML.

Every value comes across as text. A spreadsheet may reinterpret numbers, dates and identifiers when it opens the file, so a code like 00123 can lose its zeros on import unless you mark that column as text.

Compare the row count with the number of records in the XML, and confirm the headers match the fields you expected, including any attributes you know carry data.

Scan for numbered columns such as tag_2: they show where a field repeated inside a record, which may mean the XML holds a list you want as separate rows.

For anything official or financial (invoices, statements, accounting or regulatory records), treat the CSV as a working copy and verify key fields and totals against the original XML.