JSON Schema validator

Check JSON syntax or validate catalogue records against your supplied Draft-07 schema. Your files stay in your browser.

Your JSON

Paste up to 500,000 characters. Your source text stays unchanged.

UTF-8, up to 2,000,000 bytes. Replaces the text above.

Validation mode

Your schema

Dialect: JSON Schema Draft-07

Draft-07 only. Format keywords are annotations.

UTF-8, up to 2,000,000 bytes. Replaces the schema above.

Optional, up to 19 files. Remote schemas are never downloaded.

Validation result

Does not conform

Draft-07 rules. Format keywords are annotations.

Check details

JSON syntax
Valid JSON
Schema rules
Valid Draft-07 schema

Example: valid JSON syntax with required, type and enum failures.

Validate JSON against your schema

This JSON Schema validator checks a local catalogue document against your supplied Draft-07 schema, entirely in your browser. Paste JSON or choose a local file, then select the validation mode.

Syntax only checks whether the text is valid JSON. It works without a schema and reports the line and column where parsing stops. A syntax pass says nothing about required fields or correct prices.

With schema first checks JSON syntax, then validates the schema rules before checking the document. Invalid schema JSON, invalid schema rules and a document that fails those rules have separate results.

The tool reads your values without correcting or rewriting them. Keep identifiers such as "000123" in quotes to preserve leading zeros. Files and pasted text remain on your device and are not saved between visits.

Read errors at the field that failed

Each conformance error shows an instance path, a failed keyword and the expected rule. The output reports failed locations without displaying other catalogue records.

A path such as /products/1/price means the price in the second product. Array positions start at zero. A slash in a field name becomes ~1, and a tilde becomes ~0.

  • required names a missing field at its containing object.
  • type reports an expected value type, including rules on array items.
  • enum limits the value to the choices in your schema.
  • additionalProperties restricts fields beyond those allowed by your schema.

Fix the most specific field errors before reading the parent messages from combined rules. The output shows up to 100 errors per check. Correct those errors and check again to reveal any remaining failures.

Fix a catalogue record step by step

The hypothetical shirt record loaded in the tool has three faults under its supplied schema. It omits sku, writes the price as text and uses available outside the allowed availability choices.

  1. Add "sku": "SHIRT-001" to satisfy the required identifier rule.
  2. Change "price": "79" to "price": 79. The schema requires a number.
  3. Replace "available" with "in_stock", one of the schema’s allowed values.

Paste the corrected record into JSON text and keep the original schema. The result becomes Conforms to schema. Changing the schema to permit a text price would change the agreed import rules instead of correcting the record.

Use local references and known format rules

This tool supports JSON Schema Draft-07. A schema can declare that dialect with $schema or use the fixed Draft-07 setting. Other declared dialects and later-dialect keywords stop the conformance check.

The official JSON Schema dialect guidance explains how a schema declares its rules. Schema validity is checked against a bundled Draft-07 meta-schema.

Choose local reference files for rules shared across schemas. A reference such as price.json resolves against the main schema’s filename or $id. Files with an explicit $id must match the identifier used by the reference.

For example, a main schema containing {"$ref":"price.json"} can use a selected price.json containing {"type":"number"}. The JSON value 79 passes, while "79" fails.

As the JSON Schema reference guide explains, an identifier can look like a web address without requiring a download. Supply the matching local schema for an absolute identifier. A missing file or fragment stops the check, and the tool never fetches a remote resource.

format keywords are annotations in this tool. For example, format: email does not reject an invalid email address. Rules such as type, pattern and enum still apply.

Each document allows 500,000 characters and 128 nesting levels. Schema files allow 2,000,000 characters in total, with at most 20 files including the main schema. A check stops after 10 seconds.

Conformance checks stop when a number exceeds the browser’s safe numeric range. Use quoted identifiers and check exact financial precision in your import system. A schema pass establishes the supplied shape rules, while real stock and prices still need checking against the catalogue source.