How does it decide which element repeats?

By default it picks the most common direct child of the root. You can override the row element with an XPath-style selector when the structure is deeper.

What if elements have different child sets?

Columns are the union of all encountered child or attribute names. Missing values produce empty cells so every row keeps a stable column count.

Is my XML sent anywhere?

No. The conversion is browser-local.

Are attributes included as columns?

Yes, optionally. Attribute columns can be prefixed (for example @id) to distinguish them from child elements with the same name.

xml → csv · rows · headers · live · local

Flatten XML rows to CSV

Take a simple XML document with rows of children and pull the data into CSV. Headers come from the union of child element names. Runs in your browser.

XML → CSV

Input

147 B

5 lines

Output

0 B

1 lines

Status

error

see panel

Ratio

0.00×

out/in

input · xml rows

output · csv

ErrorDOMParser is not defined

Quick Start

How XML rows become CSV

The tool reads the root element's direct children as rows, and each row's child elements as columns. Missing fields become empty cells.

01
Paste XML
Document with a root holding repeated <row>-style elements.
Parsing is strict-but-tolerant — comments and trailing commas are accepted on input where the source format historically permits them; output stays canonical.
inputstricttolerantliveparse
input · sourcexml · live
```
<rows><row>…</row></rows>
```
loaded · parsedtarget · ready
02
Headers detected
Union of every child tag becomes the header row.
Conversion preserves type information where the target supports it (numbers stay numeric, booleans stay boolean) so the destination parser never has to re-coerce.
headerstype-preservinglosslesslivememoised
headers · optionsauto · live
```
name,age
```
options applied · liveround-trip
03
Cells filled
Text content of each child fills the cell — missing ones are blank.
Re-encoding is idempotent: running output back through the same converter produces the same bytes, which keeps round-trips git-friendly.
cellsidempotentround-tripdiff-cleandeterministic
rows · convertedout · ready
```
Alice,30
Bob,25
```
converted · livediff-clean
04
Copy or download
Drop the CSV into Excel, Sheets, or a CSV importer.
Copy writes via navigator.clipboard.writeText; downloads use the target’s native MIME so editors apply the right syntax highlighting on open.
exportclipboardtarget MIMEblobclient-side
✓ · copiedready · done
```
✓ Copied
```
shipped · ready to shipsuccess

Pro tips

Converting between formats, safely

Pick the strictest source format

Lossy formats hide bugs. Choose JSON or YAML as your source-of-truth, convert downstream as needed.

Round-trip in CI

If your converter is idempotent, your CI can verify A → B → A equals the original. Catches subtle data loss.

Numbers vs strings differ

YAML/TOML have a number type; CSV doesn’t. Quote IDs in CSV to keep leading-zero values intact.

Watch character encoding

Source format may be Latin-1 / Windows-1252; target should be UTF-8. Convert encoding before structure.

Preserve comments where you can

YAML and TOML support comments. Don’t silently drop them — they often encode intent.

Schema-aware beats blind

Use a schema to guide conversion. Field types, required-ness, and defaults survive better with structure.

Use Cases

When to convert XML to CSV

Reporting, spreadsheets, legacy XML feeds.

Legacy feeds

Turn legacy XML data feeds into spreadsheets. Type information survives: numbers stay numeric, booleans stay boolean, strings stay strings. The destination parser doesn't have to re-coerce, which avoids the "'true' becomes "true"" bug class.

round-trip safe

Reports

Drop into Excel for ad-hoc analysis. Run output back through the inverse converter to verify idempotent round-trips in CI. A → B → A should produce byte-identical input — if it doesn't, you've found data loss.

type-preserving

ETL pipelines

Stage as CSV before loading into a warehouse. Comments and metadata survive where the target format supports them (YAML, TOML, HCL). The tool doesn't silently drop intent-encoded annotations, which keeps your config self-documenting.

schema-aware

DB import

Many DB tools have a CSV importer but no XML one. Pair with a schema (JSON Schema, OpenAPI, Zod, Pydantic) to catch shape drift on either side. Catch breaking changes at conversion time rather than at runtime in production.

lossless

Quick scan

Diff structured XML data with familiar columns. Output respects target-format conventions: quoting in CSV, indent in YAML, brackets in JSON. Existing parsers don't need patches, and the result drops into legacy pipelines unchanged.

diff-clean

Sharing

Send a CSV to non-technical teammates. Encoding-aware: handles UTF-8 vs UTF-16 vs Latin-1 / Windows-1252 transparently. The character-set surprise that breaks "works on my machine" doesn't apply here.

spec-grade

FAQ

Frequently asked questions

What XML shapes are supported?

Flat row-style documents: a root with repeated record children. Deeply nested structures are flattened to one level.

What about attributes?

Currently only element text is read. Attribute-based formats need pre-processing.

How are commas in values handled?

Quoted CSV per RFC 4180 — values with commas, quotes, or newlines are wrapped in double quotes.

Large files?

Browser memory limits — typically megabytes work fine, GB-sized inputs do not.

Is anything sent to a server?

No. Parsing runs entirely 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!