Free, browser-based utilities for everyday developer workflows

Validate JSON Against a Schema

Check API payloads against a JSON Schema and get precise error paths. Auto-generate a schema from sample JSON to get started quickly.

Try it now

Open JSON Schema Validator with a ready-to-run example.

Try it now
When you need this
  • A QA engineer needs to confirm that an API response matches the documented contract.
  • You are writing integration tests and want to validate response shapes without writing code.
  • A third-party webhook is sending payloads and you need to confirm required fields are present.
  • You have a JSON Schema from an OpenAPI spec and want to test it against a real payload.
How to do it with Daily Developer Tools
  • Paste your JSON payload in the left panel and your JSON Schema in the right panel.
  • Click Validate — errors are listed with their exact JSON Pointer path and a human-readable message.
  • If you don't have a schema yet, paste your JSON and click Infer Schema to auto-generate a starting draft.
  • Refine the schema by adding required, format, and minimum/maximum constraints as needed.
Tips / common pitfalls
  • Add "additionalProperties": false to catch unexpected fields in strict validation scenarios.
  • Use "required": ["field1", "field2"] at the object level — a field being in properties does not make it required.
  • JSON Schema draft-07 uses definitions; draft 2019-09+ uses $defs. Check which version your toolchain targets.
  • Error paths use JSON Pointer notation: /user/0/email means the email field of the first element in the user array.
Examples & test data

User object with missing required field

JSON payload
{
  "id": 42,
  "name": "Alice"
}
JSON Schema
{
  "type": "object",
  "required": ["id", "name", "email"],
  "properties": {
    "id":    { "type": "integer" },
    "name":  { "type": "string" },
    "email": { "type": "string", "format": "email" }
  }
}
Validation result
INVALID
Error at /: must have required property 'email'
FAQ
What version of JSON Schema is supported?

JSON Schema draft-07 and draft 2019-09 via AJV. This covers $ref, allOf, anyOf, oneOf, if/then/else, and string format validation.

What do the error paths mean?

Errors use JSON Pointer notation (RFC 6901). /user/0/email means the email field of the first item in the user array. Each error also includes the failing keyword and expected value.

Can I auto-generate a schema?

Yes. Paste your sample JSON and click Infer Schema to generate a draft-07 compatible schema. Edit it to add required constraints, enums, and format validators before using it in production.

i Privacy-first: runs locally in your browser. No uploads.

How to validate JSON against a schema

Paste the JSON payload on the left and the JSON Schema on the right, then click Validate. The tool uses AJV to run full draft-07 or 2019-09 validation and returns a list of errors with JSON Pointer paths indicating exactly which fields failed and why.

Common use cases

QA engineers use this to validate API responses against OpenAPI component schemas during manual testing. Backend developers use it to test their schema definitions before adding AJV to their CI pipeline. Technical writers use it to verify that the example payloads in their documentation actually conform to the schema they have documented.

Why run this in your browser?

All processing happens locally in your browser. Your data never leaves your machine, making it safe for sensitive payloads, internal API responses, and confidential configurations.