How to Convert Excel Spreadsheets to XML in Your Browser

What happens during the conversion

Looty Tools Excel to XML works on one visible worksheet at a time — you choose it explicitly when a workbook has more than one, and sheets are never combined into a single document. The first row of the chosen sheet is treated as column headers, and every row after it becomes a row element containing one field per column.

Header text is written into a name attribute on each field element rather than turned into an element tag — for example <field name="Customer Email">…</field> — because raw header text often contains spaces, punctuation, or characters that are not legal in XML tag names. Attributes tolerate that text safely, so you rarely have to rename columns to make the export valid.

Cell values come from SheetJS’s resolved display values, not the underlying formulas. If a cell shows a calculated total, that computed number is what lands in the XML — the formula itself is never re-executed by the browser or a server.

What to watch for

Because headers live in attributes instead of tag names, duplicate or blank column headers do not break the output the way they might in a schema built from tag names — a blank header is filled in with a placeholder label, and duplicates simply keep their original text.

Values are not type-cast on the way out. Zero, “FALSE”, and similar cell contents are written as literal text, not converted to XML-native numeric or boolean types, so anything reading the file needs to parse those types itself. Date cells use the same formatted text Excel would display, not a normalized timestamp.

The one-sheet-at-a-time design means a multi-tab workbook needs one conversion pass per sheet you want in XML; there is no option to fold several worksheets into one combined document.

When this conversion is the right move — and when it isn’t

It’s a good fit when a downstream system — a legacy import job, a CMS content loader, a config pipeline — expects row-and-field XML instead of a flat CSV or nested JSON, or when you want a quick intermediate file to feed into an XSLT transform. In practice that just means opening the tool, picking the sheet, and downloading or copying the XML it produces.

It’s a weaker fit when the destination expects a specific, pre-agreed XML schema rather than the generic rows/row/field shape this tool produces — you’ll likely still need a mapping step afterward. It’s also not the right tool if you need multiple sheets merged into one hierarchy, or if the destination is really JavaScript or an API that would be happier with JSON in the first place.

Limits and privacy

Workbooks must be 25 MB or smaller with at most 50 worksheets, and hidden worksheets are left out of the sheet picker entirely. A worksheet that has only a header row and no data rows is rejected rather than producing an empty document, and generated output is capped at 50,000 data rows, 500 columns, and 50 MB of XML text.

The workbook is read and converted entirely in your browser using SheetJS — nothing is uploaded to Looty Tools servers to perform the conversion, which matters if the sheet contains account numbers, HR data, or other sensitive columns.