JSON Schema Validator
Paste your data and your schema, and get a list of every place the data breaks the rules, with a path and the keyword that failed. Nothing leaves your browser.
- No usage limits
- Your data stays local
- Every error listed
- Data stays in your browser
- Runs on your device. Files are never uploaded.
- Free and unlimited. No sign-up, no watermark.
JSON schema validator in three steps
No account, no email, no waiting for an upload.
- STEP 01
Paste your JSON data
Add the document you want to check in the first box.
- STEP 02
Paste your JSON Schema
Add the schema in the second box. The draft is read from its $schema line; without one, 2020-12 is assumed.
- STEP 03
Read the verdict
You get Valid, or a list of errors, each with a path, a message and the keyword such as required or type.
What JSON schema validator does, and what it doesn't
We'd rather tell you up front than surprise you after the download.
What you get
- Five draftsSupports draft 4, 6, 7, 2019-09 and 2020-12, chosen from your $schema value.
- Common keywords coveredTypes, enum, const, ranges, lengths, patterns, items, properties, required, allOf, anyOf, oneOf, not, if/then/else, dependencies and unevaluated keywords.
- Local references$ref works for #/$defs/... and #/definitions/..., and for schemas inside your file that have an $id or an $anchor.
- Format checksFormats such as date-time, date, email, uri, uuid, ipv4 and ipv6 are checked. Unknown formats are listed instead of silently passing.
- Honest about gapsKeywords the tool does not check are named in the report, so a pass is never overstated.
Good to know
- No remote $refA reference to another file or URL cannot be loaded. Copy that schema into $defs and point to it with #/$defs/name.
- Not a standards test suiteThis is a compact validator written for the browser. If a rare keyword matters to you, confirm in your production library.
- Up to 500 errorsVery long lists are cut at 500. Fix the first batch and run again.
Your data never leave your device
The tool runs inside your browser instead of on our servers, so there is nothing to upload, store or delete afterwards.
Typical online tool upload
Your file travels over the internet, sits on someone else's computer for a while, and you wait for the upload and the download.
Mediaextractr no upload
The tool loads into your browser once, then works on your file locally. Nothing is sent, so nothing can leak.
When people use JSON schema validator
Test an API contract
Check a sample request or response against the schema before writing code.
Check a config file
Confirm a settings file has the required keys and the right types.
Validate an import
Run a JSON export through a schema before loading it elsewhere.
Learn schema keywords
Try a keyword and see which message appears when the data fails.
Mediaextractr vs typical upload tools
| MediaextractrPrivate | Typical upload tools | |
|---|---|---|
| Your file is uploaded | Never | Yes |
| Sign-up needed | No | Often, after a few files |
| Daily file limit | None | Often 1–2 free files |
| Watermark | Never | Sometimes |
| Wait for upload & download | No | Yes |
| Speed on very large files | Depends on your device | Depends on their servers |
Reading the error list
Each line has a path, a message and a keyword in brackets. The path starts at $ and shows where in the data the problem is, for example $.items[2].price. The keyword tells you which rule failed: type, required, minimum, pattern, and so on.
At the bottom, the report states the schema version it used and any formats or keywords it did not check.
Writing a schema from scratch
Do not start from a blank page if you already have sample data:
- Generate a first draft with the JSON schema generator.
- Tighten it by hand: add required, minimum, enum and pattern.
- Make sure the data is valid JSON first with the JSON validator.
- Types for code can come from JSON to TypeScript.
Which draft should I pick?
Put a $schema line at the top of your schema and the tool follows it. If your tooling is older, draft 7 is widely supported. If you are starting fresh, 2020-12 is the current version. Newer drafts rename a few keywords, for example prefixItems replaces tuple-style items.
Questions, answered
Which JSON Schema drafts are supported?
Draft 4, 6, 7, 2019-09 and 2020-12. The tool picks one from $schema and falls back to 2020-12.
Are internal schemas and data safe to paste?
Yes. Validation is carried out by a validator that runs inside your browser, so neither the schema nor the sample data is sent out.
Why does it say a $ref cannot be loaded?
The reference points to another file or URL. Browsers cannot fetch it here, so move that schema into $defs in the same file.
Are formats like email enforced?
Yes, known formats are always checked. Formats the tool does not know are listed as not checked.
How many errors will I see?
Every error up to 500. After that the list is cut.
Is it supported on tablets and phones?
Yes, on current Safari, Chrome, Edge and Firefox, including iOS and Android. Long error lists scroll within the result area.