JSON Formatter

Key features

• Beautify with your choice of 2 spaces, 4 spaces or tab indentation.
• Minify strips all whitespace to the smallest valid payload — useful before embedding JSON in code or URLs.
• Validate checks syntax without changing anything and reports the key count and maximum depth.
• Parse errors show the exact message from JSON.parse — like 'Unexpected token' positions — instead of a vague failure.
• After every run, stat tiles show the number of keys, maximum nesting depth and the UTF-8 size before and after.
• A Sample button loads a realistic nested document so you can try all three actions in one click.

How it works

1. 1

   Paste your JSON

   Drop raw JSON into the Input panel. If it's malformed, the error banner quotes the parser's message so you know where to look.

2. 2

   Pick an indent style

   Choose 2 spaces, 4 spaces or tab from the Indent select — this only affects Beautify output.

3. 3

   Run Beautify, Minify or Validate

   Beautify pretty-prints, Minify compresses to one line, Validate just parses and toasts 'Valid JSON' with key and depth counts.

4. 4

   Review stats and copy

   Compare the size before and after, check nesting depth, then Copy the result for use in your project.

Tips for better results

• 💡Validate is the fastest way to confirm a payload is well-formed when you don't need a reformatted copy.
• 💡Minify before pasting JSON into config files, env vars or log messages to save bytes and lines.
• 💡Deep max-depth numbers (say, above 10) often signal accidental nesting — worth flattening before you ship an API.
• 💡JSON doesn't allow trailing commas, single-quoted strings or comments; the error message usually names the offending token.

Frequently asked questions