wyreup
inspect

JSON Schema Validate

Validate a JSON document against a JSON Schema. Built on ajv — supports draft-07 by default, with all errors listed at full JSON-Pointer paths so you can pinpoint the failing field.

Loading…

About JSON Schema Validate

JSON Schema Validate checks a JSON document against a JSON Schema and tells you exactly where it fails. Built on ajv with draft-07 by default, it lists every error at its full JSON-Pointer path so you can jump straight to the offending field instead of guessing. It runs entirely in your browser, which means you can validate config, API payloads, or fixtures without sending any of it to a server.

Category
inspect
Input
Accepts: application/json or text/plain.
Output
Outputs: application/json.
Cost
Free, runs in your browser
Memory
low
Privacy: JSON Schema Validate runs entirely on your device. Files you provide never leave your browser — no uploads, no server, no tracking. The page works offline once loaded.

Common uses

  • Verify an API request or response body conforms to your OpenAPI-derived schema before shipping
  • Validate a tool or app config file against a schema in CI-style spot checks during development
  • Pinpoint which array element fails by reading the JSON-Pointer path like /items/3/price
  • Confirm a third-party webhook payload matches the contract you were promised
  • Test edge-case fixtures against a schema while writing validation logic
  • Check that hand-edited JSON still satisfies the schema after a quick manual change

Frequently asked questions

Which JSON Schema drafts are supported?

It defaults to draft-07, the most widely used version, and is powered by ajv under the hood.

Does it stop at the first error?

No. It collects all validation errors and reports each one at its full JSON-Pointer path, so you can fix everything in one pass.

Is my JSON sent to a server?

No. Both the document and the schema are validated locally in your browser, so nothing is uploaded.

Can I paste plain text instead of a .json file?

Yes. It accepts application/json and text/plain, so pasted JSON works as long as it parses.

What does the output look like?

You get a JSON result indicating validity plus an array of any errors, each with its path and a human-readable message.

Keywords

  • json
  • schema
  • validate
  • ajv
  • jsonschema
  • draft-07
  • openapi

Try next

JSON Schema Infer
inspect

Generate a starter schema from a sample document, then validate against it here.
JSON Formatter
inspect

Pretty-print and sanity-check your JSON before validating it.
JSON ↔ YAML
dev

Convert YAML configs to JSON so you can validate them against a JSON Schema.
Color Palette
inspect

Extract dominant colors from an image as hex codes.
Image Diff
inspect

Pixel-level diff between two images of the same dimensions.
Image Info
inspect

Extract dimensions, format, and metadata from an image.
PDF Info
inspect

Extract page count and metadata from a PDF.
Hash
inspect

Compute SHA-256, SHA-1, or SHA-512 hashes of files.
JSON Formatter
inspect

Parse and pretty-print JSON with configurable indentation.
Extract PDF Tables
export

Extract tabular data from a PDF as JSON or CSV. Works well for simple tables with aligned columns and no merged cells. Complex tables, rotated text, and scanned PDFs (images) will not extract cleanly.
Topic Keywords
text

Pull the topic-bearing nouns and noun phrases out of any text. Answers "what is this about" — not "what words appear most" (try Text Frequency for that). Runs entirely in your browser.