Learn how JSON indentation works, how to choose 2-space or 4-space indentation, and how to format nested objects and arrays without changing the underlying data.

Format JSON Online Learn JSON Pretty Print

What is JSON indentation?

JSON indentation is the use of spaces or tabs at the beginning of lines to visually show the nesting of JSON objects and arrays. Indentation is whitespace used for readability; it is not required for the JSON data model. The same valid JSON can be written on one line or across multiple indented lines without changing its values or structure.

Compact

{"user":{"name":"Ramesh","roles":["developer","admin"]}}

Indented

{
  "user": {
    "name": "Ramesh",
    "roles": [
      "developer",
      "admin"
    ]
  }
}

JSON Indentation: Spaces, Nested Objects, Arrays, and Formatting

JSON doesn't require indentation, but readable JSON usually benefits from it. Once an object contains another object or an array, indentation makes the hierarchy visible without changing the actual data. A consistent indentation style also makes JSON files easier to review, edit, debug, and compare in version control. This guide explains how indentation works and how to apply it safely in common development workflows.

What Is JSON Indentation?

JSON indentation is whitespace placed at the beginning of lines to show the nesting level of objects and arrays. It is a presentation choice rather than a structural requirement. A parser generally treats insignificant whitespace outside strings as syntax that can be ignored, so formatted and compact representations can contain the same data.

Is Indentation Required in JSON?

No. Standard JSON does not require indentation, spaces, or line breaks between structural elements where whitespace is optional. JSON can be written as a compact single line or formatted across multiple lines. Indentation is primarily for people reading and maintaining the document.

Indented JSON vs Compact JSON

Consider the same object in two forms. The compact version is shorter, while the indented version makes the hierarchy much easier to scan.

Compact JSONjson

{"name":"Ramesh","profile":{"role":"developer","active":true}}

Indented JSONjson

{
  "name": "Ramesh",
  "profile": {
    "role": "developer",
    "active": true
  }
}

How JSON Indentation Shows Nesting

Each nested object or array is normally moved one indentation level deeper. When the nested structure closes, the closing brace or bracket returns to the indentation level of its opening property. This visual alignment makes it possible to understand a deeply nested document without reading every character.

Nested object indentationjson

{
  "user": {
    "profile": {
      "name": "Ramesh",
      "role": "developer"
    }
  }
}

JSON Indentation for Arrays

Arrays can contain primitive values, objects, or other arrays. A common readable style places each array element on its own line when the array is large or contains objects. Short arrays can also remain on one line if the project's formatting convention allows it.

Array indentationjson

{
  "skills": [
    "Python",
    "FastAPI",
    "PostgreSQL"
  ]
}

Array of objectsjson

{
  "users": [
    {
      "id": 1,
      "name": "Ramesh"
    },
    {
      "id": 2,
      "name": "Alex"
    }
  ]
}

2-Space JSON Indentation

Two spaces per nesting level are widely used for readable JSON because they provide a clear hierarchy without making deeply nested documents excessively wide. The important part is consistency. If a project uses two spaces, keep the same convention throughout files that follow that project's formatting rules.

Two-space indentationjson

{
  "user": {
    "name": "Ramesh",
    "active": true
  }
}

4-Space JSON Indentation

Four spaces per nesting level are another common choice. Four spaces can make each hierarchy level more visually distinct, although deeply nested documents can become wider. There is no universal requirement that JSON must use four spaces.

Four-space indentationjson

{
    "user": {
        "name": "Ramesh",
        "active": true
    }
}

2 Spaces vs 4 Spaces for JSON

Both styles can represent exactly the same JSON data. The choice is primarily about readability and project conventions rather than parser behavior. A team should generally choose one style for a particular codebase and apply it consistently.

2 spaces

Benefit: Compact and easy to scan

Trade-off: Nesting levels may be slightly less visually separated

4 spaces

Benefit: More visible separation between nesting levels

Trade-off: Deep JSON becomes wider

Tabs

Benefit: Display width can be controlled by the editor

Trade-off: Visual width can vary between environments

Spaces vs Tabs for JSON Indentation

JSON syntax permits whitespace where whitespace is insignificant, so indentation can be represented with spaces or tabs. For shared JSON files, many teams prefer spaces because the visual width is consistent across editors and tools. The key requirement is to use a consistent style rather than mixing indentation methods randomly.

Does JSON Care About Whitespace?

Outside string values, JSON syntax allows whitespace in places where it is insignificant. This means indentation normally does not affect the parsed data. Whitespace inside a JSON string is different: it is part of the string value and must be preserved.

Whitespace inside a string mattersjson

{
  "message": "Hello   world"
}

JSON Indentation Does Not Change the Data

Changing indentation from two spaces to four spaces, or converting formatted JSON to compact JSON, should not change the JSON values. If a formatting operation changes a key, string, number, boolean, null value, array element, or object property, it has performed more than simple formatting.

How to Indent JSON Online

The easiest way to indent an existing JSON document is to pass it through a JSON formatter. Paste valid JSON into the formatter, select or use the desired indentation style if the tool supports it, and generate readable output. The result should preserve the original JSON data while adding line breaks and indentation.

Copy the JSON you want to inspect.
Check that the input is valid JSON.
Open a JSON formatting tool.
Paste the JSON into the input area.
Choose the desired indentation level when available.
Format or pretty print the JSON.
Compare the result with the original if the data is important.

/json-formatter

How to Indent JSON in JavaScript

JavaScript provides a built-in way to produce indented JSON through JSON.stringify(). The third argument controls indentation. Passing 2 produces two-space indentation, while passing 4 produces four-space indentation.

Indent JSON with two spacesjavascript

const formatted = JSON.stringify(data, null, 2);
console.log(formatted);

Indent JSON with four spacesjavascript

const formatted = JSON.stringify(data, null, 4);
console.log(formatted);

Indent a JSON String in JavaScript

If the input is a JSON string rather than an existing JavaScript object, parse it first and then serialize it with indentation. Parsing also gives you an opportunity to detect invalid JSON before producing formatted output.

Format a JSON stringjavascript

const formatted = JSON.stringify(JSON.parse(jsonText), null, 2);

/guides/format-json-javascript

How to Indent JSON in Python

Python's json.dumps() function supports an indent argument. After parsing JSON with json.loads(), pass indent=2 or another preferred value to generate readable JSON.

Two-space JSON indentation in Pythonpython

import json

data = json.loads(json_text)
formatted = json.dumps(data, indent=2)
print(formatted)

Four-space JSON indentation in Pythonpython

import json

data = json.loads(json_text)
formatted = json.dumps(data, indent=4)
print(formatted)

Indent JSON with jq

jq is useful for inspecting and formatting JSON from the command line. Running jq with a JSON file produces human-readable output with indentation.

Format JSON with jqbash

jq . input.json

JSON Indentation in VS Code

Code editors such as Visual Studio Code can format JSON automatically. Open the JSON file and use the editor's formatting command or configured formatter. Project-level formatting rules can help keep indentation consistent across a team.

JSON Indentation in Code Editors

Most modern code editors understand JSON syntax and can automatically indent nested structures while you type. They can also reformat an existing document. Editor configuration is useful when a repository has an established indentation convention that developers need to follow.

JSON File Indentation

Readable indentation is especially useful for JSON files that developers edit manually, such as configuration files, fixtures, static datasets, and exported data. Consistent indentation makes changes easier to identify in Git diffs and reduces the chance of accidentally editing the wrong nesting level.

/guides/format-json-file

JSON Indentation for API Responses

API responses are often returned as compact JSON or displayed differently depending on the client. Formatting a response makes nested records, arrays, metadata, and error objects easier to inspect. Indentation affects presentation only; it does not make an API response structurally correct.

JSON Indentation for Request Payloads

Developers frequently format request bodies while building or debugging APIs. A readable request payload makes it easier to verify field names, nested objects, arrays, and values before sending the request. The actual request sent over the network can be formatted or compact depending on the application's serialization workflow.

/guides/format-json-payload

JSON Indentation for Webhook Payloads

Webhook payloads can become difficult to inspect when they contain nested event data. Formatting the payload is useful during development and troubleshooting. If the webhook provider signs the raw request body, keep the original body unchanged for signature verification and create a formatted copy for inspection.

/guides/format-webhook-json

Does Indentation Affect JSON File Size?

Yes. Indentation adds whitespace, so formatted JSON usually occupies more characters than its compact equivalent. For local configuration and source files, the readability benefit is often more important than the additional whitespace. For network transfer, compression and actual payload size should be considered before deciding whether formatting matters.

JSON Indentation and Minification

Indentation and minification serve opposite presentation goals. Formatting adds indentation and line breaks to make JSON readable. Minification removes unnecessary whitespace to make the textual representation more compact. Both should preserve the underlying data.

JSON Indentation vs Pretty Printing

Pretty printing is the broader process of producing readable JSON with line breaks and indentation. Indentation is one of the main mechanisms used to create that visual hierarchy. A pretty printer may also apply consistent spacing around structural elements according to its serialization rules.

JSON Indentation vs Validation

Indentation does not prove that JSON is valid beyond what the formatter or parser may have checked while processing it. Validation asks whether the document satisfies JSON syntax and, when applicable, whether it conforms to a schema or application contract. A JSON document can be well indented and still contain incorrect data types or missing required properties.

Can Indentation Fix Invalid JSON?

No. Changing indentation cannot repair missing commas, invalid quotes, unmatched brackets, trailing commas, or other syntax errors. A JSON parser or validator needs to recognize valid syntax before ordinary formatting can be applied. If the input is malformed, fix the syntax first.

Indentation for Deeply Nested JSON

Indentation becomes particularly valuable as nesting increases. A consistent level makes it easier to see which closing brace belongs to which object. However, extremely deep nesting can still be difficult to maintain. When the data model becomes unnecessarily nested, the better solution may be to simplify the structure rather than continually adjusting indentation.

Indentation for JSON Arrays of Objects

Arrays containing objects are common in API responses and configuration files. Each object is normally indented relative to the array, and the object's properties receive another indentation level. This creates a visual distinction between the collection and each record.

Indented array of objectsjson

{
  "products": [
    {
      "id": 101,
      "name": "Keyboard",
      "price": 49.99
    },
    {
      "id": 102,
      "name": "Mouse",
      "price": 29.99
    }
  ]
}

Indentation and Git Diffs

Consistent indentation can make version-control diffs easier to read. If a team uses one formatting convention, unrelated whitespace changes are less likely to obscure actual data changes. Automatic formatting can help, but it should be applied consistently so the formatter itself does not generate large, unnecessary diffs.

JSON Indentation for Documentation

Readable JSON is useful in API documentation, tutorials, README files, technical specifications, and examples. Indentation lets readers understand the relationship between properties without having to decode a long single-line string.

JSON Indentation and Sensitive Data

Formatting JSON does not make sensitive information safer. Readable output can actually make secrets and personal information easier to spot, but copying the data into an online formatter can introduce a separate privacy concern. Avoid sending API keys, passwords, access tokens, private customer data, or confidential payloads to tools that should not receive them.

JSON Indentation for Large Files

Formatting a very large JSON document can significantly increase its textual size and may make it harder for an editor or browser to handle. For large datasets, command-line tools, structured viewers, pagination, streaming, or targeted extraction can be more practical than fully expanding the entire document.

Common JSON Indentation Mistakes

Most indentation problems are readability issues rather than JSON syntax errors. A parser generally does not care whether a document uses two spaces or four spaces, but inconsistent formatting can make a document difficult to maintain.

Mixing tabs and spaces

Choose one indentation convention for the project.

Using different indentation widths in one file

Use a consistent indentation level throughout the document.

Manually deleting every space

Use a JSON-aware formatter or serializer.

Changing values while formatting

Formatting should change presentation, not data.

Assuming indentation fixes invalid syntax

Validate or repair malformed JSON separately.

Formatting signed webhook bodies before verification

Preserve the original raw request body when exact bytes are required.

JSON Indentation Best Practices

The best indentation style is usually the one that is consistent with the surrounding project and tooling. For manually maintained JSON, readable indentation is generally preferable to compact output. For generated production data, choose formatting based on actual requirements rather than applying it automatically.

Use a consistent indentation width.
Prefer the project's existing formatting convention.
Use JSON-aware tools rather than manual whitespace editing.
Keep nested objects and arrays visually aligned.
Do not modify string contents while changing indentation.
Format source files when humans need to maintain them.
Generate compact output when a workflow specifically benefits from it.
Use version-control diffs to verify that only intended changes occurred.
Validate JSON separately from formatting when correctness matters.
Preserve raw webhook bodies when signature verification depends on exact bytes.
Avoid exposing sensitive JSON to untrusted online services.

A Simple JSON Indentation Workflow

When you receive compact or difficult-to-read JSON, avoid manually inserting spaces throughout the document. Parse the JSON with a JSON-aware tool and serialize it using a consistent indentation setting. If parsing fails, investigate the syntax error first.

Keep a copy of the original JSON.
Determine whether the input is supposed to be standard JSON.
Parse or validate the document.
Fix syntax errors if parsing fails.
Format the valid JSON with a consistent indentation level.
Inspect nested objects and arrays.
Compare important data with the original.
Save the formatted version if it is a maintained file.

Choosing the Right Indentation Level

For most readable JSON, two or four spaces are practical choices. Two spaces produce a relatively compact hierarchy, while four spaces provide more visual separation. If the JSON belongs to a project, follow its established convention instead of introducing a new style for one file.

When Not to Indent JSON

There are cases where compact JSON is preferable. Generated payloads, machine-oriented artifacts, and high-volume data transfers may benefit from avoiding unnecessary whitespace. Even then, keeping a readable source representation can make maintenance easier, with compact output generated as a separate step.

JSON Indentation Styles

Factor	readability	width	common Use
2 spaces	High	More compact	General readable JSON
4 spaces	High	Wider	Projects preferring stronger visual nesting
Tabs	Depends on editor settings	Variable	Projects with an explicit tab convention
No indentation	Low for humans	Most compact	Generated or compact JSON

JSON Formatting Examples

Format JSON with 2 spaces in JavaScript

javascript

const formatted = JSON.stringify(data, null, 2);
console.log(formatted);

Format JSON with 4 spaces in JavaScript

javascript

const formatted = JSON.stringify(data, null, 4);
console.log(formatted);

Format a JSON string in JavaScript

javascript

const formatted = JSON.stringify(JSON.parse(jsonText), null, 2);

Format JSON with 2 spaces in Python

python

import json

data = json.loads(json_text)
formatted = json.dumps(data, indent=2)
print(formatted)

Format JSON with 4 spaces in Python

python

import json

data = json.loads(json_text)
formatted = json.dumps(data, indent=4)
print(formatted)

Format JSON with jq

bash

jq . input.json

JSON Indentation Checklist

Choose a consistent indentation style.
Use the project's existing convention when one exists.
Use two or four spaces if you need to establish a new convention.
Keep nested objects one level deeper than their parent.
Indent array elements consistently.
Keep closing braces and brackets aligned with their opening structure.
Do not change string contents while formatting.
Use a JSON-aware formatter instead of manually editing whitespace.
Validate JSON separately when syntax correctness matters.
Keep human-maintained JSON readable.
Use compact JSON when a workflow specifically requires it.
Check Git diffs after automated formatting.
Preserve raw webhook bodies when signatures depend on exact bytes.
Avoid sending confidential JSON to untrusted online tools.

Frequently Asked Questions

Q:What is JSON indentation?

JSON indentation is whitespace used at the beginning of lines to visually represent the nesting of objects and arrays. It improves readability but is not required by the JSON data model.

Q:Is indentation required in JSON?

No. Valid JSON can be written on one line without indentation or formatted across multiple lines with indentation.

Q:How many spaces should JSON indentation use?

Two or four spaces are common choices. There is no universal requirement for one specific indentation width, so project conventions should take priority.

Q:Should JSON use 2 spaces or 4 spaces?

Both are valid formatting choices. Two spaces keep nested JSON relatively compact, while four spaces provide more visual separation. Consistency matters more than the specific number.

Q:Can JSON use tabs for indentation?

Whitespace can be used for formatting JSON, including tabs where permitted. Shared projects often prefer spaces for more predictable visual alignment across editors.

Q:Does JSON indentation change the data?

Proper indentation should only change whitespace used for presentation. It should not change keys, values, objects, or arrays.

Q:Does indentation increase JSON file size?

Yes. Indentation adds whitespace, so formatted JSON is generally larger as raw text than its compact representation.

Q:How do I indent JSON in JavaScript?

Use JSON.stringify(data, null, 2) for two-space indentation or JSON.stringify(data, null, 4) for four-space indentation.

Q:How do I indent a JSON string in JavaScript?

Parse the string first and then serialize it with an indentation argument: JSON.stringify(JSON.parse(jsonText), null, 2).

Q:How do I indent JSON in Python?

Use json.dumps() with the indent argument, such as json.dumps(data, indent=2).

Q:Can I indent JSON online?

Yes. A JSON formatter can parse valid JSON and produce readable output with indentation. Avoid submitting sensitive data to services you do not trust.

Q:Does JSON care about spaces?

Whitespace that is insignificant to the JSON syntax generally does not affect parsing. Spaces inside string values are part of the data and must be preserved.

Q:Can indentation fix invalid JSON?

No. Indentation changes presentation and cannot repair missing commas, invalid quotes, unmatched brackets, or other syntax errors.

Q:What is the difference between JSON indentation and pretty printing?

Indentation is the whitespace used to show nesting. Pretty printing is the broader process of producing human-readable JSON, which commonly includes indentation and line breaks.

Q:Does formatted JSON work in APIs?

Yes. Formatted JSON is still JSON as long as its syntax is valid. Whether an API should transmit formatted or compact output depends on the application's requirements.

Q:Should API responses be indented?

Indentation can make API responses easier for developers to inspect, but compact responses may be preferable when minimizing raw payload size. Transport compression can also affect the practical size difference.

Q:Does JSON indentation affect performance?

Formatting can increase the raw size of JSON, but the practical network impact depends on payload size, compression, request frequency, and the rest of the delivery pipeline.

Q:Can JSON indentation affect Git diffs?

Yes. Consistent indentation generally makes JSON diffs easier to read, while inconsistent formatting can create noisy whitespace changes.

Q:What indentation should I use for a JSON file?

Use the convention already established by the project. If there is no convention, two or four spaces are practical choices for readable JSON.

Q:Can I indent a JSON array?

Yes. Arrays can be formatted with each element on a separate line, and nested objects inside the array can receive additional indentation.

Q:Does minified JSON have indentation?

Normally no. Minification removes unnecessary whitespace, including indentation and most line breaks, to create a compact representation.

Q:Should I format or minify JSON?

Format JSON when people need to read, debug, edit, or document it. Minify it when compact textual output is useful.

Explore More Resources

JSON Formatter

JSON Pretty Print

How to Format JSON

JSON Beautifier

Format JSON File

Format JSON in Browser

JSON Formatting vs Minification

Read more about JSON Formatting vs Minification

How to Validate JSON

JSON Validation

JSON Schema

Fix Invalid JSON

JSON Parsing Errors

Format JSON API Response

Read more about Format JSON API Response

Format REST API Response

Read more about Format REST API Response

Format JSON Payload

Format Webhook JSON

JSON Indentation

Learn how JSON indentation works, how to choose 2-space or 4-space indentation, and how to format nested objects and arrays without changing the underlying data.

Format JSON Online Learn JSON Pretty Print

What is JSON indentation?

Compact

{"user":{"name":"Ramesh","roles":["developer","admin"]}}

Indented

{
  "user": {
    "name": "Ramesh",
    "roles": [
      "developer",
      "admin"
    ]
  }
}

JSON Indentation: Spaces, Nested Objects, Arrays, and Formatting

What Is JSON Indentation?

Is Indentation Required in JSON?

Indented JSON vs Compact JSON

Consider the same object in two forms. The compact version is shorter, while the indented version makes the hierarchy much easier to scan.

Compact JSONjson

{"name":"Ramesh","profile":{"role":"developer","active":true}}

Indented JSONjson

{
  "name": "Ramesh",
  "profile": {
    "role": "developer",
    "active": true
  }
}

How JSON Indentation Shows Nesting

Nested object indentationjson

{
  "user": {
    "profile": {
      "name": "Ramesh",
      "role": "developer"
    }
  }
}

JSON Indentation for Arrays

Array indentationjson

{
  "skills": [
    "Python",
    "FastAPI",
    "PostgreSQL"
  ]
}

Array of objectsjson

{
  "users": [
    {
      "id": 1,
      "name": "Ramesh"
    },
    {
      "id": 2,
      "name": "Alex"
    }
  ]
}

2-Space JSON Indentation

Two-space indentationjson

{
  "user": {
    "name": "Ramesh",
    "active": true
  }
}

4-Space JSON Indentation

Four-space indentationjson

{
    "user": {
        "name": "Ramesh",
        "active": true
    }
}

2 Spaces vs 4 Spaces for JSON

2 spaces

Benefit: Compact and easy to scan

Trade-off: Nesting levels may be slightly less visually separated

4 spaces

Benefit: More visible separation between nesting levels

Trade-off: Deep JSON becomes wider

Tabs

Benefit: Display width can be controlled by the editor

Trade-off: Visual width can vary between environments

Spaces vs Tabs for JSON Indentation

Does JSON Care About Whitespace?

Whitespace inside a string mattersjson

{
  "message": "Hello   world"
}

JSON Indentation Does Not Change the Data

How to Indent JSON Online

Copy the JSON you want to inspect.
Check that the input is valid JSON.
Open a JSON formatting tool.
Paste the JSON into the input area.
Choose the desired indentation level when available.
Format or pretty print the JSON.
Compare the result with the original if the data is important.

/json-formatter

How to Indent JSON in JavaScript

Indent JSON with two spacesjavascript

const formatted = JSON.stringify(data, null, 2);
console.log(formatted);

Indent JSON with four spacesjavascript

const formatted = JSON.stringify(data, null, 4);
console.log(formatted);

Indent a JSON String in JavaScript

Format a JSON stringjavascript

const formatted = JSON.stringify(JSON.parse(jsonText), null, 2);

/guides/format-json-javascript

How to Indent JSON in Python

Python's json.dumps() function supports an indent argument. After parsing JSON with json.loads(), pass indent=2 or another preferred value to generate readable JSON.

Two-space JSON indentation in Pythonpython

import json

data = json.loads(json_text)
formatted = json.dumps(data, indent=2)
print(formatted)

Four-space JSON indentation in Pythonpython

import json

data = json.loads(json_text)
formatted = json.dumps(data, indent=4)
print(formatted)

Indent JSON with jq

jq is useful for inspecting and formatting JSON from the command line. Running jq with a JSON file produces human-readable output with indentation.

Format JSON with jqbash

jq . input.json

JSON Indentation in VS Code

JSON Indentation in Code Editors

JSON File Indentation

/guides/format-json-file

JSON Indentation for API Responses

JSON Indentation for Request Payloads

/guides/format-json-payload

JSON Indentation for Webhook Payloads

/guides/format-webhook-json

Does Indentation Affect JSON File Size?

JSON Indentation and Minification

JSON Indentation vs Pretty Printing

JSON Indentation vs Validation

Can Indentation Fix Invalid JSON?

Indentation for Deeply Nested JSON

Indentation for JSON Arrays of Objects

Indented array of objectsjson

{
  "products": [
    {
      "id": 101,
      "name": "Keyboard",
      "price": 49.99
    },
    {
      "id": 102,
      "name": "Mouse",
      "price": 29.99
    }
  ]
}

Indentation and Git Diffs

JSON Indentation for Documentation

JSON Indentation and Sensitive Data

JSON Indentation for Large Files

Common JSON Indentation Mistakes

Mixing tabs and spaces

Choose one indentation convention for the project.

Using different indentation widths in one file

Use a consistent indentation level throughout the document.

Manually deleting every space

Use a JSON-aware formatter or serializer.

Changing values while formatting

Formatting should change presentation, not data.

Assuming indentation fixes invalid syntax

Validate or repair malformed JSON separately.

Formatting signed webhook bodies before verification

Preserve the original raw request body when exact bytes are required.

JSON Indentation Best Practices

Use a consistent indentation width.
Prefer the project's existing formatting convention.
Use JSON-aware tools rather than manual whitespace editing.
Keep nested objects and arrays visually aligned.
Do not modify string contents while changing indentation.
Format source files when humans need to maintain them.
Generate compact output when a workflow specifically benefits from it.
Use version-control diffs to verify that only intended changes occurred.
Validate JSON separately from formatting when correctness matters.
Preserve raw webhook bodies when signature verification depends on exact bytes.
Avoid exposing sensitive JSON to untrusted online services.

A Simple JSON Indentation Workflow

Keep a copy of the original JSON.
Determine whether the input is supposed to be standard JSON.
Parse or validate the document.
Fix syntax errors if parsing fails.
Format the valid JSON with a consistent indentation level.
Inspect nested objects and arrays.
Compare important data with the original.
Save the formatted version if it is a maintained file.

Choosing the Right Indentation Level

When Not to Indent JSON

JSON Indentation Styles

Factor	readability	width	common Use
2 spaces	High	More compact	General readable JSON
4 spaces	High	Wider	Projects preferring stronger visual nesting
Tabs	Depends on editor settings	Variable	Projects with an explicit tab convention
No indentation	Low for humans	Most compact	Generated or compact JSON

JSON Formatting Examples

Format JSON with 2 spaces in JavaScript

javascript

const formatted = JSON.stringify(data, null, 2);
console.log(formatted);

Format JSON with 4 spaces in JavaScript

javascript

const formatted = JSON.stringify(data, null, 4);
console.log(formatted);

Format a JSON string in JavaScript

javascript

const formatted = JSON.stringify(JSON.parse(jsonText), null, 2);

Format JSON with 2 spaces in Python

python

import json

data = json.loads(json_text)
formatted = json.dumps(data, indent=2)
print(formatted)

Format JSON with 4 spaces in Python

python

import json

data = json.loads(json_text)
formatted = json.dumps(data, indent=4)
print(formatted)

Format JSON with jq

bash

jq . input.json

JSON Indentation Checklist

Choose a consistent indentation style.
Use the project's existing convention when one exists.
Use two or four spaces if you need to establish a new convention.
Keep nested objects one level deeper than their parent.
Indent array elements consistently.
Keep closing braces and brackets aligned with their opening structure.
Do not change string contents while formatting.
Use a JSON-aware formatter instead of manually editing whitespace.
Validate JSON separately when syntax correctness matters.
Keep human-maintained JSON readable.
Use compact JSON when a workflow specifically requires it.
Check Git diffs after automated formatting.
Preserve raw webhook bodies when signatures depend on exact bytes.
Avoid sending confidential JSON to untrusted online tools.

Frequently Asked Questions

Q:What is JSON indentation?

JSON indentation is whitespace used at the beginning of lines to visually represent the nesting of objects and arrays. It improves readability but is not required by the JSON data model.

Q:Is indentation required in JSON?

No. Valid JSON can be written on one line without indentation or formatted across multiple lines with indentation.

Q:How many spaces should JSON indentation use?

Two or four spaces are common choices. There is no universal requirement for one specific indentation width, so project conventions should take priority.

Q:Should JSON use 2 spaces or 4 spaces?

Both are valid formatting choices. Two spaces keep nested JSON relatively compact, while four spaces provide more visual separation. Consistency matters more than the specific number.

Q:Can JSON use tabs for indentation?

Whitespace can be used for formatting JSON, including tabs where permitted. Shared projects often prefer spaces for more predictable visual alignment across editors.

Q:Does JSON indentation change the data?

Proper indentation should only change whitespace used for presentation. It should not change keys, values, objects, or arrays.

Q:Does indentation increase JSON file size?

Yes. Indentation adds whitespace, so formatted JSON is generally larger as raw text than its compact representation.

Q:How do I indent JSON in JavaScript?

Use JSON.stringify(data, null, 2) for two-space indentation or JSON.stringify(data, null, 4) for four-space indentation.

Q:How do I indent a JSON string in JavaScript?

Parse the string first and then serialize it with an indentation argument: JSON.stringify(JSON.parse(jsonText), null, 2).

Q:How do I indent JSON in Python?

Use json.dumps() with the indent argument, such as json.dumps(data, indent=2).

Q:Can I indent JSON online?

Yes. A JSON formatter can parse valid JSON and produce readable output with indentation. Avoid submitting sensitive data to services you do not trust.

Q:Does JSON care about spaces?

Whitespace that is insignificant to the JSON syntax generally does not affect parsing. Spaces inside string values are part of the data and must be preserved.

Q:Can indentation fix invalid JSON?

No. Indentation changes presentation and cannot repair missing commas, invalid quotes, unmatched brackets, or other syntax errors.

Q:What is the difference between JSON indentation and pretty printing?

Indentation is the whitespace used to show nesting. Pretty printing is the broader process of producing human-readable JSON, which commonly includes indentation and line breaks.

Q:Does formatted JSON work in APIs?

Yes. Formatted JSON is still JSON as long as its syntax is valid. Whether an API should transmit formatted or compact output depends on the application's requirements.

Q:Should API responses be indented?

Q:Does JSON indentation affect performance?

Formatting can increase the raw size of JSON, but the practical network impact depends on payload size, compression, request frequency, and the rest of the delivery pipeline.

Q:Can JSON indentation affect Git diffs?

Yes. Consistent indentation generally makes JSON diffs easier to read, while inconsistent formatting can create noisy whitespace changes.

Q:What indentation should I use for a JSON file?

Use the convention already established by the project. If there is no convention, two or four spaces are practical choices for readable JSON.

Q:Can I indent a JSON array?

Yes. Arrays can be formatted with each element on a separate line, and nested objects inside the array can receive additional indentation.

Q:Does minified JSON have indentation?

Normally no. Minification removes unnecessary whitespace, including indentation and most line breaks, to create a compact representation.

Q:Should I format or minify JSON?

Format JSON when people need to read, debug, edit, or document it. Minify it when compact textual output is useful.