JSON Formatter & Validator

DEVELOPER FORMAT JSON VALIDATE

About this tool

Format, validate and minify JSON instantly — with clear error messages and line numbers.

Format, validate and minify JSON instantly — with clear error messages and line numbers. Free, no signup, works entirely in your browser.

RT-DEV-002 · Developer Tools

Input JSON

0 chars

How to Use the JSON Formatter

Paste your raw or minified JSON

Drop in any JSON string — from an API response, config file, or log output. The textarea accepts any valid or invalid JSON so errors can be detected and reported.

Choose your indent preference

Select 2 spaces, 4 spaces, or Tab to match your codebase style guide. The indent setting also applies when re-formatting — switch at any time and the output updates instantly.

Click Format to pretty-print and validate

The tool parses your JSON and highlights errors with exact positions. A green badge confirms valid JSON. A red error banner pinpoints exactly what went wrong so you can fix it immediately.

Copy or download the result

One-click copy to clipboard or download as a .json file ready to use in your project. Line numbers in the output make it easy to navigate large JSON documents.

JSON — The Language of Modern APIs

What Is JSON and Why Formatting Matters

JSON — JavaScript Object Notation — was born from JavaScript's object literal syntax but has long since escaped its origins to become the lingua franca of the modern web. Formalised in RFC 8259 (2017) and ECMA-404 (2013), JSON is a lightweight, human-readable text format that represents structured data as key-value pairs, arrays, and nested objects. Every major programming language — Python, Java, Go, Rust, PHP, Swift — ships with first-class JSON support.

When data travels over a network, minimising bytes matters. APIs typically return minified JSON — a compact single-line string with all whitespace stripped. While efficient for machines, minified JSON is painful to read. A 200-line API response collapsed into a single line turns routine debugging into a hunt through noise. Formatted JSON restores hierarchy and indentation, making nested structures immediately visible and letting developers spot missing fields, wrong types, or structural issues at a glance.

The cost of malformed JSON in production is real. A missing closing brace, a trailing comma, or an unquoted key causes the entire parse to fail — throwing exceptions, breaking user flows, and producing cryptic error messages downstream. Catching these errors before deployment — in a formatter that shows the exact character position — is far cheaper than diagnosing a production incident at 2 AM.

Common JSON Errors and How to Fix Them

JSON's syntax rules are stricter than many developers expect, especially those coming from JavaScript or Python where the tolerance for syntax variation is higher. The most frequent mistakes are:

Trailing commas — perhaps the most common culprit. In modern JavaScript and Python, trailing commas after the last item in an array or object are perfectly legal. In JSON, they are not. {"key": "value",} is invalid JSON; remove the comma after the last element.

Single quotes instead of double quotes — JSON requires double quotes for all strings (keys and values). Single-quoted strings like {'key': 'value'} are valid JavaScript object literals but will fail JSON.parse immediately.

Unquoted keys — again a JavaScript habit. {key: "value"} is not valid JSON; keys must always be quoted: {"key": "value"}.

Missing commas between elements — forgetting the comma separating array items or object properties is easy to miss visually but breaks parsing completely.

NaN, undefined, and Infinity — these JavaScript values have no representation in JSON. JSON.stringify(NaN) outputs null, and undefined values are silently dropped. If your data contains these, normalise them before serialising.

Deeply nested structures — technically valid but practically hazardous. Some parsers impose recursion depth limits (typically 512–1,024 levels), and deeply nested JSON is almost always a sign of a structural design problem that should be addressed at the data model level.

"JSON has become the universal data format for APIs — replacing XML in virtually every new web service since 2010."

JSON in API Development and ASEAN Tech

REST APIs universally use JSON for data exchange. From payment gateways to weather services, social platforms to government portals, the response body is almost always JSON. This dominance is not incidental — JSON's compactness (roughly 30% more compact than equivalent XML), readability, and native JavaScript integration made it the obvious choice as the web shifted from server-rendered pages to single-page applications calling APIs.

In Singapore, government APIs through data.gov.sg expose over 1,000 public datasets in JSON format — covering bus arrival times, hawker centre locations, HDB resale prices, and real-time environmental data. GovTech Singapore's APIs — used by developers building civic apps and government-integrated services — follow RESTful JSON conventions. Malaysia's open data initiatives and Indonesia's BPJS Kesehatan health insurance APIs similarly rely on JSON.

The ASEAN developer community — builders at Grab, Shopee, Lazada, Gojek, and thousands of startups across Singapore, Malaysia, Indonesia, the Philippines, and Vietnam — works with JSON every day. API SDKs, webhooks, mobile app backends, and microservice communication all route data as JSON. A fast, browser-based JSON formatter that requires no installation — and works offline once loaded — is a practical daily tool for any developer in the region.

JSON Web Tokens (JWT) — widely used for authentication in ASEAN fintech and SaaS products — embed Base64-encoded JSON payloads. Decoding and formatting that payload with a JSON formatter helps developers inspect claims, expiry times, and custom data without adding any external library to their workflow.

10 Facts About JSON

JSON was officially standardised as ECMA-404 in 2013 and as RFC 8259 in 2017 — despite being widely used since the early 2000s.

Douglas Crockford popularised JSON in 2001, though the format itself predates him — he reportedly "discovered" it rather than invented it.

A trailing comma after the last item in a JSON array or object is INVALID — even though modern JavaScript and Python allow it without complaint.

JSON supports only six data types: strings, numbers, objects, arrays, booleans, and null. Dates, undefined, and functions have no JSON representation.

The largest safely representable integer in JSON is 2⁵³ − 1 — the IEEE 754 double-precision limit. Numbers beyond this lose precision without a big-integer library.

JSON is approximately 30% more compact than equivalent XML — a key reason it displaced XML in REST API design across the entire industry.

Singapore's data.gov.sg open data portal provides over 1,000 datasets in JSON format — spanning public transport, environment, housing, and health data.

JSON Web Tokens (JWT) use Base64-encoded JSON in their payload — making JSON formatting tools useful for JWT debugging and inspection.

The fastest JSON parsers (simdjson) can process over 3 GB of JSON per second on modern hardware using SIMD CPU instructions — orders of magnitude faster than naive parsers.

JSON5 is an unofficial extension of JSON that allows comments, trailing commas, and single quotes — useful in config files (like .eslintrc) but not valid in API responses.

Frequently Asked Questions

Formatting (pretty-printing) adds indentation and newlines to JSON, making it easy for humans to read and navigate. Minifying does the opposite — it removes all whitespace to produce the most compact string possible, ideal for API responses and network transfer where byte count matters. Both produce logically identical data; only the presentation differs.
JSON does not allow a comma after the last element in an array or object. For example, {"name": "Alice",} is invalid JSON — remove the comma after "Alice". This is a common mistake for developers used to JavaScript or Python, where trailing commas are permitted. The error message in this tool will identify the approximate character position so you can find it quickly.
No — standard JSON does not support comments of any kind (no //, no /* */). Douglas Crockford intentionally excluded comments because he was concerned they would be used for directives that break interoperability. If you need comments in JSON-like config files, use JSON5 or JSONC (JSON with Comments) — formats used by editors like VS Code for settings files — but be aware these are not valid JSON and will fail strict parsers.
JSON is a text format derived from JavaScript object literal syntax, but it is stricter. In a JavaScript object literal, keys can be unquoted ({name: "Alice"}), strings can use single or double quotes, trailing commas are allowed, and values can be functions, undefined, or NaN. In JSON, all keys and string values must use double quotes, trailing commas are illegal, and only six value types are valid: string, number, object, array, boolean, and null.
JSON supports exactly six data types: string (must use double quotes), number (integer or floating-point, no quotes), object (key-value pairs in curly braces), array (ordered list in square brackets), boolean (true or false, lowercase), and null (lowercase). Dates, functions, undefined, NaN, Infinity, and binary data have no native JSON representation.
JSON numbers are stored as IEEE 754 double-precision floating-point. This means integers larger than 2⁵³ − 1 (9,007,199,254,740,991) cannot be represented exactly. This is a common problem with database ID fields — if your backend uses 64-bit integer IDs, they may lose precision when serialised to JSON and parsed by JavaScript. The standard workaround is to transmit large integers as strings and parse them with a BigInt library on the receiving side.
Yes — paste the raw JSON response body directly into the input textarea and click Format. API responses are almost always minified (single-line) JSON, and formatting them makes inspecting the structure, fields, and values much easier during development and debugging. This tool runs entirely in your browser — your data never leaves your device.
After formatting or minifying, click the Download button in the output toolbar. The tool creates a formatted.json file and triggers your browser's standard download — no server involved. The file is generated entirely in your browser using the Blob API, so it works offline and your data remains private.
100% free, forever. No account, no subscription, no hidden limits on input size. RECATOOLS is funded by contextual advertising, not paywalls. The JSON Formatter runs entirely in your browser — no server requests are made when you format or validate, so it is also faster and more private than server-side tools.
JSON and XML are both text-based formats for structured data, but they differ significantly in verbosity and readability. XML uses opening and closing tags for every element (<name>Alice</name>), which is verbose. JSON uses key-value pairs and square brackets ("name": "Alice"), which is more compact — typically 30% smaller for equivalent data. JSON also maps directly to data structures in most programming languages (objects, arrays, strings, numbers), while XML requires extra parsing to convert tags to usable types. Most new APIs built since 2010 use JSON; XML remains common in enterprise systems, SOAP APIs, and document-centric applications.

JSON Formatter & Validator