JSON Schema validate
Validate a JSON document against a JSON Schema.
Working…
Questions people ask
- Which file is the schema?
- The first file you add. The list under the drop zone shows the order: schema first, then the document to check. Both may be up to 4 MB.
- Which drafts are supported?
- Draft 2020-12 (the current standard), plus the bundled 2019-09, draft-07, draft-06 and draft-04 validators when the schema declares its own $schema. Other $schema values are validated under 2020-12 and labelled as such.
- Are $refs and $defs supported?
- Internal references (the same document: $defs, $id resolution, relative pointers) resolve exactly as the reference implementation does. References that would leave the document (remote URLs and file paths) are prohibited and refused with an explicit diagnostic; nothing is ever fetched.
- Does it enforce the format keyword (email, date, uri)?
- No. Under Draft 2020-12, format is an annotation by default and the tool does not add external format libraries. All structural keywords (type, enum, const, min/max, required, pattern, oneOf, prefixItems, unevaluated*…) are asserted.
- What happens when my document is invalid?
- That is a successful validation run: the verdict is "invalid" and the report lists each failure with the instance path (JSON Pointer), the schema path it came from, and the standard's own message. A failing oneOf/anyOf includes the first three failing branches.
- What if my schema or document is broken?
- Distinct diagnostics, distinct reasons: not-valid JSON (with line/column), a schema that fails its own meta-schema, an unresolvable $ref, or nesting beyond 200 levels. Nothing is half-validated and nothing is made up.
- How are pathological schemas handled?
- Documents nest at most 200 levels (the validator recurses with the instance depth), errors are capped at 1 000 with a truncated flag, and the job runs in the same resource-capped, network-less isolation as every tool on this platform.
- What happens to my files?
- Both files are removed as soon as processing finishes; the report is available for about 10 minutes, then automatically deleted.