jfmt.dev

JSON Beautifier

Paste minified JSON and pretty-print it with two-space indentation. The beautifier is the homepage formatter on a dedicated URL — values stay the same, only whitespace changes, and nothing is sent to a server.

input.json

JSON formatter

Input0 B
Output · preview.json
{ }

Run a tool to see a polished result here

Live syncReady · processed locally in your browser
Local-only processing: your JSON never leaves this browser tab.

Beautify vs minify vs tree view

Beautify (pretty print) inserts newlines and indentation so a payload is readable in a text editor. Minify deletes that whitespace for APIs and logs. The JSON viewer on this site turns the same document into foldable nodes instead of indented text. If you need to copy JSON back into a config file, stay on the beautifier; if you only need to click through a large object, open the viewer.

What pretty-print changes (and what it refuses to change)

Insignificant whitespace between tokens is rewritten. Unicode in strings is preserved. Trailing commas, single-quoted strings, and `//` comments are not JSON, so the beautifier rejects them instead of guessing. Duplicate keys are kept as the parser’s last value and mentioned in the status line. Oversized integers stay as digits; they are not rounded to IEEE floats.

{"a":1,"b":[true,null]} →
{
  "a": 1,
  "b": [
    true,
    null
  ]
}

Beautifier vs the homepage formatter

They share the same Web Worker. This page exists so “json beautifier” and “pretty print json” queries can rank on a URL whose H1 matches that wording. The homepage title stays aimed at the broader “JSON formatter” query. Use whichever URL you already have open; the engine is identical.

When not to beautify

Do not pretty-print before hashing or signing a payload if the receiver expects the exact original bytes. Do not beautify huge one-line logs if you only need one nested field — JSONPath or the viewer will be faster. Do not treat beautify as validation of business rules: a document can be pretty and still be the wrong shape.

Sample input on this page

The sample is a small service object with nested limits and tags. It is already loosely formatted so you can press Run and see indentation normalized. Replace it with a one-line payload to see the beautifier expand it.

{
  "service": "jfmt",
  "enabled": true,
  "limits": { "retries": 3, "timeoutMs": 1500 },
  "tags": ["beautify", "pretty-print"]
}

How to use this tool

  1. Paste compacted JSON on the left. A single-line API body or a minified config is the usual input.
  2. Run JSON Beautifier. The output is valid JSON with two-space indents; strings, numbers, and key names are not rewritten.
  3. Copy the pretty-printed result, or switch the sidebar to Minify if you need the compact form again.
  4. If parse fails, the document is not JSON yet — use the validator to read the syntax error, or Repair for trailing commas and comments.

When this page is the right choice

Land here when you searched for a JSON beautifier or pretty printer. The homepage still opens a general workspace; this URL preselects format so you do not have to hunt in the sidebar. It is the wrong page for converting to Excel or comparing two files.

FAQ

Is a JSON beautifier the same as a JSON formatter?

Yes. Beautifier, pretty printer, and formatter all indent valid JSON. This URL is worded for beautifier searches.

Does beautifying change values or key order?

Values stay the same. Key order is preserved. Only whitespace and line breaks are rewritten.

Can it pretty-print JSON with comments?

No. Comments are not JSON. Use Repair first, then beautify the strict output.

What indent width does JFmt use?

Two spaces, matching the homepage formatter. There is no tab-indent option on this page.

Is my JSON uploaded?

No. Pretty-print runs in a Web Worker in this tab.