PlayTools

JSON formatter: readable data, fewer production bugs

格式化、驗證和壓縮 JSON,帶語法高亮和錯誤檢測,全程在瀏覽器本地運行。

Runs in your browser — nothing you enter is uploaded

JSON formatter: readable data, fewer production bugs

JSON is the lingua franca of modern APIs. Pretty-printing exposes missing commas, mismatched braces, and accidental trailing text. Minifying removes whitespace for bandwidth while keeping payloads valid for clients that reject pretty output.

When to validate here: pasting sample responses from logs, preparing fixtures for tests, or teaching newcomers how objects and arrays nest. The linter feedback is immediate and private—nothing uploads to a server in normal browser-only operation.

Privacy tip: large JSON may contain tokens or PII — scrub secrets before sharing screenshots. Pair with Base64 or URL tools when debugging encoding layers.

Edge cases: duplicate keys are technically invalid per RFC but some parsers last-wins; JSON cannot have comments unless your pipeline uses JSON5—don’t assume comments are portable.

Workflow: format → visually scan structure → minify only when sending over the wire. Keep canonical pretty copies in repos for code review readability.

What Format and Minify actually do

Both buttons parse your input with the browser’s built-in JSON parser and write it back out — with 1, 2 or 4 spaces of indentation for Format, or with no whitespace at all for Minify. If the input is not valid JSON, nothing is rewritten and the parser’s error message is shown instead. Because the output is regenerated from the parsed data rather than edited in place, a few things change in ways worth knowing:

  • Duplicate keys: {"k":1,"k":2} becomes {"k":2}. The last value wins silently and the earlier one is dropped — a common source of “my setting is ignored” bugs.
  • Big integers lose precision: 12345678901234567890 becomes 12345678901234567000, because numbers are stored as 64-bit floating point and only integers up to 9,007,199,254,740,991 are exact. Send large IDs as strings.
  • Number spelling is normalised: 1.0 becomes 1 and 1e3 becomes 1000 — the same values, written differently.
  • Integer-like keys move first: {"b":1,"2":0,"a":2,"1":0} comes out as {"1":0,"2":0,"b":1,"a":2}. Other keys keep their original order.
  • Escapes are decoded: "caf\u00e9" is written back as "café".

Worked example: fixing invalid JSON

This looks like JSON but is rejected:

{
  'name': "Ada",
  "langs": ["en", "fr",],
  "active": True
}

Three problems: property names and strings need double quotes, a comma is not allowed after the last item in an array or object, and the literals true, false and null must be lowercase. The corrected version formats cleanly, and minified it becomes {"name":"Ada","langs":["en","fr"],"active":true} — 48 characters instead of 74 with 2-space indentation.

Minifying saves more as nesting grows: a three-user sample with ids, names, roles and an active flag goes from 412 characters pretty-printed to 203 minified. Over HTTP, gzip or Brotli compression narrows that gap considerably, so readable JSON in config files and fixtures costs very little.

Reading the error message

Error messages come from your browser, so the wording varies, but current Chrome and Edge report a position and a line and column, for example “Expected property name or '}' in JSON at position 4 (line 2 column 3)”. Position counts characters from zero. The real mistake is usually at that point or just before it — often a missing comma or quote on the previous line.

“Unexpected non-whitespace character after JSON” means there is more than one value in the input, such as two objects one after another. That is how NDJSON (newline-delimited JSON) log files are written; format one line at a time.

JSON, JSONC, JSON5 and NDJSON

  • JSON (RFC 8259): what this tool accepts — no comments, no trailing commas, double quotes only.
  • JSONC: JSON with // and /* */ comments, used by tsconfig.json and VS Code settings. Remove the comments before validating here.
  • JSON5: a looser superset allowing single quotes, unquoted keys, trailing commas and hexadecimal numbers. Fine for hand-edited config if your tooling supports it; not interchangeable with JSON APIs.
  • NDJSON / JSON Lines: one complete JSON value per line, common for logs and data exports. Each line is valid JSON on its own; the file as a whole is not.

Choosing an indentation

Two spaces is the convention in JavaScript projects (package.json, most API documentation) and keeps deep nesting readable on narrow screens. Four spaces matches Python’s json.dumps(indent=4) and many Java style guides. One space is a compromise for files that are diffed often but still read by humans. Pick one per repository and let your formatter enforce it, so reviews show real changes rather than whitespace.

In-depth guides

These free tools pair well with this page — open them in a new tab to finish your workflow.

常見問題

「格式化」和「壓縮」對JSON有什麼作用?

格式化(美化列印)新增空白、縮排和換行,使JSON便於人類閱讀。壓縮去除所有不必要的空白,生成最緊湊的形式,節省API回應的頻寬。

為什麼我的JSON驗證失敗?

常見JSON錯誤包括:最後一個鍵/值對後有尾隨逗號(JSON不允許)、字串使用單引號而非雙引號、屬性名稱未加引號、或數字有前導零。此驗證器會高亮顯示錯誤位置。

JSON和JavaScript物件有什麼區別?

JSON是一種資料交換格式,是JavaScript的嚴格子集。主要區別:JSON屬性名稱必須是雙引號字串;JSON值不能是undefined、函式或Symbol;JSON不支援註解。

JSON可以包含註解嗎?

不可以。JSON規範(RFC 8259)不允許註解。如果需要在設定檔中使用註解,可以考慮使用JSON5、HJSON或YAML。

什麼是JSON Schema?

JSON Schema是一種允許您驗證JSON文件結構和內容的詞彙規範。您可以定義規則,如必填屬性、允許的類型和值範圍。它用於API契約驗證和表單輸入驗證。