Tablizer

Convert JSON to XML Online

Paste JSON and get XML with one element per row. Element names are made valid automatically, so keys that XML would reject still produce a well-formed document.

From

The only part of this site that uses a server. The address is sent to it so the page can be fetched, because a browser is not allowed to fetch someone else's page itself. Your own files are never involved.

Nothing here is uploaded. The parsing happens on this page.
Edit
Paste or upload something above and it will appear here.
ToDataMarkupDocumentsCodeSchemasImages

The output will appear here once there is a table to convert.

What JSON is

JSON is a text format for nested data: objects with named keys, arrays, strings, numbers, booleans and null. It has no date type and no comments.

Every web API, most configuration files and anything that talks to JavaScript.

What XML is

XML marks up data with nested named tags and optional attributes. It is verbose, strict about being well-formed, and can carry a schema that says what shape a document must have.

Enterprise integrations, government data feeds, RSS, SOAP services and older document formats.

What changes when you convert JSON to XML

Four shapes all read correctly: an array of objects, an array of arrays with a header row, an object of column arrays, and an object keyed by row id. A single wrapper key holding the array, which is how most APIs reply, is unwrapped automatically. Nested objects are flattened one level into dotted keys; anything deeper is kept as JSON text in the cell, because a table cannot hold a tree.

Each row becomes an element with one child per column. Header names are rewritten where they have to be, because an XML tag cannot start with a digit or contain a space, so a column called 2024 Sales becomes _2024_Sales.

Keys become element names, and some keys cannot be. An XML name cannot start with a digit or contain a space, so a key called 2024 Sales becomes _2024_Sales. The rewrite is mechanical and reversible by eye.

Characters that would break the markup are escaped. An ampersand becomes & and an angle bracket becomes <, which is what makes the output parse rather than fail on the first value containing a company name like Smith & Sons.

Everything becomes an element. JSON has no notion of an attribute, so there is nothing to map onto one, and inventing a rule about which keys become attributes would make the output unpredictable.

What carries over from JSON to XML

JSON records 2 things about a table that XML has no way to hold.

JSON distinguishes a number from the text of a number; XML does not, so every value arrives as text and has to be re-parsed by whatever reads it next.

An empty cell and a missing one are the same thing in XML, so a null and an empty string in the JSON both come out blank and can no longer be told apart.

The identifier 007 comes out of the XML as 007. Reading it as a number would have made it 7, and an id that changes value is worse than one that stays text.

The role "Analyst, data" survives with its comma, in one cell rather than split across two. That is the first thing to check in any converted table, and the usual place a XML file goes wrong.

The quotes around Jonah "Jo" Pryce are written as the HTML entity " in the XML.

A worked example

Three rows of staff data, with an identifier that has a leading zero, a value containing a comma, a value containing quotes and one blank cell. Those are the four places formats disagree, so they are the four places to look.

JSON in
[
  { "id": "007", "name": "Halima Yusuf", "role": "Analyst, data", "started": "2024-03-15", "hours": "38.5" },
  { "id": "012", "name": "Jonah \"Jo\" Pryce", "role": "Engineer", "started": "2025-11-02", "hours": "" },
  { "id": "104", "name": "Wei Chen", "role": "Manager", "started": "2023-06-30", "hours": "40" }
]
XML out
<?xml version="1.0" encoding="UTF-8"?>
<staff>
  <row>
    <id>007</id>
    <name>Halima Yusuf</name>
    <role>Analyst, data</role>
    <started>2024-03-15</started>
    <hours>38.5</hours>
  </row>
  <row>
    <id>012</id>
    <name>Jonah &quot;Jo&quot; Pryce</name>
    <role>Engineer</role>
    <started>2025-11-02</started>
    <hours></hours>
  </row>
  <row>
    <id>104</id>
    <name>Wei Chen</name>
    <role>Manager</role>
    <started>2023-06-30</started>
    <hours>40</hours>
  </row>
</staff>

Questions

How do I convert JSON to XML?

Paste your JSON into the box above or drop the file onto it. Check the table in the grid, then copy or download the XML from the output panel. It takes one step and the data never leaves your browser.

Why did my zip code lose its leading zero?

Type inference turned the text 07030 into the number 7030. Tablizer leaves inference off by default for exactly this reason, and refuses to convert any value starting with a zero followed by a digit even when it is on.

Will my numbers still be numbers?

They will read the same, but XML stores them as text. Anything that sorts or sums the result will need to parse them first, and a leading zero or a currency symbol is the usual place that goes wrong.

Is there a limit on file size?

No. The work happens on your own machine, so the limit is your machine's memory rather than an upload cap. A file with tens of thousands of rows converts in a second or two.

Is my data uploaded anywhere?

No. The parsing and generating are done by JavaScript running on this page. You can watch the network tab while you convert and see that nothing is sent.

Related conversions