JSON Formatter

How to Use the JSON Formatter

1. Paste or type JSON into the large monospace textarea labelled "Paste your JSON here...". The field accepts API responses, log payloads, config files, or a single value such as 42 or "hello".
2. Pick an indent from the dropdown on the right: 2 spaces (the community default, used by npm, prettier, and most REST APIs) or 4 spaces (more common in Python and some enterprise Java shops).
3. Click Format to pretty-print with line breaks and indentation, or Minify to collapse everything onto one line and remove insignificant whitespace.
4. Read errors if any appear. Invalid input surfaces the exact SyntaxError from the engine, including the character position, so you can jump to the offending token.
5. Copy the output with the Copy button in the top right of the output panel, or select the rendered <pre> block manually for partial copies.

What the Formatter Does Under the Hood

The formatter is a thin, honest wrapper around two built-in JavaScript methods: JSON.parse(input) followed by JSON.stringify(parsed, null, indent). When you click Format, the parser walks the string with the rules from ECMA-404 and RFC 8259, rejecting anything outside the JSON grammar. The resulting in-memory tree (objects, arrays, strings, numbers, booleans, and null) is then serialized back with the indent argument set to 2 or 4 spaces, which triggers the stdlib's line-break-per-key emission.

Minify calls JSON.stringify(parsed) with no indent argument, producing the most compact canonical form the spec allows. Because both paths go through a full parse, a successful output is also a valid-JSON certificate: malformed input cannot pretty-print. The whole pipeline executes on the JavaScript engine of the tab you have open (V8 in Chrome and Edge, SpiderMonkey in Firefox, JavaScriptCore in Safari), so there is no network request at format time and no server ever sees your payload.

When This Tool Earns Its Keep

• Inspecting a minified webhook body copied out of a proxy like Charles, mitmproxy, or a Cloudflare request log.
• Cleaning up a compact package.json, tsconfig.json, or OpenAPI document before committing.
• Shrinking a large configuration blob before embedding it in an environment variable or a query string.
• Double-checking that a hand-written JSON fixture parses before shipping it into a test suite.
• Explaining a nested GraphQL response to a teammate on a call, where readable indentation matters more than file size.
• Sanity-checking that a backend that claims to emit JSON does not secretly produce JSONP or JSON5.

Common Pitfalls and Edge Cases

• Trailing commas like {"a":1,} are legal in JavaScript object literals and JSON5 but illegal in strict JSON. The parser rejects them with a SyntaxError.
• Comments (// or /* */) are never allowed in RFC 8259. Strip them before pasting if your source is a JSONC file like tsconfig.json.
• Single quotes around keys or strings are invalid; only double quotes are accepted. Python repr() output often hits this.
• Unquoted keys such as {name:"Ada"} parse in JS but not JSON. Quote every key.
• NaN, Infinity, and undefined are not JSON values; JSON.parse throws on them even though they are valid JavaScript.
• Large numbers beyond Number.MAX_SAFE_INTEGER (2^53 - 1) lose precision on parse. For order IDs or blockchain amounts, keep them as strings.

JSON in a Nutshell: RFC 8259 and ECMA-404

JSON (JavaScript Object Notation) was introduced by Douglas Crockford in the early 2000s and standardized twice, once by ECMA International as ECMA-404 and once by the IETF as RFC 8259 (which supersedes the older RFCs 4627 and 7159). The grammar is deliberately small: a value is an object, array, string, number, boolean, or null, with whitespace permitted anywhere outside a token. RFC 8259 mandates UTF-8 for network interchange, which is why servers that emit UTF-16 or Latin-1 JSON break clients. A well-formed JSON document is a single value, so a bare [1,2,3] is valid at the top level, not only wrapped in an object. Comments, trailing commas, and hex numbers are excluded on purpose; the simplicity is the feature.

Alternatives and When They Beat This Tool

Command-line jq is better when you need to query or transform JSON, not just reshape whitespace: it handles streaming over gigabytes and has a real query language. Python's python -m json.tool is handy in a terminal pipeline and is already installed on most Unix systems. IDE plugins like Prettier, VS Code's built-in Format Document, or JetBrains' JSON tool window format in place without copy-paste. A browser formatter like this one wins when you have a single blob in your clipboard, no shell open, and you do not want to paste sensitive data into a remote service like jsonformatter.org or online-json.com. For anything larger than roughly 20 MB, switch to a streaming parser such as jq, simdjson, or Node's stream-json package, since single-pass JSON.parse holds the entire parsed tree in tab memory.