JSON Tools

Tools for the JSON you meet every day in API responses, configuration files and logs: make it readable, find the exact position of a syntax error, explore it as a tree, edit it in place, or shrink it for transport.

Popular JSON Tools

All JSON Tools (10)

About JSON

JSON (JavaScript Object Notation) is a text format for structured data, standardised in RFC 8259 and ECMA-404. A document is built from objects ({}), arrays ([]), strings in double quotes, numbers, true, false and null. The grammar is deliberately small, which is why almost every language can read and write it, and also why small slips such as a trailing comma or a single-quoted string make a document invalid.

JSON5 is a separate, more relaxed format that allows comments, trailing commas and unquoted keys. It is handy for hand-written configuration but is not accepted by standard JSON parsers, so this category keeps JSON and JSON5 tools apart.

Which tool to use

To read a response, start with the JSON Formatter. If the text is rejected, the JSON Validator page explains the usual causes. For a document too long to scroll, the JSON Viewer lets you collapse branches, and the JSON Editor is for changing a document while keeping it valid. The JSON Sorter and JSON Compare answer what changed between two versions. JSON Minify and JSON Stringify prepare a document for transport: the first removes whitespace, the second wraps the whole document in one escaped string.

Frequently asked questions

Which JSON tool should I start with?

Use the JSON Formatter if you want readable output, the JSON Validator if you only need a yes or no with the error position, and the JSON Viewer when the document is large and you want to collapse sections.

Do these tools accept JSON with comments?

Standard JSON does not allow comments, so the JSON tools report them as errors. Use the JSON5 Formatter or JSON5 Validator for files with comments.

Can the tools handle line-delimited JSON (NDJSON)?

Yes. The formatter, validator and minifier detect one-JSON-value-per-line input and check each record, reporting the line of any bad record.

Common use cases

  • Reading a minified API response while debugging
  • Finding why a request body is rejected with "invalid JSON"
  • Comparing two versions of a configuration file
  • Normalising key order before committing JSON to version control
  • Shrinking JSON before embedding it in a URL or message

Example

{
  "id": 42,
  "name": "Ada",
  "roles": ["admin", "editor"],
  "manager": null
}

A valid JSON object: double-quoted keys, no trailing comma, and the six JSON value types.