Format JSON indentation and review syntax errors
Expanding one-line JSON makes object and array boundaries easier to inspect. The tool parses and re-saves the data, so formatting should be distinguished from an editor that repairs invalid syntax for you.

How to use this tool
- Choose files in JSON format. Maximum files per batch: 1.
- Review Indentation, then start processing.
- Download the JSON result and check its content and quality.
Choose the right settings
Choose two spaces, four spaces or tabs to match the file's working convention. Use the same rule as the surrounding files when the result will be reviewed or maintained by other people.
- Supported input
- JSON
- Output
- JSON
- Available settings
- Indentation
Before you start
Establish the meaning of the input
Before converting or arranging data, identify what a row or value represents and keep a source copy. In tabular files, review headers, separators and text encoding; in structured files, inspect the required object or array shape. Identifiers, dates and amounts should not be interpreted solely from how a spreadsheet happens to display them.
Where the tool offers matching columns, type rules or output fields, choose them according to the destination’s requirements. Test a sample with a blank, a repeated value and a value containing punctuation. For labels, charts or personalized documents, check which column supplies each displayed value and whether the source units and wording are correct.
Define a few checks before processing: an identifier that must retain its spelling, a value with a known interpretation and an expected relationship between records. If the tool offers type conversion or matching rules, distinguish a source value from the program’s display of it. Test ambiguous dates or differently written keys before accepting a broad rule. Keep the chosen rules and destination requirements with the result; this makes a discrepancy traceable to input, interpretation or the requested transformation.
Verify values, structure and exceptions
Reopen or import the result using the destination’s settings. Compare headers, record counts and several values with the source, allowing for the operation you requested. A summary, split or duplicate-removal task can legitimately change the count; verify why it changed rather than expecting every transformation to keep identical rows.
Inspect any exception or validation report before continuing. If columns shift, characters are garbled or a key is not found, check delimiters, encoding and exact header spelling first. Encoding data does not encrypt it, and formatting a value does not confirm its meaning. For printed codes or labels, test the actual output before making the full set.
Example input and output
compact JSON → indented valid JSONExamples describe the workflow. Results depend on the source file and settings.
Check the saved result before using it
Confirm that required keys and array entries appear in the output. Load the result in its destination program and inspect whitespace inside strings where it is part of the actual value.
If the result is different from what you expected
Comments, trailing commas and unclosed quotes are not valid JSON syntax. Correct those errors before retrying, and avoid using the displayed key order alone to determine the meaning of the data.
Limits to keep in mind
- JSON must not contain comments or trailing commas. JavaScript number precision limits apply.
Continue with a related tool
This guide explains the public browser tool. Keep a copy of the original and inspect the result before sharing it.