{ } JSON Formatter & Validator
Format, beautify, minify and validate JSON. Runs in your browser.
Last updated: November 8, 2026 · By the BoltQuickTools team
Making a JSON blob readable, and finding out why it will not parse
API responses and log entries arrive as one long line, and a single stray comma can make a config file unusable. This page runs your text through the browser's JSON parser, reports whether it is valid and prints it back in the layout you choose.
Buttons
- Beautify indents with 2 spaces. Pasting into Input does this automatically.
- 4-Space indents with 4 spaces.
- Minify removes all whitespace between tokens.
- Copy Output copies the result and Clear empties both boxes.
Typing does not reformat anything; press a button to re-check. The line below the boxes shows "Valid JSON" or the parser's error, plus character counts and a key count.
Beautifying a one-line object
{"name":"Ada","tags":["x","y"],"meta":{"active":true,"score":null}}
Beautify returns:
{
"name": "Ada",
"tags": [
"x",
"y"
],
"meta": {
"active": true,
"score": null
}
}
with 67 chars in, 108 chars out and 5 keys.
A trailing comma, as in {"a":1,}, produced this in Microsoft Edge:
Invalid JSON: Expected double-quoted property name in JSON at position 7 (line 1 column 8)
The wording comes from your browser's engine, so it varies, and the page itself does not highlight the error position in the text.
Your data is parsed, not just re-spaced
Output is rebuilt from the parsed value, so a few things can differ from what you pasted. These come straight from running Minify:
| Input | Output | Why |
|---|---|---|
{"big":12345678901234567890} | {"big":12345678901234567000} | Integers above 2^53 lose precision |
{"f":1.10,"e":1e3} | {"f":1.1,"e":1000} | Number spelling is normalised |
{"a":1,"a":2} | {"a":2} | Duplicate keys: last one wins, with no warning |
{"b":1,"2":1,"a":1,"1":1} | {"1":1,"2":1,"b":1,"a":1} | Integer-like keys move to the front |
{"s":"é\/"} | {"s":"é/"} | Unnecessary escapes are removed |
The first row matters most. Large database or snowflake IDs stored as bare numbers will be silently altered, so do not copy formatted output back into a system if your IDs are that long.
What counts as valid
- This is strict JSON. Comments, trailing commas, single quotes and
NaNare all errors. A byte-order mark at the start is tolerated. - A bare value such as
42or"x"is valid JSON and is accepted. - The key count is an approximation found by pattern matching. A string value containing
":can inflate it, and an empty key is not counted. - The code sets no size limit, so very large documents are limited by your device's memory.
When valid is not enough
Can I allow comments in my config file?
Not here. Comments are not part of JSON. The article on YAML, TOML and JSON5 covers formats that do allow them.
Valid JSON, but my API still rejects it. Why?
This page checks syntax only. To test required fields and types, use the JSON Schema Validator.
Does the formatted text get sent anywhere?
The tool's code only calls the browser's built-in parser and writes to the output box. It makes no network request with your JSON.
To compare two documents by value, try JSON Diff. The JSON guide goes deeper into common syntax errors.