THE JSONWORKBENCH GUIDE

Make JSON easier to read
without losing the details.

A tidy document is easier to inspect, compare and share. Start with a small example, understand the validation result, then choose the output that suits your task.

1. Begin with a complete JSON value

JSON is a text format for structured data. A document can contain an object, an array, a string, a number, a boolean or null at its root. Object keys and string values require double quotes. An API response such as the following is a good starting point:

{"name":"North Desk","active":true,"tags":["support","billing"]}

Paste your text into JSON input, or open a UTF-8 .json file. Opening a file reads it locally; it does not upload the contents. The input limit is 2 MiB, measured as UTF-8 bytes. Non-English characters may use several bytes each. UTF-8 files with a byte-order mark are rejected, so save them without a BOM.

2. Validate before you edit

Select Validate only to check syntax and see the structural summary without generating an output file. If validation fails, the message gives a line and column. Check that position and the preceding line: a missing comma often becomes visible when the next value begins. Standard JSON does not allow comments, single-quoted keys or a comma after the last array item.

Invalid: {"active": true,}
Valid:   {"active": true}

A successful validation checks this tool’s rules, not your application’s schema. A perfectly valid document can still be missing a required customer name, contain an unexpected status or use the wrong date format. Confirm those business rules separately.

3. Resolve duplicate keys deliberately

The document {"status":"draft","status":"sent"} contains two values for the same name in one object. Different consumers may handle this ambiguity differently. JSONWorkbench rejects it instead of silently discarding one value. Decide which value belongs in the source, or use an array if multiple values are intentional. Escaped spellings count too: "a" and "\u0061" are the same key. Reusing a key in separate objects is fine.

4. Keep large identifiers as strings

Many JavaScript systems use a numeric representation that cannot distinguish every integer above 9,007,199,254,740,991. An order identifier can therefore change when another tool reads it as a number. This workbench rejects numeric values outside the positive or negative safe range before formatting. Quote large IDs in the source, for example {"order_id":"9007199254740993"}.

Numeric tokens within the limit keep their original spelling. The value 1.00 stays 1.00, and 1e-500 stays 1e-500. This preserves detail during formatting, but a downstream parser may still round a high-precision decimal. For exact monetary calculations, use the representation required by your system, such as integer minor units or decimal strings.

5. Choose readability or compactness

Format JSON adds indentation using two spaces, four spaces or tabs. Minify removes formatting whitespace to produce a compact result. Both leave array order unchanged. Enable Sort object keys recursively to arrange names inside every object using a deterministic character order. That can reduce noisy differences when comparing configuration files, but it is not a canonicalization algorithm for signatures or cryptographic hashes.

The summary counts values by type and object keys separately. Root depth is zero; each nested value adds one level. There is a nesting limit of 256 levels and an output limit of 8 MiB. If indentation expands your document beyond the output limit, try Minify or work with a smaller section.

6. Review and save the result

Formatting never overwrites your input. Copy output writes the result to your clipboard; Download JSON creates a new file named formatted.json. If clipboard permission is unavailable, the tool selects the output so you can use your device’s Copy command. Review the result before replacing any important configuration.

Your document is held in the page’s memory rather than saved automatically. Reloading, resetting or closing the page can clear your work. Avoid secrets on shared devices, and treat downloaded files and clipboard history according to your normal data-handling rules.

Open JSONWorkbench →