How do I validate JSON against a JSON Schema?
Paste the schema on the left and the JSON on the right; it is checked as you type. Each error says where in the data it is — as a path like $.items[1].quantity and as a line you can jump to — which keyword failed, and what was expected, such as "0 is below the minimum of 1". The lines with errors are marked in the editor's gutter. Both boxes also accept YAML, and you can open files or drop them in.
Which JSON Schema versions are supported?
Draft 4, 6 and 7, 2019-09 and 2020-12, plus the OpenAPI 3.0 and 3.1 flavours. The version is read from the schema's $schema, or chosen by hand. The differences are respected: exclusiveMinimum as a boolean in draft 4 and a number later, items as a tuple list up to 2019-09 and prefixItems in 2020-12, dependencies versus dependentRequired, and whether keywords beside a $ref count (only from 2019-09). unevaluatedProperties, if/then/else, $defs, $anchor and $id all work. References are followed inside the schema but never fetched from the network.
How do I generate a JSON Schema from JSON?
Switch to Generate and paste example JSON. Every value at the same place is merged into one description, so an array of objects gives one item schema covering them all: a property is required only when every object has it, a field that is sometimes null gets "null" in its type, integers stay integers unless a decimal appears, and formats such as date-time, email and uuid are kept when every string has them. Choose the draft, whether to close objects with additionalProperties: false, and whether a top-level array is a list of samples; then "Validate with this schema" checks your data against it.
Why does my schema accept data it should reject?
Usually a keyword the validator does not know, which JSON Schema silently ignores — a typo such as "requried" or "minLenght", or "required": true written on a property instead of a list on the object. The tool lists those under Problems in the schema with the keyword it thinks you meant. Other common causes: forgetting additionalProperties: false, so unknown fields pass; a "type" missing, so any type passes; or keywords next to a $ref in draft-07 or older, which are ignored there.
Are formats like email and date-time checked?
Yes, by default: date, time, date-time (with real calendar dates, so February 30 fails), duration, email, hostname, ipv4, ipv6, uri, uuid, json-pointer and regex. Since 2019-09 the specification treats format as an annotation that validators may skip, so a strict 2020-12 validator in your stack might accept what this one rejects; untick "Check formats" to see the result without them.
What is the difference between a JSON Schema and an OpenAPI schema?
OpenAPI 3.1 uses JSON Schema 2020-12 as it is. OpenAPI 3.0 used a variant of draft 4 with differences: nullable: true instead of "null" in the type, a single type rather than a list, no const, examples or $defs, and exclusiveMinimum as a boolean. Pick OpenAPI 3.0 as the version to validate a 3.0 schema the way your API tooling will read it. To check a whole OpenAPI document rather than one schema, use the OpenAPI validator.
Is my data uploaded anywhere?
No. Validation and schema generation are JavaScript running in your browser, so the schema and the data — customer records, configuration, anything — never leave your device and are not stored. You can check by opening the network tab and watching it stay empty while you work.