Practical example
An API response such as {"price":"19.90","active":"false"} is valid JSON, but the quoted number and boolean may still break consumers that expect strict types.
JSON (JavaScript Object Notation) is a lightweight data format used to exchange structured data between services and applications.
This tool helps you format (pretty-print) JSON for readability or minify JSON to reduce size for storage and network transfer. Processing runs locally in your browser.
Pretty-print the payload first so nested arrays, objects, nulls, and escaped strings are easy to inspect.
Valid JSON can still be wrong for an API contract. After formatting succeeds, validate required fields, types, and enums with a schema.
If formatting fails, confirm the response is really JSON and not an HTML error page, truncated output, or log wrapper.
Minified JSON is useful for transport and config files, but keep a formatted version while debugging changes.
Learn the workflow behind this tool and what to check next.
A repeatable workflow for separating transport errors, JSON syntax problems, and data-contract failures in API responses.
A practical workflow for formatting JSON, finding syntax errors, validating payload shape, and checking response status when API data looks wrong.
Formatting is only the first step. Use the formatted output to confirm structure, types, nesting, and whether the response can be copied into tests or documentation.
Check missing commas, trailing commas, unescaped quotes, duplicate-looking fields, and deeply nested arrays before blaming the API client.
Look for strings that should be numbers, null values that your app cannot handle, and booleans represented as text.
Minify payloads for compact fixtures or format them for readable code reviews, bug reports, and API docs.
Replace tokens, emails, customer IDs, and real records with safe sample values before sharing JSON in tickets or chats.
An API response such as {"price":"19.90","active":"false"} is valid JSON, but the quoted number and boolean may still break consumers that expect strict types.
A response beginning with <html> is usually a proxy or application error page, not malformed JSON. Check the HTTP status and Content-Type first.
I use formatting to reveal structure, then validate the data contract separately; readable JSON is not automatically correct JSON.
You may also find these tools useful.