Turn compact JSON into readable, indented output without changing the underlying data. Learn practical ways to pretty print JSON in browsers, editors, JavaScript, Python, Node.js, APIs, and command-line tools.

Pretty Print JSON How to Format JSON

What does pretty print JSON mean?

Pretty printing JSON means adding indentation, line breaks, and whitespace so a JSON document is easier for people to read. It does not normally change the keys, values, objects, or arrays. In JavaScript, a common approach is JSON.stringify(JSON.parse(jsonText), null, 2). Pretty printing is primarily a presentation step; it is different from validating, repairing, transforming, or minifying JSON.

Online

Paste valid JSON into a JSON formatter and choose a readable indentation level.

JavaScript

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

Python

Use json.dumps(data, indent=2) for readable output.

jq

Run jq . input.json to pretty print a JSON file.

JSON Pretty Print: How to Format JSON for Readability

Compact JSON is useful for transmission and storage, but it can be difficult to inspect when everything appears on one line. Pretty printing solves that presentation problem by adding line breaks and indentation around objects and arrays. The data stays the same; only its textual representation becomes easier to read. This guide covers online pretty printing, programming-language methods, editor workflows, API responses, JSON files, indentation choices, large documents, and the difference between pretty printing and actual JSON validation.

What Is JSON Pretty Printing?

JSON pretty printing is the process of representing JSON with whitespace that makes its structure visually clear. Objects are usually placed across multiple lines, nested values are indented, and array elements are separated onto readable lines. Pretty printing is sometimes called formatting or beautifying JSON.

Compact / Before

{"name":"Ramesh","skills":["Python","JavaScript"],"active":true}

Formatted / After / Indented / Pretty

{
  "name": "Ramesh",
  "skills": [
    "Python",
    "JavaScript"
  ],
  "active": true
}

Why Pretty Print JSON?

Pretty-printed JSON is easier to inspect when debugging APIs, reviewing configuration files, reading logs, checking nested objects, documenting examples, or comparing changes in source control. Compact JSON remains useful when minimizing payload size matters, but it is harder to scan manually.

Inspecting API responses
Reading request and response payloads
Debugging nested data
Reviewing JSON configuration files
Reading webhook events
Preparing JSON examples for documentation
Reviewing Git changes
Inspecting exported data
Understanding large object and array structures

Pretty Print JSON Online

For a quick one-off task, an online JSON formatter is usually the simplest approach. Paste valid JSON into the formatter, format or pretty print it, then inspect the resulting hierarchy. If the input is malformed, a formatter may report a parsing problem rather than producing formatted output.

Copy the JSON text.
Open the JSON formatter.
Paste the JSON into the input area.
Format or pretty print the JSON.
Inspect nested objects and arrays.
Correct syntax errors if the input cannot be parsed.
Copy the formatted result when needed.

Pretty Print JSON in JavaScript

JavaScript's JSON.stringify() accepts a space argument that controls indentation. Passing 2 produces a common two-space format, while passing 4 produces four-space indentation.

Pretty print an objectjavascript

const data = {
  name: "Ramesh",
  role: "developer",
  active: true
};

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

Pretty print a JSON stringjavascript

const jsonText = '{"name":"Ramesh","active":true}';
const pretty = JSON.stringify(JSON.parse(jsonText), null, 2);
console.log(pretty);

What Does JSON.stringify(data, null, 2) Do?

The first argument is the JavaScript value to serialize. The second argument is the replacer and is null when no property filtering or custom transformation is needed. The third argument specifies the indentation space. A value of 2 produces readable two-space indentation.

javascript

JSON.stringify(data, null, 2)

javascript

JSON.stringify(data, null, 4)

Pretty Print JSON in Node.js

Node.js uses the same JSON.stringify() API as browser JavaScript. This makes it straightforward to produce readable JSON in scripts, command-line utilities, test output, logs, or generated files.

Write pretty JSON to a filejavascript

const fs = require('node:fs');

const data = {
  name: "Ramesh",
  skills: ["Python", "FastAPI"]
};

fs.writeFileSync('output.json', JSON.stringify(data, null, 2) + '
');

Pretty Print JSON in Python

Python's json.dumps() can serialize a Python value into a readable JSON string when an indent value is supplied. json.load() and json.loads() can be used first when the source is a JSON file or string.

Pretty print a Python objectpython

import json

data = {
    "name": "Ramesh",
    "skills": ["Python", "FastAPI"],
    "active": True
}

print(json.dumps(data, indent=2))

Pretty print a JSON stringpython

import json

json_text = '{"name":"Ramesh","active":true}'
data = json.loads(json_text)
pretty = json.dumps(data, indent=2)
print(pretty)

Pretty Print JSON with jq

jq is a command-line JSON processor that can read JSON and output a formatted representation. Running jq with a simple filter is a convenient way to inspect JSON files and command-line API responses.

Pretty print a JSON filebash

jq . input.json

Pretty print piped JSONbash

cat input.json | jq .

Pretty Print JSON in a Browser

Browsers provide several ways to inspect JSON. A JSON formatter can provide a dedicated interface, while browser developer tools can help inspect network responses. The browser console can also parse and stringify JSON when you need a quick manual check.

Browser consolejavascript

JSON.stringify(JSON.parse(jsonText), null, 2)

Pretty Print JSON in VS Code

VS Code and other JSON-aware editors can format JSON files using their built-in document formatting features or configured formatters. This is useful when the JSON is part of a project and should remain readable in source control.

Open the JSON file.
Make sure the file is recognized as JSON.
Run the editor's document-format command.
Review the resulting diff.
Save the file if the formatting is correct.

Pretty Print a JSON File

A JSON file can be pretty printed without changing the logical JSON data. The important distinction is between changing whitespace and editing values. A formatter should not silently modify property names, values, array members, or nesting.

/guides/format-json-file

Pretty Print Nested JSON

Nested objects are one of the main reasons pretty printing is useful. Indentation makes the parent-child relationship visible instead of forcing you to trace braces across a single line.

json

{
  "user": {
    "profile": {
      "name": "Ramesh",
      "location": {
        "country": "Nepal"
      }
    }
  }
}

Pretty Print JSON Arrays

Arrays can contain primitive values, objects, or other arrays. Pretty printing separates array elements onto readable lines and increases indentation for nested structures.

json

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

2-Space vs 4-Space JSON Pretty Printing

Both two-space and four-space indentation are common. JSON itself does not require one indentation width. The important consideration for source-controlled files is consistency with the project's existing convention.

2 spaces

Common choice for JavaScript and many JSON files.

Advantage: Compact while still showing nesting clearly.

4 spaces

Useful when a project or team convention uses four spaces.

Advantage: Provides more visual separation between nesting levels.

Does Pretty Printing Change JSON Data?

Proper pretty printing changes whitespace and line breaks rather than the logical JSON values. A parser should produce the same data structure from the compact and pretty representations when both are valid JSON and semantically equivalent.

Formatting should not be confused with transformations such as renaming properties, sorting keys, removing fields, changing values, or converting JSON into another format.

Pretty Print JSON Without Changing Values

If preserving the data exactly matters, parse the JSON and serialize it with indentation rather than manually editing the text. Review the output when precision matters, especially around numbers, escaping, Unicode, and application-specific serialization behavior.

javascript

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

Pretty Printing vs JSON Formatting

Pretty printing and JSON formatting are commonly used interchangeably. Pretty printing emphasizes readability through indentation and line breaks, while formatting can also refer more broadly to conventions such as whitespace, line endings, or editor configuration.

Pretty Printing vs JSON Beautifying

JSON beautifying generally means the same basic operation: taking compact or difficult-to-read JSON and presenting it with readable indentation and line breaks. Different tools may call the feature a formatter, pretty printer, beautifier, or beautify function.

/guides/json-beautifier

Pretty Printing vs JSON Minification

Pretty printing adds whitespace for human readability. Minification removes unnecessary whitespace to produce a compact representation. They are opposite presentation goals and should be selected based on whether the JSON is primarily being inspected by people or transmitted/stored efficiently.

Pretty print

Human readability

Minify

Compact representation

Pretty Printing vs JSON Validation

Pretty printing is not the same as validating JSON. A formatter must generally parse valid JSON before it can reliably produce formatted output, but validation is specifically concerned with determining whether the input is valid and, at a separate level, whether its structure satisfies defined rules.

Can Pretty Printing Fix Invalid JSON?

No. Pretty printing does not automatically make arbitrary malformed text valid JSON. If parsing fails because of a missing comma, single quotes, trailing commas, invalid escapes, comments, or another syntax problem, the underlying input needs to be corrected first.

Pretty Print JSON API Responses

API responses are often compact because they are intended for machines rather than direct human reading. Pretty printing a response can make nested data, arrays, metadata, pagination, and error objects much easier to inspect during development and debugging.

Pretty print fetch responsejavascript

const response = await fetch(url);
const data = await response.json();
console.log(JSON.stringify(data, null, 2));

Pretty Print JSON Request Payloads

Pretty printing a request payload is useful before sending it or while debugging an API client. It helps developers inspect nested fields and arrays without changing the payload's logical structure. For production requests, compact serialization may be preferable when payload size matters.

/guides/format-json-payload

Pretty Print Webhook JSON

Webhook payloads often contain nested event data, metadata, objects, and arrays. Pretty printing a copy of the received JSON can make event debugging easier. If the webhook uses request signatures, do not replace the original raw body with a formatted representation before signature verification.

/guides/format-webhook-json

Pretty Print JSON for Debugging

Readable JSON can reveal unexpected nesting, missing fields, empty arrays, null values, duplicated application-level data, and unexpected response structures. When debugging an application, preserve the original input and create a formatted representation for inspection instead of modifying the source data blindly.

Pretty Print JSON in Logs

Pretty JSON can make local development logs easier to inspect, but multi-line logs can be harder for log aggregation systems to process. Structured logging with machine-readable fields is often preferable in production. If pretty printing is used for logs, consider whether the logging platform expects one event per line.

Never expose passwords, access tokens, API keys, session identifiers, or other sensitive data merely to make debugging easier.

Pretty Print JSON for Documentation

Pretty-printed examples are easier for readers to understand because indentation makes the structure visible. Documentation examples should be valid JSON when they are presented as JSON, and examples should avoid real credentials or private information.

Pretty Print JSON for Git Diffs

Consistent formatting can make JSON changes easier to review in Git. If a team changes indentation or formatting rules across an existing file, however, the resulting diff may contain many whitespace-only changes. Keep formatting conventions stable when practical.

Pretty Print Large JSON

Pretty printing can significantly increase the number of characters in a large JSON document because indentation and line breaks add whitespace. For very large responses or datasets, formatting a selected portion can be more practical than rendering the entire document at once.

Format only the section being investigated when possible.
Use streaming or command-line tools for large files.
Avoid loading huge documents repeatedly in memory when a streaming approach is appropriate.
Use compact JSON for transmission when unnecessary whitespace increases payload size.
Keep a formatted copy for human inspection when useful.

Pretty Print JSON with Sensitive Data

Readable output can make sensitive information easier to notice, but it can also make it easier to copy into logs, tickets, screenshots, or external tools. Before using an online formatter, remove secrets and private data when the payload is not intended to leave the local environment.

Remove API keys.
Remove authentication tokens.
Remove passwords.
Remove session identifiers.
Remove private customer information.
Use local formatting tools for confidential payloads when appropriate.

Pretty Print JSON from an API Error Response

Error responses are often valuable during debugging because they can contain an error code, message, request identifier, or validation details. Pretty printing makes those fields easier to inspect. However, first confirm that the response body is actually JSON; an HTTP error can also return HTML or plain text.

Pretty Print JSON Strings Containing JSON

Sometimes a JSON property contains another JSON document encoded as a string. The outer JSON must be parsed first, and the inner string may require a second parsing step if it is itself valid JSON. Formatting the outer document does not automatically decode the nested string.

Nested JSON stringjavascript

const outer = JSON.parse(text);
const inner = JSON.parse(outer.payload);
console.log(JSON.stringify(inner, null, 2));

Pretty Print JSON with Unicode Characters

JSON supports Unicode text. Pretty printing should preserve string content while changing presentation whitespace. When moving formatted JSON between tools, verify that encoding is handled correctly if characters appear corrupted.

Pretty Print JSON Numbers

Pretty printing should not be treated as a way to alter numeric values. When parsing and re-serializing JSON through a programming language, be aware that the language's number representation and serializer can have implications for very large or otherwise special numeric values. If exact textual preservation matters, do not assume parse-and-reserialize is byte-for-byte identical.

Pretty Print JSON with a Custom Indentation Level

The indentation width is a presentation choice. JavaScript's JSON.stringify() accepts a space argument, and Python's json.dumps() accepts indent. Many formatters also let you choose two or four spaces.

Two spacesjavascript

JSON.stringify(data, null, 2)

Four spacesjavascript

JSON.stringify(data, null, 4)

Four spacespython

json.dumps(data, indent=4)

Pretty Print JSON Without Installing Software

For a quick task, an online formatter or browser console can be enough. For private data, local tools such as VS Code, jq, Python, or a project-specific formatter may be a better fit because the JSON can remain within the development environment.

When Pretty Printing Is Not the Right Operation

Pretty printing is appropriate when readability is the goal. Use validation when you need to check syntax, JSON Schema when you need structural rules, repair when the input is malformed, minification when compactness matters, and transformation when the data itself needs to change.

Make JSON easier to read

Pretty print / format

Check whether JSON syntax is valid

JSON validation

Repair malformed JSON

JSON repair workflow

Check required fields and data types

JSON Schema or application validation

Reduce unnecessary whitespace

JSON minification

Change fields or data structure

JSON transformation

A Practical JSON Pretty Print Workflow

The simplest workflow depends on where the JSON comes from, but the underlying process is consistent: preserve the original, determine whether it is valid JSON, create a readable representation, inspect the structure, and make any actual data changes separately.

Obtain the JSON text or parsed data.
Keep the original input unchanged.
Parse the JSON when working from raw text.
Pretty print it with a consistent indentation level.
Inspect objects, arrays, and nested values.
Validate against a schema if the application requires structural validation.
Make data changes separately from formatting.
Use minified output only when compact transmission or storage is required.

Common JSON Pretty Print Mistakes

Most problems come from confusing presentation with data processing or assuming that every piece of text resembling JSON can be formatted directly.

Trying to pretty print malformed JSON without first locating the syntax error.
Assuming indentation is required for valid JSON.
Treating JavaScript object literal syntax as standard JSON.
Using pretty-printed payloads unnecessarily in bandwidth-sensitive production requests.
Logging sensitive API responses without redaction.
Replacing a webhook's raw body before signature verification.
Changing values while manually formatting a document.
Using inconsistent indentation across a project.
Assuming formatted JSON has passed schema validation.
Parsing and reserializing data when exact textual preservation is required.

JSON Pretty Print Best Practices

Use a JSON-aware formatter rather than manually inserting whitespace, keep indentation consistent, validate malformed input separately, and distinguish development output from production payload requirements.

Use a JSON-aware formatter.
Choose a consistent indentation convention.
Keep original input when debugging external data.
Validate JSON separately from formatting.
Use schema validation for application-specific structure.
Pretty print API responses for development and inspection.
Avoid unnecessary whitespace in production payloads when payload size matters.
Redact secrets before sharing or logging JSON.
Preserve raw webhook bodies when signatures require exact bytes.
Review Git diffs after formatting source-controlled JSON.
Avoid using formatting as a substitute for repairing malformed JSON.

JSON Formatting Examples

Pretty Print JSON in JavaScript

javascript

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

Pretty Print a JSON String in JavaScript

javascript

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

Pretty Print JSON in Python

python

import json

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

Pretty Print JSON with jq

bash

jq . input.json

Pretty Print a Fetch Response

javascript

const response = await fetch(url);
const data = await response.json();
console.log(JSON.stringify(data, null, 2));

Pretty Print a Nested JSON String

javascript

const outer = JSON.parse(text);
const inner = JSON.parse(outer.payload);
console.log(JSON.stringify(inner, null, 2));

JSON Pretty Print Checklist

Confirm that the input is actually JSON.
Validate malformed input before trying to format it.
Use a JSON-aware formatter.
Choose a consistent indentation level.
Use two or four spaces according to project convention.
Keep whitespace inside string values unchanged.
Inspect nested objects and arrays after formatting.
Keep the original input when debugging external data.
Review Git diffs after formatting source-controlled JSON.
Avoid unnecessary pretty printing for bandwidth-sensitive production payloads.
Redact API keys, passwords, tokens, and private data before sharing JSON.
Preserve raw webhook bodies when signature verification requires exact bytes.
Use schema validation when application structure must be checked.
Use minification when a compact representation is required.

Frequently Asked Questions

Q:What is JSON pretty print?

JSON pretty printing means adding indentation, line breaks, and whitespace to make JSON easier for people to read. It normally does not change the logical data.

Q:How do I pretty print JSON?

Use a JSON formatter for a quick online workflow, JSON.stringify(data, null, 2) in JavaScript, json.dumps(data, indent=2) in Python, or jq . input.json from the command line.

Q:How do I pretty print JSON online?

Paste valid JSON into a JSON formatting tool, run the formatting operation, and copy the readable result. Avoid sending confidential payloads to online tools unless you are comfortable with their handling.

Q:What does JSON.stringify(data, null, 2) mean?

It serializes a JavaScript value as JSON text. The null argument means no replacer is used, and 2 requests two spaces of indentation.

Q:How do I pretty print a JSON string in JavaScript?

Parse the string and then serialize the resulting value with indentation: JSON.stringify(JSON.parse(jsonText), null, 2). The input must be valid JSON.

Q:How do I pretty print JSON in Python?

Use json.dumps(data, indent=2) or another indentation level. If the source is a JSON string, parse it with json.loads() first.

Q:How do I pretty print JSON with jq?

Run jq . input.json. jq parses the file and outputs a readable JSON representation.

Q:Does pretty printing change JSON data?

Proper formatting changes the textual presentation, such as whitespace and line breaks, rather than the logical keys and values. Parse-and-reserialize workflows can have language-specific serialization effects, so byte-for-byte preservation should not be assumed.

Q:Is pretty printed JSON valid JSON?

Yes, if the underlying JSON syntax is valid. Indentation and line breaks are permitted JSON whitespace outside strings.

Q:Is JSON indentation required?

No. JSON can be compact or formatted with indentation. Whitespace is mainly used to improve readability.

Q:Should I use 2 spaces or 4 spaces for JSON?

Both are valid. Use the convention established by the project or team and keep it consistent.

Q:What is the difference between pretty print and JSON formatting?

The terms are often used interchangeably. Pretty printing specifically emphasizes readable indentation and line breaks, while formatting can refer more broadly to a project's JSON presentation rules.

Q:What is the difference between a JSON pretty printer and a JSON beautifier?

In most practical contexts, they perform the same basic task: turning valid JSON into a more readable representation with indentation and line breaks.

Q:Can pretty printing fix invalid JSON?

No. Pretty printing is not a general repair mechanism. Missing commas, invalid quotes, trailing commas, invalid escapes, comments, and other syntax errors must be corrected first.

Q:Can I pretty print invalid JSON?

A normal JSON formatter needs to parse the input, so malformed JSON may be rejected. Repair or syntax-debugging tools are more appropriate when the input is invalid.

Q:Does pretty printing increase JSON file size?

Yes. Indentation and line breaks add whitespace, so a pretty-printed representation generally contains more characters than the equivalent compact representation.

Q:Should API responses be pretty printed?

Pretty printing is useful when developers are inspecting responses. Production APIs commonly use compact JSON when reducing payload size is useful.

Q:How do I pretty print an API response in JavaScript?

Parse the response and pass the resulting value to JSON.stringify() with an indentation argument, such as JSON.stringify(data, null, 2).

Q:How do I pretty print a JSON file?

Open the file in a JSON-aware editor and run its formatting command, or use a command-line tool such as jq. Review the resulting diff before committing source-controlled files.

Q:How do I pretty print nested JSON?

Use a JSON-aware formatter or a serializer with indentation. Nested objects and arrays will be represented with additional indentation levels.

Q:How do I pretty print a JSON array?

Use the same formatter or serializer used for objects. The formatter will place array elements on readable lines and indent nested structures.

Q:Can pretty printing change whitespace inside JSON strings?

Formatting whitespace outside JSON strings can be changed, but whitespace characters that are part of a string value are data and should not be altered.

Q:Can pretty printing change numbers?

A formatting operation should not intentionally change JSON numbers, but parsing and reserializing through a programming language can introduce representation differences for some numeric values. Exact textual preservation requires a more careful approach.

Q:Is pretty printing the same as minifying JSON?

No. Pretty printing adds whitespace for readability, while minification removes unnecessary whitespace to make JSON more compact.

Q:Is pretty printing the same as JSON validation?

No. Pretty printing concerns presentation. Validation checks whether JSON syntax is valid and may separately check whether its structure satisfies a schema or application contract.

Q:Should I pretty print JSON in production logs?

It depends on the logging system. Multi-line pretty JSON can be harder for log aggregation and parsing. Structured one-event-per-record logging is often more practical for production systems.

Q:Is it safe to pretty print sensitive JSON online?

Do not assume confidential data is safe to paste into an online service. Remove secrets and private information or use a local formatter when the payload is sensitive.

Q:Can I pretty print webhook JSON?

Yes. Pretty printing a copy of a webhook payload is useful for inspection. If signature verification depends on the raw request body, preserve and verify the original body before formatting or transforming it.

Q:Why does my JSON formatter reject my input?

The input may contain invalid JSON syntax, such as missing punctuation, single quotes, trailing commas, comments, invalid escape sequences, or incomplete data. It may also not be JSON at all.

Q:Why does JSON.parse fail before I can pretty print the JSON?

JSON.parse() only accepts valid JSON text. If parsing fails, inspect the error location and correct the malformed input before attempting to pretty print it.

Explore More Resources

JSON Formatter

How to Format JSON

JSON Beautifier

JSON Indentation

Format JSON File

Format JSON in Browser

JSON Formatting vs Minification

Read more about JSON Formatting vs Minification

JSON Parse Errors

Fix Invalid JSON

How to Validate JSON

JSON Validation

JSON Schema

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

Debug JSON API Response

JSON Minifier

JSON Pretty Print

Pretty Print JSON How to Format JSON

What does pretty print JSON mean?

Online

Paste valid JSON into a JSON formatter and choose a readable indentation level.

JavaScript

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

Python

Use json.dumps(data, indent=2) for readable output.

jq

Run jq . input.json to pretty print a JSON file.

JSON Pretty Print: How to Format JSON for Readability

What Is JSON Pretty Printing?

Compact / Before

{"name":"Ramesh","skills":["Python","JavaScript"],"active":true}

Formatted / After / Indented / Pretty

{
  "name": "Ramesh",
  "skills": [
    "Python",
    "JavaScript"
  ],
  "active": true
}

Why Pretty Print JSON?

Inspecting API responses
Reading request and response payloads
Debugging nested data
Reviewing JSON configuration files
Reading webhook events
Preparing JSON examples for documentation
Reviewing Git changes
Inspecting exported data
Understanding large object and array structures

Pretty Print JSON Online

Copy the JSON text.
Open the JSON formatter.
Paste the JSON into the input area.
Format or pretty print the JSON.
Inspect nested objects and arrays.
Correct syntax errors if the input cannot be parsed.
Copy the formatted result when needed.

Pretty Print JSON in JavaScript

JavaScript's JSON.stringify() accepts a space argument that controls indentation. Passing 2 produces a common two-space format, while passing 4 produces four-space indentation.

Pretty print an objectjavascript

const data = {
  name: "Ramesh",
  role: "developer",
  active: true
};

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

Pretty print a JSON stringjavascript

const jsonText = '{"name":"Ramesh","active":true}';
const pretty = JSON.stringify(JSON.parse(jsonText), null, 2);
console.log(pretty);

What Does JSON.stringify(data, null, 2) Do?

javascript

JSON.stringify(data, null, 2)

javascript

JSON.stringify(data, null, 4)

Pretty Print JSON in Node.js

Node.js uses the same JSON.stringify() API as browser JavaScript. This makes it straightforward to produce readable JSON in scripts, command-line utilities, test output, logs, or generated files.

Write pretty JSON to a filejavascript

const fs = require('node:fs');

const data = {
  name: "Ramesh",
  skills: ["Python", "FastAPI"]
};

fs.writeFileSync('output.json', JSON.stringify(data, null, 2) + '
');

Pretty Print JSON in Python

Pretty print a Python objectpython

import json

data = {
    "name": "Ramesh",
    "skills": ["Python", "FastAPI"],
    "active": True
}

print(json.dumps(data, indent=2))

Pretty print a JSON stringpython

import json

json_text = '{"name":"Ramesh","active":true}'
data = json.loads(json_text)
pretty = json.dumps(data, indent=2)
print(pretty)

Pretty Print JSON with jq

jq is a command-line JSON processor that can read JSON and output a formatted representation. Running jq with a simple filter is a convenient way to inspect JSON files and command-line API responses.

Pretty print a JSON filebash

jq . input.json

Pretty print piped JSONbash

cat input.json | jq .

Pretty Print JSON in a Browser

Browser consolejavascript

JSON.stringify(JSON.parse(jsonText), null, 2)

Pretty Print JSON in VS Code

Open the JSON file.
Make sure the file is recognized as JSON.
Run the editor's document-format command.
Review the resulting diff.
Save the file if the formatting is correct.

Pretty Print a JSON File

/guides/format-json-file

Pretty Print Nested JSON

Nested objects are one of the main reasons pretty printing is useful. Indentation makes the parent-child relationship visible instead of forcing you to trace braces across a single line.

json

{
  "user": {
    "profile": {
      "name": "Ramesh",
      "location": {
        "country": "Nepal"
      }
    }
  }
}

Pretty Print JSON Arrays

Arrays can contain primitive values, objects, or other arrays. Pretty printing separates array elements onto readable lines and increases indentation for nested structures.

json

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

2-Space vs 4-Space JSON Pretty Printing

2 spaces

Common choice for JavaScript and many JSON files.

Advantage: Compact while still showing nesting clearly.

4 spaces

Useful when a project or team convention uses four spaces.

Advantage: Provides more visual separation between nesting levels.

Does Pretty Printing Change JSON Data?

Formatting should not be confused with transformations such as renaming properties, sorting keys, removing fields, changing values, or converting JSON into another format.

Pretty Print JSON Without Changing Values

javascript

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

Pretty Printing vs JSON Formatting

Pretty Printing vs JSON Beautifying

/guides/json-beautifier

Pretty Printing vs JSON Minification

Pretty print

Human readability

Minify

Compact representation

Pretty Printing vs JSON Validation

Can Pretty Printing Fix Invalid JSON?

Pretty Print JSON API Responses

Pretty print fetch responsejavascript

const response = await fetch(url);
const data = await response.json();
console.log(JSON.stringify(data, null, 2));

Pretty Print JSON Request Payloads

/guides/format-json-payload

Pretty Print Webhook JSON

/guides/format-webhook-json

Pretty Print JSON for Debugging

Pretty Print JSON in Logs

Never expose passwords, access tokens, API keys, session identifiers, or other sensitive data merely to make debugging easier.

Pretty Print JSON for Documentation

Pretty Print JSON for Git Diffs

Pretty Print Large JSON

Format only the section being investigated when possible.
Use streaming or command-line tools for large files.
Avoid loading huge documents repeatedly in memory when a streaming approach is appropriate.
Use compact JSON for transmission when unnecessary whitespace increases payload size.
Keep a formatted copy for human inspection when useful.

Pretty Print JSON with Sensitive Data

Remove API keys.
Remove authentication tokens.
Remove passwords.
Remove session identifiers.
Remove private customer information.
Use local formatting tools for confidential payloads when appropriate.

Pretty Print JSON from an API Error Response

Pretty Print JSON Strings Containing JSON

Nested JSON stringjavascript

const outer = JSON.parse(text);
const inner = JSON.parse(outer.payload);
console.log(JSON.stringify(inner, null, 2));

Pretty Print JSON with Unicode Characters

Pretty Print JSON Numbers

Pretty Print JSON with a Custom Indentation Level

Two spacesjavascript

JSON.stringify(data, null, 2)

Four spacesjavascript

JSON.stringify(data, null, 4)

Four spacespython

json.dumps(data, indent=4)

Pretty Print JSON Without Installing Software

When Pretty Printing Is Not the Right Operation

Make JSON easier to read

Pretty print / format

Check whether JSON syntax is valid

JSON validation

Repair malformed JSON

JSON repair workflow

Check required fields and data types

JSON Schema or application validation

Reduce unnecessary whitespace

JSON minification

Change fields or data structure

JSON transformation

A Practical JSON Pretty Print Workflow

Obtain the JSON text or parsed data.
Keep the original input unchanged.
Parse the JSON when working from raw text.
Pretty print it with a consistent indentation level.
Inspect objects, arrays, and nested values.
Validate against a schema if the application requires structural validation.
Make data changes separately from formatting.
Use minified output only when compact transmission or storage is required.

Common JSON Pretty Print Mistakes

Most problems come from confusing presentation with data processing or assuming that every piece of text resembling JSON can be formatted directly.

Trying to pretty print malformed JSON without first locating the syntax error.
Assuming indentation is required for valid JSON.
Treating JavaScript object literal syntax as standard JSON.
Using pretty-printed payloads unnecessarily in bandwidth-sensitive production requests.
Logging sensitive API responses without redaction.
Replacing a webhook's raw body before signature verification.
Changing values while manually formatting a document.
Using inconsistent indentation across a project.
Assuming formatted JSON has passed schema validation.
Parsing and reserializing data when exact textual preservation is required.

JSON Pretty Print Best Practices

Use a JSON-aware formatter.
Choose a consistent indentation convention.
Keep original input when debugging external data.
Validate JSON separately from formatting.
Use schema validation for application-specific structure.
Pretty print API responses for development and inspection.
Avoid unnecessary whitespace in production payloads when payload size matters.
Redact secrets before sharing or logging JSON.
Preserve raw webhook bodies when signatures require exact bytes.
Review Git diffs after formatting source-controlled JSON.
Avoid using formatting as a substitute for repairing malformed JSON.

JSON Formatting Examples

Pretty Print JSON in JavaScript

javascript

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

Pretty Print a JSON String in JavaScript

javascript

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

Pretty Print JSON in Python

python

import json

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

Pretty Print JSON with jq

bash

jq . input.json

Pretty Print a Fetch Response

javascript

const response = await fetch(url);
const data = await response.json();
console.log(JSON.stringify(data, null, 2));

Pretty Print a Nested JSON String

javascript

const outer = JSON.parse(text);
const inner = JSON.parse(outer.payload);
console.log(JSON.stringify(inner, null, 2));

JSON Pretty Print Checklist

Confirm that the input is actually JSON.
Validate malformed input before trying to format it.
Use a JSON-aware formatter.
Choose a consistent indentation level.
Use two or four spaces according to project convention.
Keep whitespace inside string values unchanged.
Inspect nested objects and arrays after formatting.
Keep the original input when debugging external data.
Review Git diffs after formatting source-controlled JSON.
Avoid unnecessary pretty printing for bandwidth-sensitive production payloads.
Redact API keys, passwords, tokens, and private data before sharing JSON.
Preserve raw webhook bodies when signature verification requires exact bytes.
Use schema validation when application structure must be checked.
Use minification when a compact representation is required.

Frequently Asked Questions

Q:What is JSON pretty print?

JSON pretty printing means adding indentation, line breaks, and whitespace to make JSON easier for people to read. It normally does not change the logical data.

Q:How do I pretty print JSON?

Use a JSON formatter for a quick online workflow, JSON.stringify(data, null, 2) in JavaScript, json.dumps(data, indent=2) in Python, or jq . input.json from the command line.

Q:How do I pretty print JSON online?

Q:What does JSON.stringify(data, null, 2) mean?

It serializes a JavaScript value as JSON text. The null argument means no replacer is used, and 2 requests two spaces of indentation.

Q:How do I pretty print a JSON string in JavaScript?

Parse the string and then serialize the resulting value with indentation: JSON.stringify(JSON.parse(jsonText), null, 2). The input must be valid JSON.

Q:How do I pretty print JSON in Python?

Use json.dumps(data, indent=2) or another indentation level. If the source is a JSON string, parse it with json.loads() first.

Q:How do I pretty print JSON with jq?

Run jq . input.json. jq parses the file and outputs a readable JSON representation.

Q:Does pretty printing change JSON data?

Q:Is pretty printed JSON valid JSON?

Yes, if the underlying JSON syntax is valid. Indentation and line breaks are permitted JSON whitespace outside strings.

Q:Is JSON indentation required?

No. JSON can be compact or formatted with indentation. Whitespace is mainly used to improve readability.

Q:Should I use 2 spaces or 4 spaces for JSON?

Both are valid. Use the convention established by the project or team and keep it consistent.

Q:What is the difference between pretty print and JSON formatting?

The terms are often used interchangeably. Pretty printing specifically emphasizes readable indentation and line breaks, while formatting can refer more broadly to a project's JSON presentation rules.

Q:What is the difference between a JSON pretty printer and a JSON beautifier?

In most practical contexts, they perform the same basic task: turning valid JSON into a more readable representation with indentation and line breaks.

Q:Can pretty printing fix invalid JSON?

No. Pretty printing is not a general repair mechanism. Missing commas, invalid quotes, trailing commas, invalid escapes, comments, and other syntax errors must be corrected first.

Q:Can I pretty print invalid JSON?

A normal JSON formatter needs to parse the input, so malformed JSON may be rejected. Repair or syntax-debugging tools are more appropriate when the input is invalid.

Q:Does pretty printing increase JSON file size?

Yes. Indentation and line breaks add whitespace, so a pretty-printed representation generally contains more characters than the equivalent compact representation.

Q:Should API responses be pretty printed?

Pretty printing is useful when developers are inspecting responses. Production APIs commonly use compact JSON when reducing payload size is useful.

Q:How do I pretty print an API response in JavaScript?

Parse the response and pass the resulting value to JSON.stringify() with an indentation argument, such as JSON.stringify(data, null, 2).

Q:How do I pretty print a JSON file?

Open the file in a JSON-aware editor and run its formatting command, or use a command-line tool such as jq. Review the resulting diff before committing source-controlled files.

Q:How do I pretty print nested JSON?

Use a JSON-aware formatter or a serializer with indentation. Nested objects and arrays will be represented with additional indentation levels.

Q:How do I pretty print a JSON array?

Use the same formatter or serializer used for objects. The formatter will place array elements on readable lines and indent nested structures.

Q:Can pretty printing change whitespace inside JSON strings?

Formatting whitespace outside JSON strings can be changed, but whitespace characters that are part of a string value are data and should not be altered.

Q:Can pretty printing change numbers?

Q:Is pretty printing the same as minifying JSON?

No. Pretty printing adds whitespace for readability, while minification removes unnecessary whitespace to make JSON more compact.

Q:Is pretty printing the same as JSON validation?

No. Pretty printing concerns presentation. Validation checks whether JSON syntax is valid and may separately check whether its structure satisfies a schema or application contract.

Q:Should I pretty print JSON in production logs?

It depends on the logging system. Multi-line pretty JSON can be harder for log aggregation and parsing. Structured one-event-per-record logging is often more practical for production systems.

Q:Is it safe to pretty print sensitive JSON online?

Do not assume confidential data is safe to paste into an online service. Remove secrets and private information or use a local formatter when the payload is sensitive.

Q:Can I pretty print webhook JSON?

Q:Why does my JSON formatter reject my input?

The input may contain invalid JSON syntax, such as missing punctuation, single quotes, trailing commas, comments, invalid escape sequences, or incomplete data. It may also not be JSON at all.

Q:Why does JSON.parse fail before I can pretty print the JSON?

JSON.parse() only accepts valid JSON text. If parsing fails, inspect the error location and correct the malformed input before attempting to pretty print it.