How to Format JSON Correctly

By Deepak Kumar Developer & builder of JSON Formatter Hub · About the author

Last updated: June 2026 · Published by JSON Formatter Hub · Report an issue

Formatting JSON correctly is essential for readability, maintainability, and debugging. Well-formatted JSON is easier to read, understand, and work with, whether you're developing applications, debugging API responses, or storing configuration data. This guide will teach you the best practices for formatting JSON and show you how to use tools to format JSON automatically.

This guide is designed for developers, testers, and students who work with JSON data regularly. You'll learn about proper indentation, spacing, line breaks, and formatting conventions that make JSON both human-readable and machine-parseable. We'll also cover common formatting mistakes and how to avoid them.

Whether you're working with API responses, configuration files, or data storage, understanding how to format JSON properly will make your work more efficient and professional. By the end of this guide, you'll know exactly how to format JSON for different scenarios and when to use formatted versus minified JSON.

Understanding JSON Formatting

JSON formatting refers to the visual presentation of JSON data. While JSON itself doesn't require specific formatting to be valid (computers can parse it regardless of spacing), proper formatting makes JSON human-readable. Formatting includes indentation, line breaks, and spacing that organize the data structure visually.

There are two main approaches to JSON formatting:

• Formatted (Pretty) JSON: JSON with indentation, line breaks, and proper spacing. Used for readability, debugging, and development.
• Minified JSON: JSON with all unnecessary whitespace removed. Used for production to reduce file size and improve transmission speed.

Most of the time, you'll want formatted JSON during development and minified JSON in production. However, understanding both formats is important for working effectively with JSON data.

Core Formatting Principles

1. Indentation

Indentation is the most important aspect of JSON formatting. It visually represents the hierarchy of nested objects and arrays. The standard practice is to use either 2 spaces or 4 spaces per indentation level. Most developers prefer 2 spaces for JSON, as it keeps the code more compact.

Example with 2-space indentation:

{
  "user": {
    "name": "John Doe",
    "settings": {
      "theme": "dark",
      "notifications": true
    }
  }
}

Consistent indentation makes it easy to see which properties belong to which objects and how deeply nested the data structure is.

2. Line Breaks

Each key-value pair in an object should typically be on its own line. This makes it easy to scan and read the data. Arrays with multiple elements should also have each element on its own line when the elements are objects or complex structures.

Well-formatted object:

{
  "name": "John",
  "age": 30,
  "city": "New York",
  "email": "john@example.com"
}

Well-formatted array:

[
  {"name": "Alice", "age": 25},
  {"name": "Bob", "age": 30},
  {"name": "Charlie", "age": 35}
]

3. Spacing

Proper spacing improves readability. In JSON, you should have:

• A space after the colon that separates keys from values
• A space after commas (but not before)
• No spaces inside brackets or braces (except for content)

Correct spacing:

{"name": "John", "age": 30}

Incorrect spacing:

{ "name":"John","age":30 }

Practical Examples

Example 1: Simple Object Formatting

Here's a simple user object, first as minified JSON, then as properly formatted JSON:

Minified (production):

{"id":12345,"username":"johndoe","email":"john@example.com","active":true}

Formatted (development):

{
  "id": 12345,
  "username": "johndoe",
  "email": "john@example.com",
  "active": true
}

Example 2: Nested Objects

When dealing with nested objects, proper indentation becomes crucial:

{
  "company": {
    "name": "Tech Corp",
    "address": {
      "street": "123 Main St",
      "city": "San Francisco",
      "state": "CA",
      "zip": "94102"
    },
    "employees": 150
  }
}

Example 3: Arrays with Objects

Arrays containing objects should have each object on its own line:

{
  "products": [
    {
      "id": 1,
      "name": "Laptop",
      "price": 999.99,
      "inStock": true
    },
    {
      "id": 2,
      "name": "Mouse",
      "price": 29.99,
      "inStock": false
    }
  ]
}

Example 4: Complex Nested Structure

Real-world JSON often contains deeply nested structures. Here's an example of a properly formatted API response:

{
  "status": "success",
  "data": {
    "user": {
      "id": 12345,
      "profile": {
        "name": "John Doe",
        "email": "john@example.com",
        "preferences": {
          "theme": "dark",
          "language": "en",
          "notifications": {
            "email": true,
            "push": false,
            "sms": false
          }
        }
      },
      "orders": [
        {
          "orderId": "ORD-001",
          "date": "2024-01-15",
          "total": 149.99,
          "items": ["item1", "item2"]
        }
      ]
    }
  }
}

Common Formatting Mistakes

Even experienced developers make formatting mistakes. Here are the most common issues and how to avoid them:

1. Inconsistent Indentation

Mixing tabs and spaces, or using different indentation levels, makes JSON hard to read. Always use consistent indentation throughout your JSON file.

❌ Bad:

{
  "name": "John",
    "age": 30,
  "city": "New York"
}

✅ Good:

{
  "name": "John",
  "age": 30,
  "city": "New York"
}

2. Missing Line Breaks

Putting everything on one line makes JSON unreadable, even if it's technically valid.

❌ Bad:

{"users":[{"name":"Alice","age":25},{"name":"Bob","age":30}]}

✅ Good:

{
  "users": [
    {"name": "Alice", "age": 25},
    {"name": "Bob", "age": 30}
  ]
}

3. Trailing Commas

JSON does not allow trailing commas. Always remove the comma after the last element.

❌ Bad:

{
  "name": "John",
  "age": 30,
}

✅ Good:

{
  "name": "John",
  "age": 30
}

4. Incorrect Spacing

Proper spacing around colons and commas improves readability significantly.

❌ Bad:

{"name":"John","age":30}

✅ Good:

{"name": "John", "age": 30}

When to Use Formatted vs Minified JSON

Understanding when to use formatted versus minified JSON is important for different scenarios:

Use Formatted JSON For:

• Development: When writing or editing JSON manually
• Debugging: When troubleshooting API responses or data issues
• Configuration Files: When storing settings that humans need to read and modify
• Documentation: When showing examples in documentation or tutorials
• Code Reviews: When reviewing JSON data in pull requests

Use Minified JSON For:

• Production APIs: To reduce response size and improve transmission speed
• Web Applications: To minimize bandwidth usage
• Storage: When file size is a concern
• Performance: When every byte counts in high-traffic applications

How Our Tool Helps

Manually formatting JSON can be time-consuming and error-prone, especially with large or complex data structures. Our free JSON Formatter makes formatting JSON quick and effortless:

• Instant Formatting: Paste your JSON and get perfectly formatted output in seconds with proper indentation and line breaks.
• Validation: Our tool validates your JSON while formatting it, catching syntax errors before they cause problems.
• Minify Option: Convert formatted JSON to minified JSON for production use with a single click.
• Beautify: Transform messy, unreadable JSON into clean, well-structured code.
• Tree View: Visualize complex JSON structures in an interactive tree format for better understanding.
• Privacy: All processing happens in your browser—your data never leaves your computer.

Whether you're working with API responses, configuration files, or learning JSON formatting, our tool handles everything instantly. Simply paste your JSON data, and our formatter will apply proper indentation, spacing, and line breaks automatically.

If you encounter formatting issues or syntax errors, check out our guide on common JSON errors and how to fix them. For comparing two JSON files to see formatting differences, use our JSON Compare tool.

New to JSON? Start with our comprehensive guide on what JSON is to understand the fundamentals before diving into formatting.

Conclusion

Properly formatted JSON is essential for readability, maintainability, and professional development practices. By following the principles outlined in this guide—consistent indentation, proper line breaks, and correct spacing—you'll create JSON that is both human-readable and machine-parseable.

Remember that formatting is about making your code accessible to both humans and machines. Well-formatted JSON is easier to debug, review, and maintain. Use formatted JSON during development and minified JSON in production to balance readability with performance.

Don't waste time manually formatting JSON. Use our free JSON Formatter to format, validate, and beautify your JSON data instantly. All processing happens securely in your browser, ensuring your data remains completely private.