JSON Parser Error Messages Explained

Most JSON parser errors boil down to a short list of problems: broken punctuation, broken strings, broken numbers, extra content after a valid JSON value, or content that was never JSON in the first place. The hard part is that different runtimes phrase those failures differently.

This guide translates the message you see into the fastest likely fix, with examples from JavaScript and Python and a few current parser notes from MDN's JSON.parse error reference, the Python json docs, and RFC 8259.

Quick Lookup

If you landed here with a specific error message, start with the category below and then jump to the matching section.

How to Read the Location Info

The reported location is your best clue. In JavaScript you often get a character position. In Python,JSONDecodeError exposes the message plus pos,lineno, and colno. The parser usually detects the problem when it reaches the next impossible character, so the real mistake is often one character before the reported position.

Common JSON Error Families

Exact wording changes across engines. The category is what matters: once you know whether the failure is about object syntax, separators, strings, extra data, incomplete input, or numbers, the fix gets much faster.

{
  'name': "Alice",
  age: 30,
}

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

[
  1
  2,
  3,
]

[
  1,
  2,
  3
]

{
  "message": "Line 1
Line 2"
}

{
  "message": "Line 1\nLine 2"
}

{"a": 1}{"b": 2}

[
  { "a": 1 },
  { "b": 2 }
]

{
  "user": {
    "id": 1,
    "name": "Ana"
  }

{
  "user": {
    "id": 1,
    "name": "Ana"
  }
}

{
  "count": 01,
  "ratio": 1.,
  "value": NaN
}

{
  "count": 1,
  "ratio": 1.0,
  "value": null
}

When the Payload Is Not Actually JSON

Many real-world parse failures are upstream response problems, not syntax mistakes inside a valid JSON document.

• If the first character is <, you probably got an HTML error page, login page, or CDN/proxy response instead of JSON.
• If the body is empty, the parse failure may be correct: an empty string is not JSON.
• MDN notes that Response.json() throws SyntaxError when the body cannot be parsed as JSON, but it can also throw TypeError when body decoding fails, for example because Content-Encoding is wrong.
• If the payload came from a human-edited config file, confirm whether it is strict JSON or a looser format such as JSONC or JSON5.

const response = await fetch(url);
const text = await response.text();

console.log(response.status, response.headers.get("content-type"));
console.log(text.slice(0, 200));

const data = JSON.parse(text);

Compatibility Notes That Matter

• Message text is not standardized. The same invalid input can produce different wording in Firefox, Chrome, Node.js, Python, and backend libraries.
• JSON itself is standardized. RFC 8259 allows one JSON value at the top level, not just objects or arrays.
• Python's standard library documents some intentionally non-strict behavior, such as acceptingNaN and Infinity unless you override the decoder. That can hide invalid JSON that a stricter parser will reject later.
• A byte order mark at the start of a payload can also create interoperability problems. RFC 8259 says it must not be added to transmitted JSON, and parser behavior varies when it appears anyway.

Preventing Parse Errors

The fastest fix is usually upstream: generate valid JSON automatically and verify the raw payload before it reaches your parser.

• Serialize native data structures with JSON.stringify, json.dumps, or equivalent instead of hand-building strings.
• Log the raw payload in development before parsing, but redact secrets and tokens.
• Validate Content-Type and HTTP status before assuming a response body is JSON.
• Use a JSON-aware formatter or validator to pinpoint the first syntax break quickly.
• Use the right parser for the format you actually have: JSON, NDJSON/JSONL, JSON5, or JSONC are not interchangeable.

If you treat the error message as a category plus a location hint, most JSON failures become routine to fix. Start with the character position, inspect the raw payload, and verify that the content is strict JSON rather than a nearby format or an upstream error page.