View My JSON
Skip to main content
Blog

JSON validator online: what it checks and how to read the errors

What a JSON validator actually checks, the six mistakes behind most parse errors, and why syntactically valid JSON can still be wrong for your application.

A single missing quote can make a 2 MB payload unreadable. The frustrating part is that the error message is often terse, something like "Unexpected token } at position 1843", and it points near the mistake rather than at it. Understanding what a JSON validator actually checks makes those messages much easier to act on. This post covers the rules from RFC 8259, the half dozen mistakes that cause most failures, how to find the real cause when the reported position is misleading, and the difference between valid JSON and JSON that is correct for your application.

Sources and further reading

Try the JSON workspace