How to Format and Validate JSON Online Free — Plus the 6 Errors That Break Every Developer's API Integration
Three years ago I spent 90 minutes debugging a JSON payload that was being rejected by a payment gateway API. The error message said "invalid request body." The actual problem was a single trailing comma on line 47 of a 200-line JSON object. I couldn't see it because the JSON was minified into one unreadable line. The moment I pasted it into a formatter, the error was visible in 10 seconds. That's the entire value proposition of a JSON formatter — it turns invisible bugs into obvious ones.
This guide covers how to use UtilVox's JSON formatter, the specific errors that break Pakistani payment gateway and government API integrations, and the difference between formatting, validating, and minifying JSON so you use the right tool at the right time.
How to Format JSON on UtilVox
- Go to utilvox.com/tools/json-formatter
- Paste your JSON into the input field — minified or partially formatted
- See the result instantly — the formatter auto-formats as you paste
- Use the tree view to navigate deeply nested objects
- Copy the output — clean, indented, ready to use or share
Runs entirely in your browser. Your JSON never leaves your device — this matters when the payload contains API keys, user records, or internal configuration data.
What the Formatter Actually Does (and When to Use Each Mode)
Beautify / Pretty Print
Takes minified or inconsistently indented JSON and adds proper indentation and line breaks. The data is completely unchanged — only the visual presentation improves.
{"name":"UtilVox","tools":170,"free":true,"categories":["pdf","image","currency"]}
Becomes:
{
"name": "UtilVox",
"tools": 170,
"free": true,
"categories": [
"pdf",
"image",
"currency"
]
}
When to use: Debugging API responses, reading config files, understanding unfamiliar data structures, sharing JSON with a teammate.
Validate
Checks your JSON against the JSON specification and tells you exactly where the error is — line number, character position, what is wrong. Unlike just pasting into a code editor, a dedicated validator gives you a clear error message rather than a vague red underline.
When to use: Before sending a JSON payload to an API, before committing a config file, when an API keeps returning 400 Bad Request.
Minify
Removes all whitespace, line breaks, and indentation to produce the smallest possible JSON string.
When to use: API responses (smaller payload = faster transfer), storing JSON in a database field, embedding JSON in HTML or JavaScript.
The 6 JSON Errors That Show Up Constantly
After watching thousands of JSON strings run through the UtilVox formatter, these are the errors that break things most often:
Error 1: Trailing Comma
The most common. JSON does not allow a comma after the last item in an object or array. JavaScript allows it — JSON does not. If you copy a JS object literal into a JSON payload, this will bite you.
{
"name": "UtilVox",
"tools": 170, ← this comma has nothing after it — invalid
}
Fix: remove the comma after the last property.
Error 2: Single Quotes Instead of Double Quotes
JavaScript accepts single quotes. JSON requires double quotes — always, for both keys and string values. This trips up anyone who writes JS and pastes something into a JSON field.
{'name': 'UtilVox'} ← invalid JSON
{"name": "UtilVox"} ← valid JSON
Error 3: Unquoted Keys
JSON requires all keys to be strings in double quotes. JavaScript object literals allow unquoted keys. This is an extremely common mistake when someone copies a JS object and tries to use it as JSON.
{name: "UtilVox"} ← invalid JSON
{"name": "UtilVox"} ← valid JSON
Error 4: Missing Closing Bracket or Brace
A deeply nested JSON object with a missing } or ] somewhere will fail at parse time with "unexpected end of input." A formatter with tree view makes this visible immediately — you can see which object or array is never closed.
Error 5: Comments
JSON has no comment syntax. // and /* */ comments are valid JavaScript but will immediately break JSON parsing. Configuration files like .eslintrc and tsconfig.json look like JSON but actually use a JSON superset (JSONC) that allows comments. Pure JSON does not.
{
// this is a comment — INVALID in JSON
"name": "UtilVox"
}
Error 6: Using undefined or Functions
JSON supports six data types: string, number, boolean, null, array, and object. undefined, functions, and NaN are not valid JSON values. If you serialise a JavaScript object with undefined values, those keys are silently dropped — which can cause confusing bugs where data disappears.
JSON for Pakistani Developers — The Specific APIs That Cause Problems
JazzCash and EasyPaisa Integration
JazzCash and EasyPaisa APIs return JSON responses. When an integration fails, the first step is always to paste the response into a formatter and read the actual error object. Payment gateway error responses are often deeply nested — a formatter with tree view makes the error path obvious.
Common issue: JazzCash returns some responses where the nested responseCode is a string "000" not a number 0. Developers who check === 0 instead of === "000" miss successful transactions. The formatter shows you the data type of each value so you catch this before it hits production.
HBL, Meezan, and Local Bank APIs
Bank API documentation in Pakistan is inconsistent about whether they use camelCase or snake_case keys, and sometimes mixes both. The tree view in the formatter lets you see every key in the response at a glance, making it easy to map their response to your data model without missing anything.
FBR and NADRA Integration
Government API responses in Pakistan are often not well-documented. The only reliable way to understand what an endpoint returns is to call it, paste the response into a formatter, and read the actual structure. This is standard practice — the formatter is the documentation.
WhatsApp Business API
The WhatsApp Business API extensively uses JSON for message payloads. The interactive message types (buttons, lists, media) have strict JSON requirements. One malformed payload silently fails — the message is not delivered and WhatsApp returns a generic error. Always validate your payload in the formatter before sending.
JSON Data Types — What Is and Is Not Allowed
| Type | Example | Notes |
|---|---|---|
| String | "hello" | Double quotes only |
| Number | 42 or 3.14 | No quotes around numbers |
| Boolean | true or false | Lowercase only |
| Null | null | Lowercase only |
| Array | [1, 2, 3] | Any mix of types |
| Object | {"key": "value"} | Keys must be strings |
| ❌ undefined | — | Not valid JSON |
| ❌ NaN | — | Not valid JSON |
| ❌ Function | — | Not valid JSON |
| ❌ Comment | — | Not valid JSON |
| ❌ Date object | — | Store as ISO string instead |
Dates in JSON are stored as strings. The standard format is ISO 8601: "2024-05-18T10:30:00Z". Most APIs follow this convention, but some older APIs use Unix timestamps (a number) — check what the API expects.
JSON vs JavaScript Object Literal — Why They Are Not the Same
This confusion causes a significant portion of JSON errors. JSON looks like a JavaScript object, but the rules are stricter:
| Feature | JSON | JavaScript Object |
|---|---|---|
| Key quotes | Required (double quotes) | Optional |
| String quotes | Double quotes only | Single or double |
| Trailing commas | Not allowed | Allowed (ES5+) |
| Comments | Not allowed | Allowed |
| Functions as values | Not allowed | Allowed |
undefined as value | Not allowed | Allowed |
NaN as value | Not allowed | Allowed |
The practical implication: you cannot paste a JavaScript object literal directly into a JSON field without checking for trailing commas, single quotes, and unquoted keys. The UtilVox formatter validates against the JSON spec specifically — it will catch all of these.
When to Format vs Minify
Format when you are reading or debugging. Formatted JSON is for humans.
Minify when you are sending or storing. Minified JSON is for machines.
In practice: keep your source config files formatted and readable. Minify API payloads for production. Never send a 50KB formatted JSON response when a 12KB minified version carries the same data.
Frequently Asked Questions
Is my JSON data safe in the formatter?
Yes — UtilVox JSON Formatter runs entirely in your browser. Your data is never transmitted to any server. This is important when your JSON contains API credentials, user data, or internal system details.
Can it handle very large JSON files?
Yes — the formatter handles large files. Most JSON under 10MB formats instantly. Very large files (100MB+) may be slow depending on your device, but typical API responses and config files are well within limits.
What is the difference between JSON and JSONC?
JSONC (JSON with Comments) is used by some tools (VS Code settings, TypeScript config) and allows // and /* */ comments. Standard JSON parsers will reject JSONC. The UtilVox formatter validates against the strict JSON spec.
My JSON looks correct but the API still rejects it — why?
The API may have additional requirements beyond valid JSON syntax: a required field missing, a field in the wrong data type (string vs number), an enum value that does not match the allowed values. The formatter confirms the JSON is syntactically valid — but you also need to match the API's schema requirements.
What is JSONL?
JSONL (JSON Lines) is a format where each line is a separate valid JSON object, typically used in logging, data exports, and ML training datasets. It is not a single JSON document — each line is its own independent object.
Related Developer Tools on UtilVox
- JWT Decoder — Decode and inspect JSON Web Tokens (the header and payload are JSON)
- Base64 Encoder — Many APIs send JSON payloads as Base64 encoded strings
- Regex Tester — Validate JSON field values with regex patterns
- URL Encoder — Encode JSON strings for safe inclusion in URLs
- MD5 Generator — Generate hashes for JSON payload verification
Format Your JSON Now
Validate, beautify, and debug your JSON instantly — free, private, runs in your browser.
👉 Open JSON Formatter
Related Free Tools on UtilVox
- JSON Formatter — Format, validate and beautify JSON online
- CSV to JSON — Convert CSV data to JSON format
- JSON to CSV — Convert JSON back to CSV
- XML Formatter — Format and validate XML documents