JSON Formatter — Pretty Print JSON

How to use

Paste JSON into the input, upload a .json file, or load the sample to see the tool in action.
Choose two spaces, four spaces, or tabs for indentation. Enable key sorting only if alphabetical order helps your review.
Read the formatted result as you type. If parsing fails, use the reported line and column to locate the problem.
Copy the result or download it as a .json file. Press Ctrl or Command plus Enter to process immediately.

Examples

Review an API response

The nested user record becomes easy to scan while all values keep their original types.

Input

{"id":12,"user":{"name":"Avery","active":true}}

Output

{
  "id": 12,
  "user": {
    "name": "Avery",
    "active": true
  }
}

Sort a settings object

Enable Sort object keys to make key order predictable when comparing two files.

Input

{"zeta":1,"alpha":2}

Output

{
  "alpha": 2,
  "zeta": 1
}

When formatting helps

Formatted JSON is useful when an API response arrives as one long line, a log entry needs inspection, or a configuration diff is hard to follow. Indentation exposes object boundaries and array items, so a misplaced field is easier to notice. The output remains valid JSON and can be pasted into a code editor, issue report, or test fixture.

Sorting keys is a review aid, especially when two producers emit the same object in different orders. It can make text diffs quieter. Leave sorting off when key order carries useful context for a human reader, such as the order in which settings were authored. JSON objects are data mappings, so clients should not rely on their display order.

For an API incident, first format the captured response with sorting off. That keeps the original field sequence visible while you compare it with a log or request trace. If you later compare two equivalent objects in a text diff, make a second copy with sorted keys. Keep the raw response as well: formatting cannot prove that a field has the correct type or that the response meets your API contract.

Reading errors and output

If the input is incomplete while you type, the error may be temporary. Finish the quoted string, closing bracket, or comma and the formatter will update. The line number beside the editor marks the reported line; activate the error message to place the cursor at its column. For large output, the screen shows a shortened preview to keep scrolling responsive. The Copy and Download buttons still use the full formatted text.

If you are preparing an example for an issue, replace secrets and personal data before sharing it. Browser-only processing keeps the input off this site’s servers, but copying the formatted result into another service is a separate action under your control.

Frequently asked questions

Does formatting change my data?

It changes whitespace and, if selected, object key order. JSON values remain the same, although the exact original whitespace is not preserved.

Can I format a large file?

Yes. Parsing runs in a browser worker, and the visible preview is capped for very large outputs. Copy and download still use the complete result.

Why does my input show an error?

JSON requires quoted property names and strings, no trailing commas, and valid escaping. The error reports a line and column when the parser provides one.

Is my JSON uploaded anywhere?

No. The tool runs in your browser. Input, uploaded files, and formatted output are not sent to a processing server.