JSON Schema Validator
Validate a JSON document against a JSON Schema and see exactly which property fails and why, supporting common JSON Schema drafts. Useful for checking API response shapes or debugging a config file, processed entirely client-side with nothing sent to a server.
Usage examples
Checking an API response shape
Paste the schema your API promises and a sample response to confirm the fields, types, and required properties actually match before you ship.
Debugging a failing config file
When a tool rejects your config with a vague error, validate it here against the documented schema to see precisely which field is wrong and why.
Reviewing a pull request's data contract
Before approving a change to a shared JSON structure, paste the updated schema and a few example payloads to make sure nothing silently breaks.
Validating a config file against a documented schema
Many CLI tools publish a JSON Schema for their config file — paste yours in alongside the published schema to catch typos and type mismatches before running the tool.
Testing edge cases for a schema you're writing
While drafting a new schema, paste in a few deliberately invalid documents (missing a required field, wrong type) to confirm your schema actually rejects them as expected.
Frequently asked questions
Which JSON Schema draft is supported?
This tool validates against JSON Schema Draft-07, the most widely supported and compatible draft. Keywords introduced only in later drafts, such as Draft 2019-09 or 2020-12 (for example '$recursiveRef' or the newer 'prefixItems' array form), are not recognized and may be silently ignored.
Is my schema or data sent to a server?
No. Both the schema and the document are validated entirely in your browser using the ajv library. Nothing is uploaded anywhere.
What's the difference between 'Invalid schema' and a validation failure?
'Invalid schema' means the JSON Schema itself is malformed or self-contradictory and could not be compiled, so no validation could even run. A validation failure means the schema compiled fine, but your document does not satisfy its rules — each failing rule is listed with the exact path in your data.
How do I read an error like 'at `/user/age`: must be >= 0'?
The path shows where in your JSON document the problem is located, using '/' to separate nested keys and array indexes. The message after the colon explains which rule from the schema was broken.
Can a schema reference another schema with $ref?
Only within the same pasted document using local, same-document JSON Pointers (like '#/definitions/address'). External file or URL references aren't resolved, since nothing is fetched from the network.
What does 'additionalProperties: false' actually enforce?
It makes the schema reject any object that has properties not explicitly listed, which is a common way to catch typos in field names (like 'eamil' instead of 'email') that would otherwise pass silently.
Is an empty schema ({}) valid?
Yes — an empty schema places no constraints at all, so every JSON document validates against it successfully.