✔ JSON Schema Validator

Validate JSON data against a practical subset of JSON Schema Draft 7. Runs entirely in your browser.

Last updated: November 8, 2026 · By the BoltQuickTools team

Testing a document against a JSON Schema

You are writing an API contract or config format and want to know whether a sample payload satisfies it, and exactly where it does not. This page checks one JSON document against one schema using a validator built into the page. It covers most of Draft 7, with the exceptions listed below.

Running a check

  1. Paste the schema into JSON Schema and the document into JSON Data.
  2. Press Validate. The result is either "Valid - JSON data conforms to the schema" or a list of every error found.
  3. Format Both re-indents the two panels and leaves a panel alone if it does not parse.
  4. Schema Tree shows the schema's properties, types and constraints as a list that you can fold.
  5. Sample (Valid) and Sample (Errors) load working examples.

What an error report looks like

Press Sample (Errors) then Validate and you get "Invalid - 7 errors found":

name: String too short
  Expected: minLength 1 | Actual: length 0
age: Value below minimum
  Expected: minimum 0 | Actual: -5
email: Invalid format
  Expected: format "email" | Actual: "not-an-email"
roles[1]: Value not in enum
  Expected: one of ["admin","editor","viewer"] | Actual: "superuser"
roles: Array items are not unique
  Expected: all unique items | Actual: duplicate items found
website: Invalid format
  Expected: format "uri" | Actual: "not a url"
extraField: Additional property not allowed
  Expected: no additional properties | Actual: found "extraField"

Validation does not stop at the first problem, but a type mismatch skips the other checks for that value, so fixing one error can reveal another.

Where this validator differs from the specification

Each of these was confirmed by running the page. The first four produce a false "Valid".

Drafts, typos and composition

My schema has a typo, but validation passes. Why?

Unknown keywords are ignored, and the schema itself is not checked. {"requried":["a"]} passes any object, so if a rule seems to do nothing, check its spelling.

Can I use 2019-09 or 2020-12 schemas?

Newer keywords such as prefixItems, unevaluatedProperties and dependentRequired are silently ignored. Use a library such as Ajv for those drafts.

Does it support if, then and else?

Yes, along with allOf, anyOf, oneOf, not and dependencies. anyOf and oneOf failures appear as a single summary line, without the reasons from each branch.

If the JSON itself fails to parse, the JSON Formatter is the quicker check. Once a schema is settled, the JSON Schema to Code Generator can turn it into types, and the JSON guide has more background.