Text workspace
JSON Formatter
Pretty-print, minify, or validate JSON in one local panel. Choose indent, optionally sort keys, copy, or download. Review API responses and catch syntax errors before you share.
JSON never leaves this tab while you format or validate it.
What this panel does
Parses JSON in the browser so you can pretty-print with 2- or 4-space indentation, minify without extra whitespace, validate with a clear success or parser error, optionally sort object keys A→Z, copy the result, or download a .json file. Pretty mode makes dense API responses readable for reviews; minify shrinks fixtures for pasting into tickets; validate catches trailing commas and quotes after a hand edit. The tool formats syntax only: it does not fetch URLs, apply JSON Schema, or redact secrets, so scrub sensitive fields before you share a screenshot.
How to use it
Paste the JSON, choose pretty-print, minify, or validate, pick indent and whether to sort keys, then copy or download the result. Fix syntax in the box when validate fails, then pretty-print again before you share. Scrub tokens and PII before screenshots.
Assumptions
Uses the browser JSON parser. Pretty-print uses the indent you choose (2 or 4 spaces). Validate checks syntax only, not business rules or schemas. Sort keys is optional and recursive.
Worked example
Input
{"ok":true,"items":[1,2],"note":"ship"}
Output
Pretty-print (2-space):
{
"ok": true,
"items": [
1,
2
],
"note": "ship"
}
Validate: success
Minify: {"ok":true,"items":[1,2],"note":"ship"}
Broken sample {"ok":true,} → parser error (trailing comma).
Quick comparison
| Option | Detail |
|---|---|
| Pretty-print | 2- or 4-space indentation for readable reviews. |
| Minify | Strip unnecessary whitespace for compact fixtures. |
| Validate | Success or parser error; does not auto-fix. |
| Sort / download | Optional A→Z keys; download stays local to this tab. |
More typical paste jobs
- Pretty-print {"a":1,"b":[true,false]} with 2-space or 4-space indentation.
- Validate a hand-edited webhook body and see a clear parser error if it is broken.
- Minify a fixture, sort keys, then download before attaching it to a bug report.
Practical use cases
- Developers reviewing API responses before sharing them with a remote teammate.
- Anyone validating a webhook or config JSON after a hand edit.
- Support engineers pretty-printing a customer payload pasted into a ticket.
- QA shrinking a fixture with minify before attaching it to a bug report.
- You decoded a Base64 sample and need to confirm the JSON still parses.
Limitations
Syntax only: no JSON Schema, no JSON Path queries, no URL fetch, no interactive tree view. Does not redact secrets. Parser errors point at syntax, not business-rule validity. Very large documents may strain the tab even though nothing is uploaded.
Text tool questions
- Does validate fix my JSON automatically?
- No. Validate reports success or a parser error. You still edit the text to fix trailing commas, quotes, or brackets.
- What indentation does pretty-print use?
- Choose 2 or 4 spaces. That keeps diffs readable in most code reviews without depending on editor settings.
- Can it fetch a URL for me?
- No. Paste the JSON body yourself. Keeping the work local avoids sending private payloads to a server.
- Does minify change values?
- No. Minify only removes unnecessary whitespace. Enable sort keys if you want A→Z key order after a successful parse.
- Are secrets safe to paste?
- Formatting stays local, but treat screenshots and shared pastes carefully. Scrub tokens before you send a capture.
Text tools on GetToWork process paste locally. Assumptions belong on the page. How our tools work · Editorial policy · Contact