JSON Validator

Check whether your JSON is valid. Paste a document below and the validator reports the first syntax error with its line and column, or confirms the document parses cleanly.

json-validator · runs locally

What this JSON validator checks

A JSON validator (or JSON syntax checker, or JSON lint tool) verifies that a document follows the JSON grammar defined in RFC 8259: double- quoted strings, comma-separated members, matched braces and brackets, and no extras like comments or trailing commas. This tool runs your input through a strict parser — the same one browsers and Node.js use — so if it passes here, it will parse anywhere.

When validation fails, the raw parser message can be cryptic (“Unexpected token } in JSON at position 47”). This validator translates that character position into a line and column number, so you can jump straight to the offending spot in your editor instead of counting characters.

How to validate JSON online

  1. Paste the JSON document into the box above.
  2. Click Validate JSON.
  3. Read the verdict: a summary of the document if valid, or the error and its location if not.
  4. Fix the reported issue and validate again until the document passes.

Validation vs. formatting

Validation answers one question: will this parse? If you also want to make the document readable, run it through the JSON Formatter after it validates — formatting requires a successful parse first, so the two tools naturally work together when debugging API responses, webhook payloads and configuration files.

Frequently asked questions

What are the most common JSON syntax errors?

Trailing commas after the last item, single quotes instead of double quotes, unquoted property names, comments (JSON does not allow them), and unescaped control characters inside strings. These account for the vast majority of validation failures.

Is JSON5 or JSONC valid JSON?

No. JSON5 and JSONC are supersets that allow comments, trailing commas and unquoted keys. Many tools accept them (VS Code settings, for example), but a strict JSON parser — like the one used by APIs and this validator — will reject those extensions.

Why does the validator only show one error?

JSON parsers stop at the first character that violates the grammar, because everything after that point is ambiguous. Fix the reported error, validate again, and the parser will surface the next problem if one exists.

Does valid JSON mean my data is correct?

It means the document is syntactically well-formed. It does not check that the fields, types or values match what your application expects — that is schema validation, which is a separate step usually done with JSON Schema.