Convert XML to DuckDB
Upload a .xml file and get back a DuckDB 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 DuckDB
Generated from the converter's own DuckDB type mapping — this is what it actually emits, not an example.
| Your data | DuckDB type |
|---|---|
| Whole number | BIGINT |
| Decimal (money) | DECIMAL(10,2) |
| Floating point | DOUBLE |
| True / false | BOOLEAN |
| Date | DATE |
| Date and time | TIMESTAMP |
| Short text | VARCHAR |
| Long text | VARCHAR |
| Binary data | BLOB |
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.
Decimals and text in the .duckdb file
DuckDB takes the source's declared types more nearly unchanged than any other target here, which makes the two places where it cannot the things worth reading: the width of a decimal, and the length of a string.
- →DECIMAL tops out at 38 digits, so a wider source column is clamped rather than refused: an Oracle NUMBER(50,10) is created here as DECIMAL(38,10), and the scale is never allowed to grow past the precision holding it.
- →A decimal that declared no scale gets six places for its fraction rather than none, inside that same rule: a source precision of 10 becomes DECIMAL(10,6), one of 5 becomes DECIMAL(5,5), and one that declared no precision either becomes DECIMAL(18,6).
- →Strings become VARCHAR with no length attached to them. DuckDB's VARCHAR is unbounded, so no column has to be sized in advance and no row can be turned away for being longer than the column it goes in.
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 DuckDB
- →A real .duckdb file, not a script — open it straight away with the DuckDB CLI.
- →DuckDB has genuine DECIMAL and BOOLEAN types, so nothing is flattened on the way in.
What you get
A ZIP containing database.duckdb. If anything about your data needed a judgement call, a _warnings.txt explains it.
Questions
- Is converting XML to DuckDB 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 DuckDB?
- Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real DuckDB 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.