Guides Knowledge Base

JSON Checker Online

Free JSON checker online. Paste JSON to check its syntax against RFC 8259 and get the exact line and column of any error. No sign-up, nothing uploaded.

A JSON checker reads your document against the RFC 8259 grammar and tells you whether it is well-formed. Paste JSON and the check runs on every keystroke, reporting valid or invalid status plus the exact line and column where parsing stopped.

What a JSON Checker Reports

A syntax check answers one question: does this text conform to the JSON grammar? It does not judge whether the fields are the ones your API expects — that is a schema check. What it gives you is certainty that JSON.parse() will not throw.

Checker Output

  • Status — valid or invalid, updated as you type.
  • Error position — the line and column where the parser stopped.
  • Structure statistics — key count, maximum nesting depth, and byte size.

Syntax Check vs Schema Check

Two different failures look the same from the outside. {"age": "thirty"} passes a syntax check and fails a schema check that requires an integer. {"age": 30,} fails the syntax check and never reaches the schema. Check syntax first; it is the cheaper and more common fault.

Checking JSON on the Command Line

# jq exits non-zero on invalid JSON
jq empty file.json

# Python, with the error position printed
python3 -m json.tool file.json > /dev/null

Who this guide is for

  • Check a config file before a deploy that would fail on a parse error
  • Confirm a fixture file is well-formed before committing it
  • Check a payload pasted from a bug report against the spec
  • Verify an editor did not corrupt a file with smart quotes

Try the free JSON Validator

Runs entirely in your browser — no upload, no signup, and your data never leaves your device.

Open JSON Validator

Frequently Asked Questions

Is a JSON checker the same as a JSON validator?

In everyday use, yes — both check text against the JSON grammar. "Validator" sometimes implies schema validation as well, so this page uses "checker" for the syntax-only meaning.

Is anything uploaded when I check my JSON?

No. The check runs in your browser tab. Nothing is transmitted, logged, or stored, which matters when the payload carries tokens or customer records.

Why does my JSON fail the check when it looks fine?

The usual culprits are invisible: a smart quote pasted from a document, a byte-order mark at the start of a file, or a non-breaking space. The reported column points at the offending character.

Tools mentioned in this guide

Related JSON Topics & Reference Articles