Tablizer

Convert XML to JSON Online

Paste XML and get JSON. Attributes, nested elements and repeating records all read correctly, and the result is a flat table you can check before you export.

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 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 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 changes when you convert XML to JSON

The first repeating element is treated as the rows. Attributes are read alongside child elements and prefixed so they do not collide with a same-named tag. Nesting one level deep becomes dotted column names; deeper structures are kept as text.

You choose the shape. An array of objects is the default and the one most code expects. A 2D array is smaller. Column arrays suit charting libraries. A keyed object suits lookups by id.

The repeating element becomes the rows. An XML document has one root and usually one wrapper element holding the records; the first array found while walking down is treated as the data, and the wrappers above it are ignored because they carry no values of their own.

Attributes come across alongside child elements, prefixed with an @ so they cannot collide with a same-named tag. An element with both an id attribute and an id child gives you @id and id as separate columns.

XML makes no distinction between a number and the text of a number, so everything arrives as text. Turn type inference on if you want JSON numbers and booleans out the other side.

What carries over from XML to JSON

JSON can express everything XML holds about a table, so this conversion is about shape rather than loss.

JSON wants a type for each column, and XML does not record one, so each column is typed from what its values look like. A column of digits that should stay text - a zip code, a phone number, a leading-zero id - is the usual thing to check afterwards.

The identifier 007 comes out of the JSON 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 JSON file goes wrong.

The quotes around Jonah "Jo" Pryce are escaped with a backslash in the JSON.

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.

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

Questions

How do I convert XML to JSON?

Paste your XML into the box above or drop the file onto it. Check the table in the grid, then copy or download the JSON 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.

What happens to deeply nested XML?

One level of nesting becomes dotted column names. Below that, the structure is written into the cell as JSON text. A table is two dimensional and a document is a tree, so something has to give, and keeping the data as text loses less than flattening it into invented columns.

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