XML to CSV

CSV has rows, XML has a tree, and the bridge between them is a repeating element. The page finds the most numerous group of same-named siblings and makes one row per occurrence — in a catalogue of books, that is the book element. Every other candidate it found is listed, so if it picked the wrong one you can name the right one by name or by path. A document with no repeated siblings still converts: it becomes a single row, which is usually what you want from a config file.

Within a record, every leaf value becomes a column. Nested elements flatten to dotted paths, so address/city becomes address.city; attributes take the prefix you set, @id by default, which keeps them from colliding with an element of the same name. A leaf that repeats inside one record can be joined with a separator, split into numbered columns, or reduced to the first value. The header is the union of every record’s keys in first-seen order, and missing values are left empty rather than shifted.

Comments and processing instructions are dropped, mixed content (text interleaved with child elements) keeps only the text, and namespaces are kept as written rather than resolved. A deeply irregular document will not become a clean table, so the page reports the empty cells and how many records are missing a column instead of silently producing something tidy-looking. Output is RFC 4180 quoted, or fully quoted on request. Nothing leaves the browser; the same four anonymous usage counts as the rest of the site apply.