JSON iGraph
← Home

JSON Formatter

LiveIn-browser only
Ln 1, Col 11 line · 0 bytes
0 bytes
Help

Format with 2-space, 4-space, or tab indent, minify whitespace, sort object keys, and check byte size — 100% in-browser.

01-03 Guide

How to format JSON in 3 steps

Beautify, minify and validate your payloads in seconds, with full control over spacing and key order.

    raw.jsonPaste or Upload
    { "user": {
    "id": "usr_42",
    "name": "Ada"
    }}
    Drag & drop .jsonREADY · 100% IN-BROWSER
    01

    Paste or load JSON

    Paste your JSON into the left pane, or press Sample to load an example.

    auto-transform✓ Valid Syntax
    2 Spaces
    vs
    Minify
    vs
    4 Spaces
    Web Worker engine0ms main thread
    02

    Format & validate

    It formats as you paste. Press Format, or Minify to strip every byte of whitespace instead.

    result.jsonKeys Sorted [A-Z]
    CopyDownloadShare
    Instant SaveClient-side only
    03

    Sort, copy & export

    Set the indent width or Sort keys beside the result, then Copy or Download it.

Why JSON iGraph

Engineered for precision & privacy

Exact error locations

Invalid syntax points to the exact line and column so you fix missing commas and brackets immediately.

100% private in-browser

Parsing runs strictly in your browser Web Workers. Your JSON is never uploaded or sent anywhere.

Recursive key sorting

Alphabetize object keys recursively all the way down for deterministic Git diffs while keeping arrays in order.

Live byte counters

Real-time size counters measure raw and minified text so you know exact bandwidth savings before transfer.

Technical Guide

What a JSON formatter actually does (and why whitespace matters)

JSON has no opinion about whitespace. {"a":1} and the same object spread across four indented lines are the identical document to a parser — the difference exists only for the person reading it. A JSON formatter, or beautifier, parses the text into abstract values and writes it back out with consistent indentation and line breaks. That is why it doubles as a validator: if it will not format, it will not parse, and the error names the exact line and column.

That matters most with JSON you did not write: a minified API response, a payload squeezed onto one log line, or a config file hand-edited until its nesting is unreadable. Sorting keys is the other half — objects are unordered by definition, so two equivalent payloads can produce chaotic Git diffs. Array order is left untouched, because arrays are ordered and sorting them would alter your data.

RFC 8259 TransformationLossless
Input Payload{"user":"Ada","roles":["admin"]}
Formatted Output{ "roles": ["admin"], "user": "Ada" }
Engine Specifications

Formatter Engine Standards

Strict adherence to official internet data interchange specifications.

  • ✓Standardized 2-space, 4-space, or tab indent
  • ✓Recursive alphabetical key reordering
  • ✓Lossless minification for network payloads
  • ✓Off-thread Web Worker execution (0ms main thread)
  • ✓Syntax error pinpointing (exact line & column)
IETF RFC 8259 & ECMA-404100% COMPLIANT

Zero server uploads. Your JSON payloads are processed exclusively inside your browser sandbox.

Answers

Frequently asked questions

Everything you need to know about browser-based formatting, validation, and privacy.

Is my JSON uploaded anywhere?
No. Formatting runs entirely in your browser — the JSON never reaches a server, and there is no request to log. You can confirm it by opening your network tab while you format.
Why did my file fail to parse?
The most common causes are a trailing comma after the last item, single quotes instead of double quotes, or an unquoted key. The error message names the line and column so you can go straight to it.
Does sorting keys change my data?
It reorders the keys of every object, which JSON treats as unordered, so the data is equivalent. Array order is never touched — that is meaningful and reordering it would change your data.
What is the difference between formatting and minifying?
Formatting adds indentation and newlines so a human can read the structure. Minifying removes every optional byte, which is what you want before sending JSON over a network.
Should I indent with 2 spaces, 4 spaces or tabs?
Two spaces is the most common convention for JSON and what most style guides assume. Four is easier to scan on deeply nested data. Tabs let each reader pick their own width, which matters for accessibility.
Can it handle comments or trailing commas?
Strict RFC 8259 JSON does not permit comments or trailing commas. If your payload contains them, click ⚡ Auto-Fix Syntax in the editor to automatically strip comments and trailing commas into valid JSON.

Related tools

More browser-based JSON utilities

Graph Visualizer — Live

Stop reading raw brackets. Start seeing connections.

Paste the same JSON into the graph and see it as connected nodes you can search, fold and export — completely free and in-browser.

Open JSON Graph →Back to Formatter ↑
GRAPH SCHEMA PREVIEWINTERACTIVE
Root: Object──►
├──user (Object)
└──roles [Array]
Node Graph Visualizer⚡ ZERO SERVER PROCESSING