XML to CSV Converter

What XML shape this xml to csv converter supports

This tool is built for the shape that actually shows up in the overwhelming majority of real XML data exports: a single root element containing a repeating list of record elements, where each record's own children are flat leaf elements holding text, for example a root named records containing several record elements, each with a plain id, name and email child.

That is deliberately not a general purpose XML to CSV converter for arbitrary document shapes. A record whose child element itself contains further nested children has its full text content flattened into a single cell rather than expanded into extra columns, since a table has no clean way to represent arbitrarily deep nesting. If your XML is more than two levels deep in a genuinely structural way, reshape it first or expect the deeper levels to collapse into one field.

• Supported: one root element wrapping a repeating list of record elements.
• Supported: flat leaf children inside each record, holding plain text.
• Supported: attributes on the record element, optionally as extra columns.
• Not supported without flattening: a record whose child element has its own nested children.

Converting xml records to csv columns

Each repeating element directly under the root becomes one CSV row, and the union of every child tag name seen across all of those elements becomes the column list, in the order each tag was first encountered. That means a record missing an optional field, such as a middle name only some entries have, still produces a complete table with an empty cell in that column rather than breaking the conversion.

A record's own attributes, if it has any, can be included as additional columns prefixed with an @ symbol, matching the same convention this site's XML to JSON converter uses, so an id attribute on a record element becomes an @id column alongside the columns built from its child elements.

How domparser xml parsing catches malformed documents

DOMParser has an unusual failure mode worth knowing about: it never throws a JavaScript exception for malformed XML. Instead of throwing, it silently returns a document whose contents are a parsererror element describing what went wrong. This converter checks for that element explicitly after every parse and surfaces its message as a readable error rather than producing an empty or corrupted CSV file.

The most common cause of a parse failure is a tag that is opened but never closed, since XML, unlike HTML, tolerates no unclosed tags at all, along with an ampersand or a less than sign appearing in text content without being written as the escaped entity & or <.

Delimiter and quoting for the exported CSV

Comma is the default output delimiter and the one almost every spreadsheet application expects, though semicolon, tab and pipe are available for tools and locales that use a different convention. A cell is quoted only when its own text actually requires it, meaning it contains the chosen delimiter, a double quote or a line break, which is the same minimal quoting convention RFC 4180 describes for CSV.

A literal double quote found inside an element's text is escaped by doubling it before being written into its cell, so a value containing a quoted term inside the original XML text survives the round trip into CSV without corrupting the column boundaries around it.

Turning an xml to spreadsheet workflow into a repeatable habit

Because DOMParser and the row building logic that walks its resulting document both run in the browser with no server involved, there is no daily limit and no upload size cap beyond what your device's memory can hold, so converting an xml to spreadsheet export you receive on a recurring basis costs nothing extra each time.

For a document that does not fit the repeating record shape this tool expects, converting it to JSON first with a general purpose XML to JSON converter and inspecting the resulting structure is often the fastest way to see how it should be reshaped before a tabular export makes sense.