JSON formatting, validation and conversion tools
Format, validate, query, convert, and generate types — one JSON workflow.
JSON is the format you touch most and think about least — until a payload won’t parse or needs to become something else. This workflow covers the full lifecycle: beautify it so it’s readable, validate it against the spec with precise error positions, query nested values with JSONPath, convert it to TypeScript, CSV, or YAML, generate a Zod or JSON Schema from it, and minify it for transport. Everything runs locally in your browser.
- 1
Format and beautify
Turn a minified or messy blob into indented, readable JSON — the first step to understanding any payload.
- 2
Validate against the spec
Confirm the JSON is well-formed and get the exact line and column of the first error, so you can fix a stray comma or unquoted key fast.
- 3
Query nested values
Use JSONPath to extract just the fields or array elements you need from a deeply nested document.
- 4
Convert to another format
Re-emit the same data as TypeScript types, CSV for a spreadsheet, YAML for config, or convert from CSV or XML back into JSON.
- 5
Generate types and schemas
Produce a TypeScript interface, a Zod schema for runtime validation, or a JSON Schema contract directly from a sample document.
- JSON to TypeScriptGenerate TypeScript interfaces from JSON
- Zod Schema GeneratorSmart JSON-to-Zod: merges array samples for optional/nullable/enum/format inference, emits the z.infer type, and validates any payload live
- JSON Schema GeneratorGenerate a JSON Schema (Draft 2020-12 / draft-07) from a JSON sample with array-merge required-key, enum & format inference + a live validator
- 6
Minify for transport
Strip whitespace to shrink the payload for an API response or an embed once you’re done editing.
Frequently asked questions
Paste a representative JSON sample into a JSON-to-TypeScript tool and it infers an interface from the keys and value types. Refine the result by marking optional fields, replacing loose unions, and adding runtime validation with a Zod schema if the JSON comes from an untrusted source like an API.
Formatting re-indents JSON to make it readable but assumes it’s already valid. Validating checks that it actually conforms to the JSON spec and reports the exact position of the first syntax error. When a payload won’t parse, validate first to find the problem, then format once it’s clean.