Step 1 / source
Choose the source
Drop one file here
Choose a CSV whose first row names columns and whose later rows use one consistent delimiter.
Checking publication status...LOCAL DATA CONVERTER / CSV TO XML
CSV to XML
Convert a rectangular header-based CSV into well-formed UTF-8 XML with one explicit element per row and safely escaped cell text.
Processed in this browserOne UTF-8 .csv file up to 5 MB, with no more than 50,000 data rows, 200 columns, 1,000,000 cells, or 20 MB output. Every row must have the same width.
CSV - 50,000 records
No file upload
This operation runs with browser APIs. Nirmion receives catalogue requests, not the selected source bytes.
Original stays unchanged
The converter creates a separately named output. It never writes back into the source file.
Bounded work
One UTF-8 .csv file up to 5 MB, with no more than 50,000 data rows, 200 columns, 1,000,000 cells, or 20 MB output. Every row must have the same width.
Plain-language method
How a CSV row becomes one XML record
Nirmion parses quoted delimiters and line breaks, validates a rectangular table, turns each header into a safe unique XML element name, escapes reserved XML characters in every cell, and wraps all row elements inside the requested root element. It never interprets cell text as markup.
- 01Choose a valid source
Use one header row and consistently separated data rows. A shifted quote or missing delimiter changes table shape and is rejected before XML is generated.
- 02Review the conversion choices
Root and row names must be simple XML names such as dataset and record. Header text is normalized automatically and duplicate names receive suffixes.
- 03Inspect the separate result
The download ends in _nirmion_tools_records.xml, declares UTF-8, and contains one child element for every source column in every record.
Useful when
Practical jobs this tool handles
- Prepare a legacy XML import from a CSV export.
- Send tabular records to a system that accepts simple XML.
- Create inspectable XML fixtures from approved data.
Before converting
Confirm the XML vocabulary
- Identify the CSV delimiter before conversion.
- Use root and row names expected by the receiving system.
- Review normalized header element names in the result.
Know the boundary
Header names may be normalized
Spaces and unsupported punctuation in CSV headers become safe XML-name characters, and collisions receive suffixes. Validate those generated element names against the receiving schema.
Quick answers
Questions before you convert
The output is simple record XML, not an inferred schema.
Are ampersands and angle brackets safe?
Yes. Cell values are XML-escaped and are never treated as elements.
Does it create an XSD schema?
No. It creates one self-contained XML data document without guessing data types.
What happens to duplicate headers?
They receive stable numeric suffixes so both columns remain present.