How to Format and Validate JSON Online (Plus Common JSON Errors)

JSON is everywhere — API responses, configuration files, data exports, webhook payloads, and NoSQL databases all use it. But raw JSON is often minified into a single unreadable line, or riddled with syntax errors that cause cryptic failures. An online JSON formatter and validator fixes both problems in seconds.

What is JSON and why does formatting matter?

JSON (JavaScript Object Notation) is a lightweight data interchange format. It uses human-readable text to represent structured data as key-value pairs, arrays, and nested objects. Valid JSON looks like this:

{
  "name": "Jane Smith",
  "age": 34,
  "roles": ["admin", "editor"],
  "address": {
    "city": "London",
    "country": "UK"
  }
}

When JSON comes from an API or file export, it is often minified — all whitespace removed to reduce size: {"name":"Jane Smith","age":34,"roles":["admin","editor"]}. That is machine-readable but very difficult for humans to inspect or debug. Formatting (also called “pretty-printing”) adds indentation and line breaks, making the structure immediately readable.

Common JSON errors and what causes them

• Trailing commas — JSON does not allow a comma after the last item in an object or array. Valid in JavaScript but invalid in JSON. This is the most common JSON error.
• Single quotes — JSON requires double quotes for strings. Single-quoted strings are valid in JavaScript but invalid in JSON.
• Unquoted keys — Object keys must be strings in double quotes.{name: "Jane"} is invalid; {"name": "Jane"} is correct.
• Undefined, NaN, or Infinity — These JavaScript values have no JSON equivalent. They cause serialisation errors.
• Missing commas between elements — Forgetting the comma between two properties or array items.
• Mismatched brackets — An unclosed { or [ nested somewhere in complex JSON is easy to miss.
• Invalid escape sequences — Backslashes in strings must be properly escaped (\\ for a literal backslash, \" for a quote inside a string).

Step-by-step: formatting and validating JSON with ToolsGravity

1. Open the JSON Formatter and paste your raw or minified JSON into the input field.
2. Click Format / Validate. The tool either:
   • Returns beautifully indented JSON — confirming it is valid, and
   • Returns an error message with the line number and description of the problem.
3. For invalid JSON, read the error message, find the indicated line in the raw input, and fix the issue. Common fixes: remove the trailing comma, change single to double quotes, add missing brackets.
4. Copy the formatted JSON to use in your project, documentation, or debugging session.
5. If you need to minify JSON (remove all whitespace for production use), use the minify option to generate the compact version.

JSON formatting options

JSON vs JSONC vs JSON5

Standard JSON is strict by design — no comments, no trailing commas, no unquoted keys. Some tools and config formats use relaxed variants:

• JSONC — JSON with comments (used by VS Code settings files)
• JSON5 — More permissive: allows comments, trailing commas, single quotes, and unquoted keys

If you are validating a VS Code config or similar JSONC file, the errors reported by a strict JSON validator are expected — those files are not standard JSON.

Summary

The ToolsGravity JSON Formatter is a daily tool for any developer who works with APIs, configuration files, or data pipelines. Paste your JSON, get it formatted and validated in one click, and copy the result. For JWT tokens (a specific JSON-based format), the dedicated JWT Decoder provides a more specialised view of the token's header, payload, and signature.