Question 1

What is JSON Schema and why do I need it?

Accepted Answer

JSON Schema is a vocabulary that lets you describe the structure and constraints of JSON data, types, required fields, value ranges, string patterns. It's the standard way to validate API requests/responses, OpenAPI specs, configuration files, and form inputs. Having a schema turns 'is this JSON valid?' into a deterministic check rather than runtime guesswork.

Question 2

Which JSON Schema draft does the generator use?

Accepted Answer

Draft 2020-12, the latest stable specification. It's a superset of older drafts for common use, so generated schemas are also accepted by most Draft 7 validators with minor adjustments (the $schema URL changes and a few keyword names differ).

Question 3

How does format detection work?

Accepted Answer

After inferring the basic type, the generator runs a series of regex checks against string values: emails match RFC 5321 pragmatic patterns, URIs check for protocol + host, UUIDs match the 8-4-4-4-12 hex shape, date-times match ISO 8601, and IPv4 matches dotted-quad. Detected formats are added as 'format': 'email' (etc.) to the schema.

Question 4

Are all keys marked as required?

Accepted Answer

By default, yes, every key present in the sample is added to the 'required' array. This is the safest default for API contracts. If your real schema has optional fields, edit the generated 'required' list to remove them. You can also paste multiple sample documents (as an array) so the generator can detect which fields appear in some but not all.

Question 5

How are arrays handled?

Accepted Answer

Arrays get an 'items' subschema inferred from the first non-empty element. If your array is heterogeneous (mixed types), the inferred schema may be too narrow, generated as a union (anyOf) only when the generator sees obviously different shapes. Hand-tune for complex polymorphic arrays.

Question 6

Can I generate a schema from multiple samples?

Accepted Answer

Yes, wrap your samples in a JSON array and the generator infers the union of structures: keys that appear in some samples but not others are marked optional, types that vary across samples become unions. This produces a more accurate schema than a single sample for production APIs.

Question 7

Is my JSON sent to a server?

Accepted Answer

No. Schema generation is pure JavaScript running in your browser. Your sample JSON, including any PII, secrets, or proprietary fields, never leaves your machine. Verify with DevTools → Network.

Question 8

What standards does JSON Schema Generator validate against?

Accepted Answer

JSON Schema Generator checks compliance with JSON Schema (draft 2020-12), RFC 8259 (JSON).

Question 9

What are the limitations of JSON Schema Generator?

Accepted Answer

Inference is heuristic, may not capture all constraints Does not generate descriptions or titles Array item types are inferred from first element

JSON Sample	Inferred Schema Type	Standard Format
`"2024-05-16"`	`string`	`date`
`42`	`integer`	N/A
`42.5`	`number`	N/A
`"https://..."`	`string`	`uri`

JSON Schema Generator

Privacy note

How to Use JSON Schema Generator

Paste JSON Sample

Generate Schema

Copy Schema

JSON Schema Generator: the essentials

Key points

Learn More

JSON Schema Validation: Stop Trusting API Responses Blindly

Stop Hand-Writing Your Types: The Engineering Case for JSON-to-Type Codegen

Stop Trusting LLM JSON: Validate AI Outputs with Zod in 5 Minutes

What is JSON Schema Generator?

Frequently Asked Questions

Technical Deep Dive

JSON Schema Generator

Draft 2020-12 output

Tunable strictness

No upload

01 Type & Format Mapping

02 Inference Engine Logic

Runs 100% in your browser

You Might Also Need

Git Commit Message Generator

Regex Explainer

AI Code Review Assistant

API Client Code Generator