Build and edit JSON Schema documents visually with type definitions, validations, and live preview.
JSON Schema Editor assembles a schema document from visual choices about the root type, named properties, nested structures, and validation constraints. Each change appears in a live JSON preview, letting you inspect the keywords and hierarchy that describe acceptable JSON instances. It edits the contract, not the instance data. The most common surprise is that adding a field under `properties` does not make it mandatory; required property names must be declared separately on their containing object.
The visual controls define a schema tree rather than an example data tree. Selecting an object creates an object schema; adding named fields places child schemas beneath `properties`. A field's selected JSON type and validation values become keywords on that child schema. The live preview lets you inspect the resulting nesting and keyword values as you edit.
Requiredness is recorded at the parent object level. When a property is marked required, its name belongs in the parent's `required` array; it is not a flag inside the property's own schema. Array item rules belong under `items`, while string and numeric constraints remain on the schema node they constrain. Read the preview by following that hierarchy.
No. A schema under `properties` constrains that member when it is present. To require it, include its exact name in the containing object's `required` array. Spelling and case must match. An optional field can therefore be fully typed and constrained while still being absent from a valid instance.
Not necessarily. Validators support particular JSON Schema drafts and vocabularies. A keyword from one dialect may be rejected or interpreted differently by a consumer configured for another. Check the `$schema` identifier, if present, and the validator's documented draft support. Also confirm whether that consumer treats `format` as an assertion or only as an annotation.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.