Issue
Sign In
StepCodex FeaturedStepCodex Reviews
Notion Docs

Pretty-print, minify, validate, analyze structure, and repair common issues — all locally in your browser. Free online tool, no login, no sign-up.

LocalPersonal data security

Loading Tool Engine

Usage Guide & Tech FAQ

Usage Guide

  1. Paste raw JSON (or upload a file) and ensure it follows standard JSON rules.
  2. Pick output mode: `Pretty` for readability or `Compact` for request payloads.
  3. Optional: enable `Sort keys (recursive)` for stable output and easier reviews.
  4. Set indentation (2/4/Tab) to match your style, then format.
  5. When there is an error: use `Validate` first to read the message, then try `Strip trailing commas` for common cases.
  6. Copy results in two ways: copy the visible text (for manual paste) or copy the minified JSON (for API bodies).
  7. To integrate into your project, use `Download .json`.
  8. In the `Markdown Fold Preview`, click nodes to fold/expand and use search to locate paths precisely.
  9. When presenting to non-devs, use the fold preview to walk the tree instead of raw minified JSON.
  10. For repeated edits, keep indentation style stable so Git/review tools show meaningful diffs.
  11. Read the title and description first to confirm this utility matches your task (avoid using the wrong tool and misinterpreting output).
  12. Paste or type input in the editor; if a sample/template is provided, load it first to learn the expected output shape.

Related Tech Knowledge

  • Formatting pipeline: parse (JSON.parse) -> optional recursive key sorting -> unified stringify output.
  • Differences in readability come from indentation and line breaks; semantics stay the same if types/values are unchanged.
  • Recursive key sorting stabilizes the output: identical inputs produce consistent key order, great for Git diff.
  • Trailing comma repair is heuristic: it fixes common `...,}` / `...,]` patterns, but complex non-standard syntax may still fail.
  • Error position hints are derived from parse error messages when available, giving you line/column guidance.
  • All operations run locally in your browser with safeguards for personal data.
  • The fold preview is path-based tree rendering, optimized for structural inspection and quick pinpointing.
  • Very large JSON may slow down parsing, rendering, and search traversal; consider splitting input when needed.
  • Gateways/log platforms care about one-line vs pretty payloads—balance readability with size/indexing.
  • In sensitive environments, avoid loading third-party sample links that could pull external data.
  • Core parsing and computation run in your browser; by default your raw business payload is not persisted to this site’s servers (see on-page privacy notes).
  • The pipeline is typically: read input → parse (lexical/syntactic/structured) → transform → render; failures aim to be diagnosable.