JSON Schema validator
Validate a JSON document against a JSON Schema (draft-07) and get a list of every property that breaks the rules.
- Runs in your browser
- No upload
- Result stays on your device
Privacy & limitsRuns in your browser. Nothing is uploaded.
Input content stays in this tab; Refentra does not upload or store it. Optional aggregate action counts are sent only with your usage consent. Clear the workspace when finished.
Supported profile: Draft-07 bounded profile: types, bounds, objects, arrays, enum/const, logic, local acyclic refs. Unsupported keywords fail. Numbers use IEEE-754; integers must be safe and finite. multipleOf uses exact divisibility of the parsed number’s canonical decimal representation; no tolerance is enlarged for large values. Numbers must round-trip their decimal meaning. Unsafe integers, overflow, underflow or unsupported decimal precision are rejected before output.
Maximum text: 200,000 UTF-16 units; parser limits can be smaller. Worker time limit: 15 seconds (regex 1.5 seconds).
Check the input and the result
- Prepare and choose the operation
Put the instance and the schema in their separate fields, and include required properties and additionalProperties rules explicitly.
- Check a concrete example
Use this sample and compare the indicated result: {"count":2} + {"type":"object","properties":{"count":{"type":"integer","minimum":1}},"required":["count"],"additionalProperties":false} → valid=true; {"count":0} → errors[].keyword="minimum"
- Check the output before you reuse it
Use each error’s instance path and keyword to find the failing value, then either change the data or revise the schema on purpose.
Answers for this task
Does valid mean the data is trustworthy?
Validation only confirms the schema constraints that are accepted. An allowed string can still be false, malicious or unsuitable for your application.
What should I check if the input fails?
First make both fields strict JSON. A schema compilation error is different from a valid schema that rejects the instance.
Where does this tool stop?
Remote references are not fetched. Use the supported local schema dialect, and don't assume that every JSON Schema draft or format is available.