
JSON Schema: Validate Data Online (Draft 2020-12)
Test API payloads and config files against JSON Schema Draft 2020-12 — errors pinpointed by JSON Pointer path, in the browser.
Validating JSON data against a schema
Valid JSON is not the same as valid for your API. A payload can parse perfectly. It can still miss a required field, ship the wrong type, or violate a format constraint. Those bugs often surface only in integration tests or production logs. JSON Schema answers a different question than syntax checking: does this instance conform to the contract? FastMinify's online JSON Schema validator runs Draft-07 and 2020-12 validation in two Monaco editors (schema and instance), entirely in your browser. If the syntax is in doubt, start with the JSON validator. If the contract lives in OpenAPI, use validate-openapi. The API tools hub lists the schema conversion and OpenAPI linting tools.
Honest limits and maintainable schemas
A green result means the instance matched the pasted schema, not that your entire API platform is compliant.
$ref values, including https:// ones, never resolveSchemas that validate cleanly in the browser tend to survive CI and SDK generation.
$schema in shared files, to avoid implicit 2020-12 assumptionsadditionalProperties: false only when you enforce closed objects deliberatelyexamples in OpenAPI and paste them as validator instances in reviewsdescriptionBrowser checks save pipeline minutes; org policy still lives in CI.
JSON syntax vs JSON Schema validation
Do not swap tools mid-debug; each answers a distinct failure mode.
FastMinify detects the draft from $schema when present; missing $schema defaults to 2020-12.
https://json-schema.org/draft/2020-12/schemahttp://json-schema.org/draft-07/schema#components.schemasWhen validation fails, Ajv reports where the instance broke the schema, which is essential for large API payloads.
instancePath points to the failing value (JSON Pointer style)required, type, format, …)required schema → path / or missing property pathsValidate JSON against a schema, step by step
The JSON Schema validator provides two editors: Schema on the left and Instance on the right. Paste JSON into each field. YAML is not accepted in the schema editor, which takes JSON only. The limit is 512 KiB per field.
Strict mode turns on Ajv strict: true at schema compile time, so unknown keywords and other non-strict schema patterns fail before instance validation.
components.schemasYour mobile client crashes on a new field shape. The response is valid JSON but breaks the published schema.
Confirm the JSON syntax
Paste the response into json-validator. If syntax fails, repair before schema validation.
Paste the schema and the instance
Open json-schema-validator. Paste the canonical schema (from an OpenAPI export or a schema registry) and the staging response.
Read the instancePath errors
Fix the API or update the schema with a deprecation plan. Re-validate after deploy. Optionally diff staging against production payloads.
A team shares a JSON config validated in CI with JSON Schema, and you need a quick local check without cloning the pipeline.
Load the schema from the repo
Copy the schema JSON. It must be self-contained, because external $ref are not resolved in the browser.
Validate your edit
Paste the edited config as the instance. Enable Strict if the schema is authored for strict review.
Chain with the YAML tools if needed
Configs often start as YAML. Convert with yaml-to-json, validate the syntax, then schema-validate the JSON instance.
OpenAPI, components.schemas, and conversion
REST teams often publish shapes in OpenAPI components.schemas, while JSON Schema registries store standalone files. The validator accepts either once extracted as JSON. The workflow starts with validate-openapi for the spec envelope, extracts the schema, then checks the payload against it with json-schema-validator. See our OpenAPI validation guide and lint & format guide for the spec side of the contract.
When the schema source is the OpenAPI file, you can pivot formats on the hub without a local CLI. Use openapi-to-json-schema to extract a schema from OpenAPI components. Use json-schema-to-openapi to wrap a standalone schema into an OpenAPI shell for portal import.
Browser validation speeds up feedback, while CI still owns regression suites. Paste representative instances: the happy path, edge nulls, and enum boundaries. Document the draft in $schema next to every shared schema file in git.
Common validation failures
These show up constantly in support tickets and flaky CI jobs.
required property: instancePath points at the parent or /type, such as a string where an integer is expected (common after form serialization)additionalProperties: false catches extra fields from API versioning mistakesformat violations such as date-time, email, or uuid (through ajv-formats)enum mismatch from undocumented status codes or region codes in payloadsStrict mode and unsupported drafts surface here before instance validation runs.
$schema URL: upgrade to Draft-07 or 2020-12$ref is a hard error, so inline or bundle refs locally firstdescription or vendor extensions, depending on policyConclusion
JSON Schema validation closes the gap between JSON that parses and trustworthy API data. Start with syntax when needed, then validate instances against Draft-07 or 2020-12 schemas with clear instancePath errors, locally before CI. Extract schemas from OpenAPI when contracts live in specs, and keep browser checks honest about refs, drafts, and size limits.
Validate your JSON instance against a schema now
Related Articles

Paste a token and a JWKS to check an RS256, ES256 or HS256 signature in your browser. How kid picks the key, measured errors and the claims to check.

HTTP/2 and HTTP/3 change how files travel, not how big they are. Measured sizes, compile times and bundling tests show what minification still saves.

Convert a Unix epoch to a readable date and back, tell seconds from milliseconds, and avoid time zone, JWT and clock change traps, all in your browser.