CSV → XML — feed relational dumps into XML-first systems
CSV parses to a JSON array, then serialises with the same json-to-xml rules — predict root/items naming from your grid shape.
Developer notes
• Flat arrays produce repeated `_item` tags — mirror JSON→XML docs. • Validate partner XSD offline.
When teams pick this route
• EDI-ish pipelines still expecting XML envelopes. • Cross-team handoffs where analysts only speak CSV.
About these options
CSV exports: choose a delimiter (Auto follows locale — semicolon on /fr), RFC-minimal vs always-quoted fields, line endings, and whether to emit a header row. CSV imports: delimiter + whether row 1 holds column names (Auto delimiter follows locale only for convenience). JSON output (XML, YAML, or CSV sources): indentation (including compact one-line) and optional recursive key sort. JSON → XML: toggle pretty-printing and indent width. YAML output: indent width, readable vs tighter layout, and deterministic string quoting (there is no source YAML file to “preserve”). XML comments are not represented in the intermediate JSON tree.
Worked examples
Two-column grid
Sample input
Sample output
Pipe-delimited logs
Sample input
Sample output
Navigate related converters
Pivot JSON first via CSV → JSON, compare XML → CSV, or emit YAML through CSV → YAML.
CSV → XML FAQ
Markup quirks
Namespaces?
Not injected — add wrappers manually post-export.
Attributes?
Only what JSON→XML produces today.
Huge CSV?
Parsing is synchronous — chunk inputs.
Different XML root?
Post-process or reshape JSON before XML via csv→json→manual edit.
Looking for every converter, encoder, and minifier in one place? Developer tools hub Open the curated developer tools catalogue.