Where exactly is that JSON broken?
Paste a blob or a URL. Peekjson parses it and tells you — in plain language — what went wrong, where, and what the server really sent. Not "unexpected token at position 4471".
Paste a blob or a URL. Peekjson parses it and tells you — in plain language — what went wrong, where, and what the server really sent. Not "unexpected token at position 4471".
Line and column, with surrounding context and a visible marker. No scrolling to count characters from position 4471.
Content-type, status code, redirect chain, and the raw body. If the server returned HTML with a JSON content-type claim, you see both.
"Found an unexpected comma" instead of "Unexpected token ',' in JSON at position 184". Translates the most common V8 JSON errors into terms you can act on.
Pasted JSON is parsed entirely in your browser — nothing is sent to a server. URL fetches go through a server-side validator for your safety, but no content is stored.