🧭
Precise error context
Parse failures show the character position, line, column, and nearby source text when the browser exposes a position.
Input or options changed — run an action to refresh the output.
JSON input
Result
No result yetChoose Format, Minify, or Validate.
🌳
Safe tree viewer
Explore nested objects and arrays in collapsible nodes rendered with text nodes—not executable HTML.
🔎
Search and path lookup
Count text matches or retrieve values using paths such as users[0].profile.name without using eval.
Formatting and validating JSON safely
Paste or import a JSON file, choose formatting preferences, and run an explicit action. Processing stays in the browser, but sensitive data can still remain in clipboard history or screenshots.
JSON is stricter than JavaScript
Property names and strings require double quotes. Comments, trailing commas, undefined, NaN, and single-quoted strings are invalid.
Numbers have precision limits
JavaScript may lose precision for integers larger than 9,007,199,254,740,991. Keep large identifiers as quoted strings.
Minification
Minify removes insignificant whitespace but preserves parsed data. It does not compress the transport like GZIP or Brotli.
Sorted keys
Recursive sorting improves stable diffs, but changes property order. Do not enable it when downstream systems depend on presentation order.