JSON Formatter

1. Format an API response for reading

Paste this JSON or run Format (Beautify). Use Text view to inspect the object and array structure.

Input

{"name":"Tani","active":true,"scores":[10,20]}

Current tool output

{
  "name": "Tani",
  "active": true,
  "scores": [
    10,
    20
  ]
}

In this example, the values stay the same while spaces and line breaks are added. However, the tool parses and reserializes the input; it is not an editor that preserves every original text or value. See the large-integer and duplicate-key cases below.

2. Repair input containing a comment and single quotes

This input is not standard JSON. In this example, Auto-Repair removes the comment, quotes the keys, changes string quotes, and removes the trailing comma.

Input

// example
{name:'Tani',active:true,}

Current tool output

{
  "name": "Tani",
  "active": true
}

Repair is an aid for some common syntax problems. It cannot fully restore an arbitrary damaged file or determine what its author intended.

3. Extract names from an array

Format the input JSON first, open the query panel with the JSONPath button, and enter the path below. The wildcard selects each item in the users array.

Input

{"users":[{"name":"Tani"},{"name":"Mina"}]}

Query path: $.users[*].name

Current tool output

[
  "Tani",
  "Mina"
]

Change the path to $.users[0].name to find only the first name. With one match, this tool displays the value itself rather than an array of matches.

Large integers may round during formatting or paste

This number is outside JavaScript's safe-integer range. Its value changes during parsing in the current tool, not because of the indentation setting.

Input

{"id":9007199254740993}

Current tool output

{
  "id": 9007199254740992
}

Exporting the ID as a string from the original system preserves these digits. Converting an already-rounded result to a string later cannot recover the original number.

Duplicate keys in one object keep only the last value

This input parses without an error, but the first role value disappears. RFC 8259 recommends unique object names for interoperability.

Input

{"role":"reader","role":"editor"}

Current tool output

{
  "role": "editor"
}

If both values matter, revise the original structure to use distinct keys or an array. This tool does not issue a separate duplicate-key warning.

Successful repair does not guarantee unchanged strings

This is a counterexample from running Auto-Repair on already-valid JSON. The current repair logic also removes the comma inside the string, changing its value.

Input

{"note":"a,}"}

Current tool output

{
  "note": "a}"
}

Use Format, not Auto-Repair, to indent valid JSON. Repair can also change the input field, so save the original separately before running it and compare string values afterward.