HTML Formatter
Beautify and indent HTML markup.
OpenPaste a one-line API response and read it as indented JSON, with syntax errors reported live.
Drop in an API response, a config export or any raw JSON string.
A green badge means it parsed; otherwise the parser error is shown.
Choose indented output or a compact single line.
Copy the result or save it as formatted.json.
A webhook delivery lands in your logs as one long line and you need to know whether customer.address is missing or just null. Paste it here and the formatter validates the payload and lays it out with proper indentation, so the answer is visible at a glance.
Every keystroke runs the browser's native JSON parser. Valid input is printed with two-space indentation and a green Valid JSON badge; invalid input clears the output and shows the parser's error message, which usually includes the position of the problem. Beautify and Minify switch between indented and single-line output, Sample loads a small example, and Download saves formatted.json.
A green result means the syntax is correct, not that the data is right. Valid JSON can still carry the wrong types or omit keys your code needs. Most parse failures come from JavaScript habits: trailing commas, single quotes and unquoted keys. For large documents, the collapsible JSON tree viewer is easier to explore, and a clean sample can go straight into the JSON Schema Generator. The blog also walks through a format, minify and Base64 workflow built from these tools.
Payloads stay in this tab while you work. Refreshing the page clears the working copy, and nothing you paste is logged.
Keyboard shortcut
Make a delivery body readable so nested IDs and claims are easy to check.
Confirm a feature-flag or settings file parses before you push it.
Clean a sample response, then generate a schema from it.
Answers for this tool. For site-wide help, open the FAQ hub.
JavaScript stores numbers as 64-bit floats, so integers above 9007199254740991 are rounded when parsed. If your payload has very large numeric IDs, keep them as strings in the source data.
The parser keeps the last value for a repeated key and silently drops the earlier ones. If a field seems to have the wrong value, search the raw input for a second copy of that key.
No. Comments are not part of the JSON standard, so the parser rejects them. Remove the // and /* */ lines first, otherwise the error will point at the first comment.