How to fix “JSON.parse” errors (and avoid them next time)

Why JSON.parse fails

JSON.parse accepts only strict JSON. That means double quotes for strings, no trailing commas, and no comments. Many “JSON-like” formats (JavaScript objects, config snippets, logs) look similar but aren’t valid JSON, so they fail immediately when parsed.

Use the error position to pinpoint the break

The fastest workflow is to validate first, then fix the exact character that breaks parsing. Most modern browsers include the byte position in the error message. A validator can translate that into a line/column hint, which is much faster than guessing.

Most common causes (real-world)

Here are the top causes:

• Single quotes: {'a': 1} is JavaScript, not JSON. Use {"a": 1}.
• Trailing commas: {"a": 1,} is invalid. Remove the last comma.
• Unquoted keys: {a: 1} is invalid. Keys must be in double quotes.
• Comments: // comment or /* ... */ are not allowed.
• Copying from logs: extra characters before/after JSON (timestamps, prefixes) will break parsing.

If the input is supposed to be an array of objects (common for conversions), verify the top-level shape. For example, JSON → CSV expects something like [{"col":"value"}], not a single object {"col":"value"}. Similarly, converters often assume consistent rows/columns.

If you need a safe way to debug sensitive payloads, use a no-upload validator. It runs entirely in your browser — you can validate and fix issues without sending data to a server.

FAQ

Can I validate “confidential JSON” safely? Yes—use a validator that runs locally in your browser. Your payload stays on-device.

Why does JSON.parse complain about a token that “looks normal”? Often the text is not JSON at all (it’s a JavaScript object literal or a log line). Validate syntax first.

const text = input.trim();
const value = JSON.parse(text);
console.log(Array.isArray(value) ? 'array' : typeof value);