Free JSON Formatter & Validator

How to use the JSON Formatter

1. 1

   Paste your JSON

   Paste minified, messy or broken JSON into the input editor — an API response, a config file or a log line.

2. 2

   Click Beautify or Minify

   Beautify indents the JSON so it is easy to read. Minify removes all whitespace to make it as small as possible.

3. 3

   Fix errors automatically

   If the JSON is invalid you'll see the error. When it can be repaired, click Fix JSON to correct unquoted keys, single quotes, trailing commas and comments in one go.

4. 4

   Copy or download

   Copy the result to your clipboard or click Download to save it as a .json file.

Examples

{"id":42,"user":{"name":"Ada","roles":["admin","dev"]},"active":true}

{
  "id": 42,
  "user": {
    "name": "Ada",
    "roles": [
      "admin",
      "dev"
    ]
  },
  "active": true
}

{
  name: 'TrueFormatter', // app name
  tags: ['json', 'tools',],
}

{
  "name": "TrueFormatter",
  "tags": [
    "json",
    "tools"
  ]
}

Common errors and how to fix them

Unexpected token } in JSON

There is a trailing comma before a closing } or ]. Click Fix JSON, or delete the last comma.

Expected double-quoted property name

A key is unquoted or uses single quotes, which is valid JavaScript but not JSON. Fix JSON adds the double quotes for you.

Unexpected token < in JSON at position 0

You pasted HTML, not JSON — usually an error page returned by a server or proxy. Check the status code and response of your API call.

Unexpected end of JSON input

The JSON is cut off: a closing bracket is missing or the copy was truncated. Copy the full response again.

Large numbers change after formatting

JavaScript numbers lose precision beyond 2^53 (9007199254740991), so 64-bit IDs can change. Have your API send such IDs as strings.

Invisible character at the start of the file

Files saved with a UTF-8 BOM start with an invisible \uFEFF character. Delete the first character or re-save the file as UTF-8 without BOM.