Processed in your browser

XML / CSV Converter

The XML root must contain one repeated row element whose children become CSV columns. Reverse conversion deliberately emits rows/row so root and row names are not guessed from arbitrary table data.

Processed in your browser
0 / 1,000,000
Converted output

Tool guide

What is XML / CSV Converter?

XML and CSV Converter moves regularly repeated XML records into spreadsheets and generates stable XML from table data. To avoid guessing, an XML root must contain one repeated row element; reverse conversion always emits rows and row, while dotted headers, quoting, delimiters, and spreadsheet-safety rules remain explicit. Common workflows include the following. Export repeated XML records to a table. Generate stable rows/row XML. Review headers, fields, and formula risk. The page also documents input boundaries, output behavior, and practical cautions so you can review the result before putting it into an application, configuration, test, or production workflow.

When to use it

  • Export repeated XML records to a table.
  • Generate stable rows/row XML.
  • Review headers, fields, and formula risk.

How to use it

  1. Choose a direction and delimiter.
  2. Prepare one repeated row element for XML input.
  3. Enable spreadsheet safety when appropriate.
  4. Convert and verify headers and field counts.
  5. Review the generated rows/row XML structure.
  6. Load one of the realistic examples first to verify the selected options and processing direction before replacing it with your own data.

Runnable examples

The “Example 1” and “Example 2” buttons load the matching inputs. They cover different structures, directions, or boundaries and can be run directly in the workspace.

Example 1

<tools><tool><id>41</id><name>YAML TOML</name><status>developed</status></tool><tool><id>50</id><name>XML TOML</name><status>verified</status></tool></tools>

Example 2

id,name,status
41,YAML TOML,complete
50,XML TOML,verified

Input rules

  • The XML root must contain one repeated row type.
  • CSV headers must be unique and non-empty.
  • DTD, ENTITY, and mixed content are unsupported.
  • Text input is counted before processing and is limited to 1,000,000 characters on this page; file modes apply the separate file limit shown in the workspace.
  • The XML root must contain one repeated row element type.

Output rules

  • XML row elements become CSV rows.
  • Nested fields use dotted headers.
  • CSV import emits rows/row.
  • Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
  • CSV import always emits rows and row element names.

Limitations and cautions

  • The XML root must contain one repeated row element type.
  • CSV import always emits rows and row element names.
  • Mixed content, comments, and namespaces cannot round-trip losslessly.

How your data is handled

All parsing, format conversion, Base64 work, and intermediate data remain in the current browser tab. JSONLane does not upload the input or retain it after refresh or close.

FAQ

Is XML or CSV content uploaded?

No. Parsing, conversion, and output generation remain in the current browser tab.

Is every round trip lossless?

No. Comments, layout, type systems, and binary capabilities differ, so the page identifies the areas that require review.

Why can valid input still be rejected?

The destination may not have a safe representation. Dangerous keys, unsafe integers, excessive depth, and ambiguous mappings are rejected instead of silently rewritten.

Can XML row element names differ?

No. The root must contain one repeated row element type.

What root name does CSV import use?

It always produces rows with repeated row children.

How do XML attributes enter CSV?

They use @attributes in the intermediate structure and can appear as dotted columns.

Updated: 2026-08-09