The 8 most common JSON errors and how to fix them
Trailing commas, single quotes, comments, malformed numbers… what each error means and how to fix it.
Validate and pretty-print or minify JSON data.
Runs in your browser
Valid JSON. Output is 116 characters.
Output
{
"name": "TodoEnUnClick",
"tools": 30,
"languages": [
"es",
"en"
],
"free": true,
"ads": null
}Turn compact or messy JSON into readable, indented text — or minify it to save space. The JSON is validated before formatting and, if there's an error, you get the line, column and likely cause.
Parsing is done by a dedicated parser that never executes the content and keeps numbers exactly as written, so very large integers don't lose precision.
Paste a single-line response and get an indented structure that's easy to scan.
Format both with “Sort keys” so differences stand out when you compare them line by line.
The JSON is processed in your browser and never sent to a server. Still, avoid sharing screenshots that contain tokens or passwords.
Both validate the same way; the formatter also rewrites the JSON, while the validator shows statistics about its structure.
Because standard JSON doesn't allow them. Formats like JSON5 or JSONC do, but they aren't valid JSON for most APIs.
Trailing commas, single quotes, comments, malformed numbers… what each error means and how to fix it.