JSON Toolkit

Free online tools to format, minify, diff, convert, validate, and inspect JSON in your browser. Includes JSON/YAML/XML/CSV/Excel/TypeScript conversion, JSON Schema, JSONPath, and JWT tools. All processing runs locally in your browser with no upload required.

All processing runs locally in your browser. Input data is not uploaded to a server, which helps with sensitive data.

Popular JSON tools

JSON FormatterFree online JSON / JSONC / JSON5 formatter to format, minify, and validate data with comments, trailing commas, tree view, and node operations JSON Repair / CleanFree online JSONC / JSON5 repair tool for comments, trailing commas, single quotes, unquoted keys, and other common JSON issues JSON ↔ YAMLFree online JSON to YAML and YAML to JSON converter JSON → TypeScriptFree online tool to infer and generate TypeScript interface types from JSON / JSONC / JSON5 Regex TesterFree online regular expression tester with flags, named groups, highlighted matches and common templates Timestamp ConverterFree online Unix timestamp and date converter with second, millisecond, microsecond precision and multiple time zones UUID GeneratorFree online UUID v1 / v4 / v7 and NanoID generator with batch output, case toggle and hyphen removal Color ConverterFree online color format converter between HEX, RGB, HSL, HSV, CMYK with a live swatch preview JWT ParserFree online JWT parser to decode tokens, inspect Header / Payload, and verify HS256 signatures

All JSON tools

What this category is for

These tools all serve one goal: turning JSON from machine-readable into something you can read, edit and verify. Debugging an API mostly means formatting and minifying; config files often need comments and trailing commas repaired; integration work means converting between JSON, YAML, XML, CSV and Excel; and diagnosing a production issue usually comes down to diffing two responses or pulling one field out with JSONPath.

All parsing happens in your browser, so you can paste a real response containing tokens, phone numbers or order IDs without redacting it first for some online service.

Choosing between these tools

You just need to see the structure: Use JSON Formatter. It accepts strict JSON, commented JSONC and JSON5 alike, and renders a collapsible tree; the fastest way to find a field inside a single-line response.
The text will not parse at all: Start with JSON Repair. Comments, trailing commas, single quotes, unquoted keys and escape backslashes picked up from log lines are all its job. Fix it there, then hand the result to the other tools.
You need a different data format: JSON ↔ YAML suits config files, JSON ↔ XML suits legacy APIs, JSON → CSV / Excel hands an array to non-technical colleagues, and JSON → TypeScript freezes a response into a type.
You need to validate, not just view: JSON Schema Generator infers constraints from a sample, JSON Schema Validator checks data against those constraints and reports error paths, JSONPath Query extracts deep fields by expression, and JSON Stats reports depth, key count and type distribution.

Formats and capabilities compared

What the same document gains or loses in each target format; usually the deciding factor when picking a conversion tool.

Target format	Structure	Types	Typical use
YAML	Nesting fully preserved	Preserved, plus comments and anchors	Service config, CI pipeline definitions
XML	Preserved, but arrays need an agreed wrapper element	Everything becomes text; needs a schema to constrain	Integrating with legacy and SOAP systems
CSV / Excel	One level only; nesting is flattened or dropped	Everything becomes cell text	Handing data to colleagues who filter and sort in a spreadsheet
TypeScript interface	Structure becomes a type definition	Inferred; optionality needs a human check	Letting the compiler catch misspelled fields

Limits that apply across this category

JSON numbers parse as JavaScript numbers, which represent integers exactly only up to 2^53-1. Snowflake IDs, order numbers and account balances should travel as strings at the transport layer, otherwise any JavaScript-based parser loses the last digits. That is a property of the format and the language, not a defect in one tool.

Conversion is lossy. Comments, metadata beyond key order, XML attributes and namespaces, and CSV types do not necessarily survive a round trip. Keep the original file before you use a converted result in a real process.

FAQ

Does JSON Toolkit upload my data?

No. Formatting, conversion, analysis, JWT parsing, and file processing run locally in your browser. The server does not receive your input.

Which JSON-related formats are supported?

JSON, YAML, XML, CSV, Excel, TypeScript interfaces, JSON Schema, JSONPath, and JWT are supported. Image compression, background removal, and format conversion are available from the top image toolbar.

Are these tools free to use?

Yes. All tools are free to use online, require no account, and run directly in your browser.

Does the JSON formatter support loose syntax?

Yes. It accepts common loose input such as unquoted object keys and single-quoted strings for faster debugging.