Read a JSON Schema as a property list with required fields, constraints and unresolved references, and generate an example instance from it.
Waiting for a schema
A JSON Schema document. Nothing is fetched, so external $refs stay unresolved.
Waiting for a schema
Paste a JSON Schema document.
JSON Schema Inspector runs entirely on your device — nothing is uploaded, and no external reference is fetched.
You’re on the Free plan. Compare plans
`required` is the keyword schemas most often get wrong, because of where it lives. It is a list of property *names* held on the object, not a flag on each property — so adding a property to `properties` without adding its name to `required` leaves it optional, silently, and validation passes on a payload missing it.
`additionalProperties` defaults to true, which means a schema listing three properties accepts a payload with thirty. Authors who believe they have written a closed schema have usually written an open one, and the finding says so.
`nullable` is not a JSON Schema keyword at all — it is an OpenAPI 3.0 extension. In JSON Schema you write `"type": ["string", "null"]`, and OpenAPI 3.1 does the same because 3.1 aligned with JSON Schema. A `nullable: true` in a plain schema does nothing, and is reported rather than honoured.
The example generator produces an instance that satisfies the schema, which is the quickest way to check that the schema says what you meant. A schema that generates an example you would not accept is a schema with a problem.
Nothing is fetched, so an external `$ref` is listed as unresolved rather than followed, and the node it sits on says which reference could not be read.
Because `required` is a separate list of names on the object, not a flag on the property. Adding to `properties` without adding the name to `required` leaves it optional, and validation will pass without it.
Only if you set `additionalProperties: false`. The default is true, so a schema listing three properties happily accepts thirty. This is the most common gap between what a schema author intended and what the schema says.
`"type": ["string", "null"]` in JSON Schema and in OpenAPI 3.1. `nullable: true` is an OpenAPI 3.0 extension only — in a plain schema it is an unknown keyword and is ignored.
No. Nothing is fetched, so a reference to another file or a URL is listed as unresolved on the node that holds it. Bundle the schema first if you need the whole thing.
It reports structural problems and keywords that will not do what they appear to. It does not validate an instance against the schema, and it is not a substitute for a validator in your pipeline.