DEVELOPER TOOLS · VISUAL WORKSPACE

JSON Schema Studio

Create nested JSON schemas, set constraints, generate example data, and inspect validation results—all in one local-first workspace.

2020-12JSON Schema dialect

0Schema nodes

0Required fields

SCHEMA DESIGNER

Customer profile

Add fields and rules to your data contract

Ready

Choose a field to edit. Nested objects and arrays appear in the outline.

TEST YOUR SCHEMA

JSON data validator

Paste a JSON document or import a .json file. To validate records independently, select “Each array item”. Errors include JSON Pointer paths.

Input JSON

Validation mode Basic format assertions (email, URI, UUID, dates) Remember test data in this browser

Draft 2020-12 treats format as annotation by default. Optional format checks are basic and not full standards conformance.

VALIDATION RESULTS

Diagnostics

Run validation to see results.

How validation works

This studio validates a documented Draft 2020-12 keyword subset locally. It does not claim complete 2020-12 conformance. Unsupported schema keywords or external references stop validation with an explicit message, rather than returning a misleading pass.

SCHEMA SOURCE

Review & edit JSON Schema

Edit the underlying schema directly. Advanced keywords stay intact on import and export. Applying source changes replaces the visual editor’s current schema after confirmation.

DOCUMENTATION

Capabilities and limits

Supported validation groups

Types, enums, numeric and string bounds, arrays, object properties, local JSON Pointers, required fields, composition (allOf/anyOf/oneOf), conditions and dependencies.

Not a full JSON Schema engine

External references, dynamic references and unevaluated keywords are not validated. Complex regular expressions may be rejected for safety; validate production schemas with a fully conforming implementation.

Privacy and exports

Inputs are processed in this tab. Your schema is saved locally. Test data is only saved in local storage when you opt in. Download the project to make a portable backup.

Using JSON Schema Studio

Create or import a schema, edit supported constraints and local definitions, then apply source changes. Validate supported JSON or a bounded batch and inspect diagnostics before exporting reports. Save a portable project only after reviewing its included test data.

The bundled validator implements a declared Draft 2020-12 subset, not full standards conformance. Unsupported assertions block validation and external references are not fetched. Regex heuristics do not enforce a hard execution timeout. Test-data draft storage is opt-in, but portable projects include current test JSON. Size, depth, batch and diagnostic budgets apply.

Choose a schema, validation report or data-bearing project

Schema export: share the supported schema and local definitions.

Project JSON: preserve the schema with current test JSON and supported editor settings.

JSON/CSV reports: review supported diagnostics for the tested data and declared subset.

Draft storage: choose test-data persistence separately from what portable project export includes.

Practice: test a required string property

Define an object schema with a required string property named name.

Compare the fictional test objects {"name":"Draft"} and {"name":3}, inspecting the diagnostics for the declared type.

Review included test data before exporting the portable project.

This is an authored validation exercise, not executed test output or a standards-conformance claim.

Schema validation questions

Will every Draft 2020-12 schema validate here?

No. The validator implements a declared subset. Unsupported assertions block results, external references are not fetched, and regex heuristics do not provide a hard execution timeout.

Does disabling browser test-data storage remove it from exported projects?

No. Portable projects include the current test JSON even when draft-data storage is not opted in. Export the schema alone when that is the intended handoff, and inspect any project for private values.