Why "Invalid JSON" Isn't a Useful Error on Its Own
Anyone who has pasted a large JSON payload into a parser and gotten back nothing more than "Unexpected token" knows the frustration — the message confirms something is wrong without saying where. For a 5-line object that's a minor annoyance; for a 500-line API response, it can mean scanning the whole thing by eye, bracket by bracket, to find one missing comma. A validator is only as useful as the location it can point to.
Why Browser Error Messages Aren't Reliable Enough
Every browser exposes JSON parsing through the same JSON.parse() function, but the error messages it throws are not standardized — they vary by JavaScript engine and even by version of the same engine. Older engines included a numeric character position in the message ("Unexpected token } in JSON at position 45"); newer versions of some engines have moved to showing a text snippet instead, without any explicit position at all. A tool that tries to extract a line and column by pattern-matching those messages will work today and quietly break the next time a browser updates its wording.
A More Reliable Approach: Track Position While Parsing
The fix is to stop depending on the error message entirely. Instead, a small hand-written scanner walks the JSON text character by character, following the same grammar rules as any JSON parser — an object needs a quoted key, then a colon, then a value, then a comma or closing brace, and so on — while keeping a running character index. The moment something doesn't match what the grammar expects, that index is exactly where the document stopped making sense, independent of whatever wording any particular browser would have used. Converting that index into a line and column is simple from there: count the newlines before it for the line number, and measure the distance back to the last newline for the column.
What Validation Catches That a Successful Parse Doesn't
It's worth remembering that valid JSON and correct JSON aren't the same thing — a validator confirms the syntax is well-formed, not that the data means what you intended. A JSON file with a typo'd key name, or a number stored as a string, will parse without any error at all. Syntax validation is the first filter, catching the mechanical mistakes (a stray comma, an unclosed bracket, an unescaped quote) that would otherwise crash whatever system consumes the file — not a substitute for checking the actual content against whatever schema or expectations that system has.
Frequently Asked Questions
Because JSON.parse() error messages aren't standardized across JavaScript engines or even across versions of the same engine — older engines included a numeric character position, while newer versions of some engines show only a text snippet with no position at all. A tool that tries to extract a line and column by pattern-matching that message text will work today and quietly break the next time a browser updates its wording.
The two most common are trailing commas (valid in JavaScript object literals but invalid in strict JSON) and missing quotes around object keys. Both are immediately obvious once a validator points to the exact character where the document stopped making sense, rather than leaving you to scan a large file bracket by bracket.
Instead of depending on the browser's error message, a reliable validator walks the JSON text character by character with a hand-written scanner that follows the same grammar rules a JSON parser would — an object needs a quoted key, then a colon, a value, then a comma or closing brace, and so on. The moment something doesn't match what the grammar expects, that character index is exactly where the document broke, and it's converted into a line number by counting newlines before it and a column by measuring distance back to the last newline.
Yes — a validator that tracks position while parsing character-by-character, rather than relying on the browser's inconsistent JSON.parse() error text, can point directly to the line and column where a large payload breaks. That turns finding one missing comma in a 500-line API response from a manual bracket-by-bracket scan into an instant lookup. It's a one-time $3.99 purchase — no subscription, no account required.
No — valid JSON and correct JSON aren't the same thing. A validator only confirms the syntax is well-formed; a file with a typo'd key name or a number stored as a string will still parse without any error. Syntax validation catches mechanical mistakes like a stray comma or unclosed bracket, but it's not a substitute for checking the actual content against whatever schema the consuming system expects.