1. Format first
Start by pretty-printing compressed payloads or log fragments so the structure and nesting become obvious.
🔒 Browser-side processing
Format, validate, minify, and inspect JSON with tree view support.
No input
Workflow
Start by pretty-printing compressed payloads or log fragments so the structure and nesting become obvious.
Search helps narrow large payloads down to a user ID, status flag, or nested key without scanning the whole response manually.
The tree view is especially helpful when arrays and nested objects make plain formatted text harder to explain or screenshot.
Troubleshooting
JSON requires double quotes around keys and string values. JavaScript object syntax often causes confusion here.
A trailing comma may look harmless, but standard JSON parsers reject it in both arrays and objects.
This page runs in browser memory, but production secrets and personal data should still be masked before review when your internal policy requires it.
Examples
When you inspect API responses, config snippets, or logged payloads, separate “is this valid JSON?” from “does the shape match what I expected?” first.
Pretty-print compressed responses, then inspect status fields, pagination, and nested data positions.
{"ok":true,"data":{"user":{"id":42,"role":"admin"}}}
Single quotes, trailing commas, and comments belong to JavaScript-like objects, not strict JSON.
{
"env": "prod",
"featureFlags": ["search", "export"]
}
FAQ
JSON is a data exchange format. Keys and string values need double quotes, and comments or trailing commas are not valid.
Format when humans need to read and review the payload. Minify when you need a compact one-line body or fixture.
Most API responses are fine, but very large files can affect browser memory and rendering. For huge logs, inspect the relevant slice first.
Use JWT Decoder for token payloads, JSON YAML Converter for format handoff, and API Request Tester for reproducing requests.