JSON Schema Validator — Validate JSON Against a Schema

Paste a JSON Schema on the left and a document on the right to get a readable list of every constraint the document breaks, each one pointing at the exact property that failed. Both documents stay in your browser.

What is supported

The draft-07 vocabulary, which is what most schemas in the wild are written against:type, enum and const; the numeric bounds (minimum, maximum, the exclusive variants and multipleOf); the string constraints (minLength, maxLength, pattern and the common format values); array shapes (items as a schema or a tuple,minItems, maxItems, uniqueItems, contains); object shapes (properties, patternProperties,additionalProperties, required, propertyNames,dependencies); the combinators allOf, anyOf,oneOf and not; and if/then/else.

Local references resolve — #/definitions/address and #/$defs/addressboth work. Remote $ref URLs are deliberately not fetched: this page makes no network requests, so a schema that points at another host will report the reference as unresolvable rather than quietly reaching out for it.

Reading the errors

Each row names the failing keyword, the path in your document ($.address.zip) and what was expected in plain English. When a document fails ananyOf or oneOf, the branch that came closest is shown rather than every branch at once, which is usually the one you meant to match.

Scroll back up and paste your schema — validation runs as you type.