Start with the failing input
Do not tidy the payload before checking it. Paste the same JSON that failed, because the useful clue is often the exact missing comma, bad quote, escaped character, or extra text that formatting would hide or reject.
When you should validate first
| Situation | Why validation should come first |
|---|---|
| You copied JSON from logs or a terminal | Log output often contains truncated text, escaped characters, or extra wrapper text that makes the payload invalid. |
| You edited the payload manually | Manual edits often introduce missing commas, mismatched quotes, or trailing commas. |
| An API request or parser is failing | The failure may be plain syntax, not business logic. Validation helps you rule that out fast. |
| You are not sure whether the JSON is complete | Validation tells you whether you can trust the structure before you spend time formatting it. |
Recommended sequence
- Paste the failing payload into the JSON Validator before changing whitespace.
- Fix the first syntax issue: commas, quotes, brackets, braces, escaping, or stray characters.
- Re-run validation after each fix so you do not stack new edits on top of a still-broken payload.
- Open the JSON Formatter only after the validator says the JSON parses cleanly.
Common JSON errors to check first
- Missing commas between keys or array items
- Single quotes where JSON requires double quotes
- Unmatched braces or brackets
- Trailing commas at the end of objects or arrays
- Extra text before or after the actual payload
What to do after validation passes
- Format the JSON to inspect nested objects, arrays, and field names more easily.
- Read the safety guide if the payload contains secrets or customer data.
- Read the comparison guide if your team keeps mixing these jobs up.
Why this guide exists
Many developers search for json formatter after seeing an error, but a formatter is not a debugger for invalid syntax. This page covers the broken-payload workflow: prove parseability first, then format for review.
FAQ
Validate first when the payload may be broken, copied from logs, edited manually, or already throwing parser errors. Formatting comes after the JSON is structurally valid.
The most common errors are missing commas, unquoted keys, bad quotation marks, trailing commas, unmatched braces, and extra characters after the payload.
Once the JSON validates cleanly, open the JSON Formatter to make it easier to read, debug, or share in a redacted form.