JSON Guides

By Bruno J F Costa · Updated 9 September 2026 · Original walkthroughs that go beyond the homepage editor.

These pages are written to stand on their own. The formatter is the practice bench: paste, format, validate, copy. The guides explain decisions the buttons cannot make for you — when compact output is safer than pretty-print, why a JavaScript object is not JSON, how UTF-8 and escapes actually work, and what you should never drop into any beautifier.

They are not a second copy of the homepage FAQ. Start with the tool workflow if you are new; jump to the later articles when you already know Format and Validate and need a specific rule.

Path 1 — Use the tool

If you only need to clean a payload today, stay on this path. Each article walks a real click sequence on JSON Quiet and then stops. Do not skip validation if the file will leave your machine.

How to format JSON Paste, open a file, or load a public URL. Choose indentation. Format. Copy. Use compact only when size or a single-line paste matters. How to validate JSON (RFC 8259) Strict mode for anything you ship. Relaxed mode only while you clean a messy paste. Syntax is not a schema check. Common JSON errors and how to fix them Trailing commas, single quotes, unquoted keys, comments, NaN, undefined, and a repair loop that starts at the first reported line.

Path 2 — Understand the language

These articles answer “why did the parser reject this?” without repeating the error catalog. Read them when you are converting JavaScript, logs, or Portuguese text into portable JSON.

JSON vs JavaScript objects Why undefined, comments, and single quotes survive in JS and fail in every other language’s JSON library. Unicode, accents, and UTF-8 in JSON How “São Paulo”, emoji, and \uXXXX coexist. What to check when a Brazilian payload looks “corrupted” after a hop. Escape sequences in JSON strings When to write \n, \", and \u00e9. How an unescaped quote closes a string too early. Finding a key in nested JSON A reading method for deep API bodies: pretty-print first, then walk objects and arrays without writing a new tool.

Path 3 — Choose a format and stay safe

Not every file that contains curly braces is one JSON document. These pages cover compact vs pretty output, line-delimited logs, schema versus syntax, and the privacy line you should not cross in any formatter.

Minify vs pretty-print Indentation does not change values — but compact output changes how you review diffs, embed payloads, and debug production errors. JSON Lines / NDJSON One value per line for logs and streams. Why validating the whole file as a single document fails on purpose. JSON Schema vs RFC 8259 validation A valid document can still be the wrong shape. What syntax checks cover and what a schema (or OpenAPI) is for. What not to paste into a JSON formatter Tokens, customer PII, and internal configs. JSON Quiet stays in the browser — judgment still matters.

How to use this hub

Bookmark this page if you teach a teammate the tool. Send Path 1 to someone who has never formatted JSON. Send Path 2 when a JavaScript object “almost” works in Python or Go. Send Path 3 before someone pastes a production secret into a random cloud beautifier — including this one, if they have not read the Privacy Policy.

Author: Bruno J F Costa. Last expanded 9 September 2026. Each article includes at least one payload you can paste into the formatter — invalid JavaScript-style objects, a minified order body, a nested data.items[0].attributes.sku tree, JSON Lines records, and redacted fixtures. Corrections and genuine questions: Contact.

Open the JSON formatter · About the site