How it works
The browser JSON parser validates input, then output is formatted with two spaces or minified.
Invalid JSON errors are shown without sending content away.
Format and validate JSON.
Pretty print, minify, and validate JSON with clear local error messages.
ResultWaiting
0nodes
0object keys
0max depth
Enter a path to inspect a nested value.
Practical examples
- Pretty-print a compact API response before reading it.
- Minify JSON before pasting it into a test fixture or config file.
- Use path lookup to inspect nested fields such as user.name or items[0].id.
How to read the result
- Valid JSON updates the node, key, and depth summary.
- Pretty print preserves JSON values while changing whitespace.
- Path lookup reads a parsed value without changing the formatted output.
Limits and privacy notes
- Only strict JSON is accepted; comments and trailing commas are invalid.
- Very large payloads can slow a browser tab.
- JSON text is parsed locally in your browser and is not uploaded.
Validate, format, inspect
- Pretty print first to catch syntax errors.
- Use path lookup for nested fields.
- Use minify only after the payload is valid.
Common invalid cases
- Trailing commas are invalid.
- Comments are invalid.
- Keys and strings must use double quotes.
Read the metrics
- Node count hints at payload size.
- Object-key count shows structure density.
- Depth helps spot deeply nested responses.