JSON to XML Converter

What are these data formats?

Programs store and exchange structured data, such as settings, records, and lists, in text formats that each write it in their own way. A converter is handy when one program gives you data in a format that another one doesn't read, or when a format is easier to read or edit for the job at hand.

Tool description

This tool converts data between these 12 formats: JSON, YAML, XML, TOML, TOON, CSV, TSV, MessagePack, JSON5, JSONL, INI, and Java properties. Every data format converter here works the same way, from the general Data Format Converter to the ones for a single pair, such as JSON to YAML, CSV to JSON, or XML to JSON: it starts on the formats in its name, and the Source and Target menus switch to any other.

The converters take data as text you paste or type, or as files, and give text or files. Pick which with the File and Text tabs at the top of the source side and of the target side. Both start on Text.

• Text in: paste or type your data, and it converts as you type.
• File in: pick or drop one file or many. Browse files lists only files in the source format, but files dropped on it can be in any of the 12 formats, and each one converts from the format its extension names, so a .yaml file converts as YAML even on the JSON to XML converter. A dropped file with another extension, such as .txt, converts from the source format. Files in UTF-16 or in a legacy encoding, such as Windows-1252, are read too.
• Text out: the result appears in a code editor with syntax highlighting, ready to copy. When several files are converted, the File menu above it picks the file it shows.
• File out: the converted files show up in a grid, each with its own Download button, and keep their file names with the new extension. Download All saves every converted file in one ZIP file, or a single converted file as it is. Pasted data gives one file named converted, such as converted.yaml. The converted files are UTF-8 text, except MessagePack files, which are binary.

The swap button turns the conversion around: the target format becomes the source, the two sides swap tabs, and the result becomes the new input.

When the input isn't valid in the source format, the error message says what's wrong, usually with the line and column of the problem. With files, the error message names the files that failed, and the Text tab on the target side gives the details for the file it's showing.

Your data is converted in your browser and never uploaded.

Example

This JSON:

{
  "users": [
    { "id": 1, "name": "Ann", "admin": true },
    { "id": 2, "name": "Bo", "admin": false }
  ]
}

becomes this YAML:

users:
  - id: 1
    name: Ann
    admin: true
  - id: 2
    name: Bo
    admin: false

this CSV, with one row per user:

id,name,admin
1,Ann,true
2,Bo,false

and this TOON:

users[2]{id,name,admin}:
  1,Ann,true
  2,Bo,false

How the formats map to each other

Formats don't all hold the same kinds of data, so some conversions follow these rules:

• CSV and TSV hold a table. The first row names the columns, and each other row becomes an object. Nested objects become columns named by their path, and lists become JSON text in their cell, so {"name": "Ann", "address": {"city": "Oslo"}, "tags": ["a", "b"]} becomes the columns name, address.city, and tags. Converted back, those columns become nested objects and lists again. When the data is an object that holds one list, such as {"users": [...]}, the rows are the items of that list, and a list of lists becomes rows without a header.
• Text values: CSV, TSV, XML, INI, and properties hold only text, so the converters turn true and false into true and false, and numbers written plainly, such as 42 or 3.5, into numbers. Values such as 007, 1.50, or 1e3 stay text, so zip codes and version numbers keep their exact form.
• XML attributes become keys that start with @, and the text of an element that has attributes becomes #text: <price currency="USD">44.95</price> becomes {"@currency": "USD", "#text": 44.95}. Repeated elements become a list. Converting to XML, keys that start with @ become attributes again. An object with a single key whose value isn't a list becomes the root element. Other data goes inside a <root> element, with each item of a list at the top in an <item> element. Characters that XML names can't have, such as spaces, become _.
• TOML, INI, and properties can only hold named values at the top, so data that's a list is written under the name items, and a single value under value. TOML has no null, so null values are left out.
• INI writes nested objects as sections, such as [server.ssl], lists of values as key[] = value lines, and lists of objects as sections named by their position, such as [users.0].
• Properties keys join nested names with dots and number list items in brackets, such as app.hosts[0], the way Spring Boot writes them. Converted to YAML or JSON, those keys become nested objects and lists, so an application.properties file converts to the layout of an application.yml file. Characters outside Latin-1 are written as \u escapes.
• YAML results quote text that YAML 1.1 readers would read as something else, such as on, yes, or a date, so that YAML 1.1 and YAML 1.2 readers get the same data. A YAML file with several documents separated by --- becomes a list of them, and << merge keys are filled in.
• MessagePack is binary. As text, the tools read and write it as hexadecimal bytes: {"a": 1} is 81 A1 61 01, and the input can have spaces, commas, and 0x before each byte. MessagePack files, picked or saved on the File tab, hold the bytes themselves, so a converted .msgpack file is binary. Several messages one after another become a list.
• JSONL results have each item of the list on its own line.
• Whole numbers too big for JavaScript numbers, such as 64-bit IDs, keep all of their digits.
• TOML dates and times, and MessagePack timestamps, become text such as 1979-05-27T07:32:00Z.

Tips

• To convert cells from a spreadsheet, copy them and paste them as TSV: spreadsheet apps copy cells as tab-separated text.
• CSV and TSV fit data that's a list of similar records. Deeply nested data reads better as YAML, TOML, or TOON.
• Comments in YAML, XML, TOML, JSON5, INI, and properties files aren't kept, since the converters carry over only the data.