Raw bodyOK
Confirm that you pasted the actual response body, not headers or log text.
A JSON formatter makes valid JSON readable, while an error checker points to commas, quotes, HTML responses, and other parse-breaking patterns.
Examples are prefilled, and supported operations run in the browser where possible.
JSON errors can come from commas, quotes, unclosed braces, or an API returning HTML instead of JSON. This tool formats, minifies, and points to parse error locations in one flow.
{
"name": "FixData",
"tools": ["csv", "json"]
}{
"name": "FixData",
"tools": ["csv", "json",]
}A formatter makes JSON readable, while a validator checks whether it is valid. This tool does both.
Check for expired auth, 404/500 pages, or proxy responses before editing JSON syntax.
Use minify when you need compact logs or config snippets. Use pretty format for review.
| Path | Type | Children | Preview |
|---|---|---|---|
| $ | object | 2 | name, tools |
| $.name | string | 0 | "FixData" |
| $.tools | array | 3 | 3 items |
| $.tools[0] | string | 0 | "csv" |
| $.tools[1] | string | 0 | "json" |
| $.tools[2] | string | 0 | "token" |
Check whether the pasted value is the raw JSON body, whether an API wrapper is mixed in, and whether syntax and output are ready.
Confirm that you pasted the actual response body, not headers or log text.
Look for HTML, login pages, HTTP headers, JSONP wrappers, or security prefixes.
Use line and column details to check quotes, commas, brackets, and truncated strings.
Once valid, create a formatted copy for review or a minified copy for transport.
The payload can be parsed as JSON.
Next step: Format or minify it depending on whether you need review or transport.
Output will appear here.