Convert XML to CSV
Upload a .xml file and get back a CSV file. Types are preserved rather than flattened to text. Free, no registration, up to 10MB.
Click to upload or drag and drop
CSV, Excel, SQLite, SQL, DBF (max 10 MB)
How your data is typed in CSV
Generated from the converter's own CSV type mapping — this is what it actually emits, not an example.
| Your data | CSV type |
|---|---|
| Whole number | text (CSV has no types) |
| Decimal (money) | text (CSV has no types) |
| Floating point | text (CSV has no types) |
| True / false | text (CSV has no types) |
| Date | text (CSV has no types) |
| Date and time | text (CSV has no types) |
| Short text | text (CSV has no types) |
| Long text | text (CSV has no types) |
| Binary data | text (CSV has no types) |
Working from an .xml file
XML describes structure but not types, and nests arbitrarily deep, while a table does neither. The reader takes one specific slice of the document, and it is worth checking that the slice is the one you meant.
- →Only the direct children of the row element become columns. A grandchild such as <address><city> has no text of its own at that level, so it arrives as NULL - flatten one level before uploading.
- →Namespaces are reduced to local names, so <ns:order> and <order> are the same element here, and two elements differing only by prefix collide into one column.
- →Attributes are read first and child elements second, so where a row carries both an id attribute and an <id> child, the child's value is what lands in the column.
- →No XSD or DTD is consulted. Every value goes through the same inference a CSV gets, with the same refusal to guess at an ambiguous date.
The shape of the CSV files you get
CSV is where the type information stops, so what is left to describe is the file itself: how a row is terminated, which fields are quoted, and how a value that used to have a type is spelled out as characters.
- →Rows end with a carriage return and a line feed, the RFC 4180 ending, while a newline inside a quoted field stays the single character it always was. The encoding is UTF-8 with no byte-order mark in front of it.
- →Quotes go on only where they are needed - a field holding a comma, a double quote or a newline - and a quote inside a field is doubled rather than escaped with a backslash. Every other field is written bare.
- →Decimal values are written digit for digit and never through a floating-point number, so a money column that was exact in the source is still exact in the file. Booleans are written lower case, as true and false, which is the spelling this converter's own reader takes back as a boolean.
Reading XML
- →The row element is whichever child repeats — no configuration needed.
- →Attributes become columns alongside child elements, so nothing on the row itself is left behind. What a table cannot hold is depth: only the row element and its immediate children are read, so nested structures need flattening by one level first.
- →Empty and self-closing elements become NULL.
Writing CSV
- →One file per table, with a header row.
- →NULL is written as an empty field, never the word "None".
- →Binary data is written as hex, which is reversible.
What you get
A ZIP containing <table>.csv. If anything about your data needed a judgement call, a _warnings.txt explains it.
Questions
- Is converting XML to CSV free?
- Yes. Files up to 10MB convert free with no account. There is a limit of five conversions per day per IP address.
- Will my XML data keep its types in CSV?
- Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real CSV types rather than everything becoming text. The mapping table above shows exactly what you get.
- Do you store my file?
- No. The file is written to a temporary directory, converted, and the directory is deleted as soon as your download has been sent.