Step 1 / source
Choose the source
Drop one file here
Choose the flat record xml you want to turn into styled xlsx worksheet.
Checking publication status...LOCAL DATA CONVERTER / XML TO EXCEL
Convert repeated flat XML records into a genuine styled XLSX worksheet while blocking DTD and entity declarations.
Step 1 / source
Choose the flat record xml you want to turn into styled xlsx worksheet.
Checking publication status...This operation runs with browser APIs. Nirmion receives catalogue requests, not the selected source bytes.
The converter creates a separately named output. It never writes back into the source file.
One UTF-8 .xml file up to 5 MB. The document must have one root containing repeated flat records within 50,000 records, 200 columns, 1,000,000 cells, and 20 MB output.
Plain-language method
Nirmion validates well-formed XML without DTDs or custom entities, identifies one repeated record element, projects scalar attributes and child elements to columns, and writes a frozen, filterable worksheet. Formula-like text is neutralized.
Use one root containing one repeated record element. Each record may contain scalar attributes and scalar child elements only.
The worksheet name is cleaned to Excel rules and limited to 31 characters.
The result ends in _nirmion_tools_workbook.xlsx and contains values only, not XML hierarchy, schemas, comments, or processing instructions.
WORKED EXAMPLE / REVIEW BEFORE RELYING
Use a short, non-sensitive sample first. This example shows the checkpoints to apply before moving an authorised dataset into the destination workflow.
Choose sample.xml with a header and two representative, non-sensitive records.
Keep the documented defaults, convert once, and compare the preview or result count with the XML sample.
Open the separate Excel download and verify two records, field names, nulls, encoding, and destination compatibility.
Useful when
Before converting
Know the boundary
Nested elements, mixed content, repeated child fields, namespaces with complex structures, schemas, and comments cannot be represented as one rectangular worksheet and are rejected or omitted by contract.
Quick answers
The conversion contract is deliberately explicit.
Yes. Scalar attributes become columns prefixed with @.
No. Nested records are rejected to avoid ambiguous columns.
No. Generated cells are values, and formula-like text is neutralized.
YOUR NIRMION