JSON Schema validation checks a JSON instance against a schema. This JSON Schema Validator evaluates a documented Draft 07 keyword subset: type, properties, required, additionalProperties, items, enum, const, length and numeric bounds, pattern, minItems, maxItems, uniqueItems, and local $ref under #/. It runs in the browser. Nothing is uploaded.
This is not a full JSON Schema implementation. Combinators such as allOf, anyOf, oneOf, not, if/then/else, patternProperties, tuple items arrays, and remote $ref are rejected with a named keyword. They are not silently ignored. Silent ignore would mark invalid data as valid.
Syntax-only checks belong on the JSON Validator. Schema checks whether a value matches a contract. Generate a starting schema on the JSON Schema Generator if you do not have one yet.
Parse errors name the box. Schema errors use paths such as users[0].age. A missing required property is reported on the object path.
A schema that requires id as a number and name as a string, with additionalProperties: false, accepts {"id":1,"name":"Ada"} and rejects an extra email or a string id.
Supported keywords are listed in the first section. Annotation keywords such as title, description, and $schema are ignored. Unsupported evaluation keywords abort validation so you do not get a false pass. Local $ref must point at a schema object in the same document; cycles are refused.
Type checks accept a string or an array of types, including ["string","null"]. integer matches finite whole numbers. additionalProperties may be true, false, or a nested schema for extra keys. items must be one schema, not a tuple list. pattern is a browser regular expression; invalid patterns fail the schema, not the instance.
Use this for the schemas this site can generate and for hand-written object/array contracts of the same shape. Do not paste a large vendor schema that is built from allOf and external $ref and expect a useful result. Take that file to Ajv or your language’s schema library.
A valid instance is reported as Valid. Failures list every problem found under the node budget. The instance is never executed. Strings that look like HTML stay strings. If you only needed to know whether the instance is legal JSON, you already have that answer from parse; do not treat a schema pass as a security review of the payload.
Empty input is not validated. A schema that is a JSON array is refused. Boolean schemas true and false follow the spec: true accepts any instance, false accepts none.
format (email, uri) is not evaluated.pattern uses the browser regular expression engine.Generate then edit first: how to generate and check a JSON Schema. Background: what JSON Schema is.
Parse and validation run in this browser. Instance and schema are not sent to YallaSolve for this tool.
Checks JSON against a documented Draft 07 keyword subset (type, properties, required, items, enum, and similar). Combinators such as allOf and remote $ref are rejected, not ignored.
No. It evaluates a documented keyword subset. Unsupported evaluation keywords abort with a named error instead of being ignored.
No. JSON Validator only checks JSON.parse. This page checks the instance against the schema.
Only local references that start with #/. Remote URLs and cyclic refs are refused.
allOf is not evaluated here. Reporting the instance as valid would be a lie. Remove combinators or use a full validator in your toolchain.
