Convert XML to Excel
Upload a .xml file and get back a Excel 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 Excel
Generated from the converter's own Excel type mapping — this is what it actually emits, not an example.
| Your data | Excel type |
|---|---|
| Whole number | number |
| Decimal (money) | number |
| Floating point | number |
| True / false | boolean |
| Date | date |
| Date and time | date |
| Short text | text |
| Long text | text |
| Binary data | hex text |
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.
What opens the converted workbook
Choosing Excel as the target puts no copy of Excel anywhere in the process: the workbook is assembled on the server by a library and handed over finished. What that library writes is what decides how the result behaves when you open it.
- →The output is .xlsx, the OOXML format, and only that. There is no .xls option, so a machine that can open nothing newer than Excel 97-2003 needs the CSV target and a save from there instead.
- →Values are the only thing written. No formulas, no macros, no charts, no column widths, no frozen header row - which is why the first thing most people do with it is widen a column. If Excel opens it in Protected View, that is the mark of the web on a downloaded file rather than anything in the workbook.
- →A conversion is capped at a million rows across all of its tables, and a worksheet holds 1,048,576, so no table can ever arrive too tall for the sheet it is being written into.
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 Excel
- →One file per table. Booleans stay booleans and numbers stay numbers.
- →Excel has no fixed-point type, so decimals become numbers — use a database target if exactness matters.
What you get
A ZIP containing <table>.xlsx. If anything about your data needed a judgement call, a _warnings.txt explains it.
Questions
- Is converting XML to Excel 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 Excel?
- Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real Excel 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.