Understand what JSON parser errors mean, find the exact syntax problem, and fix malformed JSON in APIs, files, applications, and development workflows.

Format & Check JSON Fix Invalid JSON

What causes a JSON parse error?

A JSON parse error occurs when a parser receives text that does not conform to valid JSON syntax. Common causes include missing commas, single quotes instead of double quotes, trailing commas, unquoted property names, unmatched braces or brackets, invalid escape sequences, comments, incomplete JSON, or an API returning HTML or another non-JSON response. The fix is to identify the parser's reported location, inspect the surrounding characters, correct the invalid syntax or unexpected response, and parse the JSON again.

Quick Fix Steps

Check the parser error message and reported position.
Inspect the JSON around the reported character.
Look for missing commas, quotes, colons, braces, or brackets.
Check for single quotes, trailing commas, comments, and invalid values.
If the data came from an API, inspect the HTTP status, Content-Type, and raw response body.
Validate the corrected JSON before using it in the application.

JSON Parse Errors: How to Understand and Fix JSON Parsing Problems

A JSON parse error means the parser couldn't turn the supplied text into a valid JSON value. The message can look vague at first, especially when the reported character is far from the mistake that caused the parser to fail. In practice, most parsing failures come from a small set of syntax problems or from an application receiving something that isn't JSON at all. This guide explains how to read those errors, find the underlying problem, and troubleshoot JSON from files, APIs, request bodies, webhooks, and application code.

What Is a JSON Parse Error?

A JSON parse error happens when software attempts to parse JSON text but the input doesn't follow JSON syntax. Parsing is the step that converts a textual JSON representation into an in-memory value such as an object, array, string, number, boolean, or null. If the parser encounters something it cannot legally interpret, it stops and reports an error.

Parsing vs Formatting vs Validation

These operations solve different problems. Parsing attempts to read JSON syntax. Formatting changes whitespace and presentation. Validation can check JSON syntax and, separately, whether the resulting data satisfies a schema or application contract. A formatter may also parse the input as part of its operation, but formatting itself does not repair arbitrary malformed JSON.

operation	purpose	example
Parsing	Convert JSON text into a data structure	`JSON.parse(text)`
Formatting	Make valid JSON easier to read	`JSON.stringify(data, null, 2)`
Validation	Check syntax or data against defined rules	`JSON Schema validation`
Repair	Correct malformed JSON	`Fixing a missing comma or quote`

The Most Common JSON Parse Error Causes

Most parser failures can be traced to a small number of syntax mistakes. When debugging manually, check these before looking for more unusual causes.

Missing comma

Example:

{
  "name": "Ramesh"
  "role": "developer"
}

Add a comma after the name property.

Single quotes

Example:

{'name': 'Ramesh'}

JSON strings and property names use double quotes.

Trailing comma

Example:

{
  "name": "Ramesh",
}

Remove the comma before the closing brace.

Unquoted property name

Example:

{name: "Ramesh"}

Write the property name as "name".

Missing colon

Example:

{
  "name", "Ramesh"
}

Separate the property name and value with a colon.

Unmatched braces or brackets

Example:

{
  "user": {
    "name": "Ramesh"
  }

Make sure every object and array is properly closed.

Invalid value

Example:

{
  "active": True
}

JSON uses true, false, and null in lowercase.

Invalid escape

Example:

{
  "path": "C:\temp"
}

Use valid JSON escape sequences and escape literal backslashes when required.

Unexpected Token Errors

Messages such as "Unexpected token" usually mean the parser encountered a character or value that is not valid at that point in the JSON document. The reported token is often useful, but it isn't always the original mistake. A missing comma earlier in the document can cause the parser to complain when it reaches the next property.

Typical unexpected token situationjavascript

const text = '{"name":"Ramesh" "role":"developer"}';
JSON.parse(text);

Unexpected End of JSON Input

An "Unexpected end of JSON input" error generally means the parser reached the end of the input before completing a valid JSON value. Typical causes include truncated JSON, a missing closing brace or bracket, an incomplete string, or an empty response being passed to JSON.parse().

Incomplete JSONjavascript

const text = '{"user":{"name":"Ramesh"}';
JSON.parse(text);

Empty inputjavascript

JSON.parse('');

Unexpected Character Errors

An unexpected-character error means the parser encountered a character that doesn't fit the JSON grammar at that position. Check the nearby text for single quotes, comments, unquoted values, HTML, control characters, or accidental characters copied into the JSON.

JSON Parse Error Caused by Single Quotes

JSON requires double quotes around property names and string values. JavaScript object literals can use single quotes for strings, but that does not make the resulting text valid JSON.

Invalid JSONjson

{'name': 'Ramesh'}

Valid JSONjson

{"name": "Ramesh"}

JSON Parse Error Caused by Trailing Commas

Standard JSON does not allow a comma after the final member of an object or the final element of an array. Some programming languages and configuration formats allow trailing commas, which can create confusion when that syntax is passed to a strict JSON parser.

Invalid trailing commajson

{
  "name": "Ramesh",
}

Valid JSONjson

{
  "name": "Ramesh"
}

JSON Parse Error Caused by Comments

Standard JSON does not support JavaScript-style comments. An input containing // or /* ... */ comments can therefore fail when passed to a strict JSON parser. Some JSON-like configuration formats support comments, but those formats should not be assumed to be interchangeable with standard JSON.

Not standard JSONtext

{
  // user information
  "name": "Ramesh"
}

JSON Parse Errors from Invalid Escape Sequences

Backslashes have special meaning inside JSON strings. JSON supports specific escape sequences such as quotation marks, reverse solidus, slash, backspace, form feed, newline, carriage return, tab, and Unicode escapes. An unsupported escape sequence can cause parsing to fail.

Escaped backslashjson

{
  "path": "C:\\Users\\Ramesh"
}

JSON Parse Errors from Invalid Values

JSON has a limited set of literal values. Boolean values are true and false, and the null value is written as null. Values such as True, False, None, undefined, NaN, and Infinity are not standard JSON literals.

Valid JSON valuesjson

{
  "active": true,
  "deleted": false,
  "metadata": null
}

JSON Parse Errors from Unquoted Strings

A bare word cannot be used as a JSON string. String values must be enclosed in double quotes. This is another common difference between JSON and programming-language object literals.

Invalidtext

{
  "name": Ramesh
}

Validjson

{
  "name": "Ramesh"
}

JSON Parse Errors from Unmatched Braces and Brackets

Every object opened with { must be closed with }, and every array opened with [ must be closed with ]. Deeply nested JSON makes missing or incorrectly placed closing characters harder to spot manually, which is why formatting valid JSON is useful during inspection.

Correctly nested JSONjson

{
  "user": {
    "roles": [
      "developer",
      "admin"
    ]
  }
}

How to Find the Exact JSON Parsing Problem

Start with the parser's line, column, character position, or byte offset if one is provided. Then inspect several characters before and after that location. The reported position is where the parser recognized a problem, not necessarily where the mistake was introduced. For example, a missing comma can cause an error at the beginning of the next property.

Read the complete error message.
Record the line, column, position, or byte offset.
Inspect the surrounding JSON.
Check the previous property or array element.
Look for missing punctuation and incorrect quotes.
Check whether the entire input is actually JSON.
Validate the corrected input again.

How to Fix a JSON Parse Error

The safest repair process is to identify the syntax violation instead of randomly changing characters until the parser accepts the input. Once the invalid token or missing structure is identified, make the smallest necessary correction and parse the document again.

Keep a copy of the original input.
Read the parser error and location.
Inspect the surrounding structure.
Correct the specific syntax problem.
Run the parser again.
Format the valid JSON to make the hierarchy easier to inspect.
Validate the final structure against the application's expected schema when applicable.

JSON.parse Errors in JavaScript

JavaScript uses JSON.parse() to convert a JSON string into a JavaScript value. If the string is not valid JSON, JSON.parse() throws a SyntaxError rather than returning a partially parsed result.

Handle a JSON.parse errorjavascript

try {
  const data = JSON.parse(jsonText);
  console.log(data);
} catch (error) {
  console.error('Invalid JSON:', error.message);
}

JSON Parse Errors in Node.js

Node.js applications commonly parse JSON from files, HTTP responses, environment-derived configuration, queues, and request bodies. When parsing fails, log enough context to identify the source without exposing credentials, tokens, or private payload data.

Safe parsing patternjavascript

function parseJson(text) {
  try {
    return JSON.parse(text);
  } catch (error) {
    throw new Error(`Invalid JSON: ${error.message}`);
  }
}

JSON Parsing Errors in Python

Python's json.loads() parses a JSON string, while json.load() reads JSON from a file-like object. Invalid input raises a JSON decoding exception that includes useful information about where decoding failed.

Handle JSON decoding errorspython

import json

try:
    data = json.loads(json_text)
except json.JSONDecodeError as error:
    print(f"Invalid JSON at line {error.lineno}, column {error.colno}")

JSON Parse Errors in API Responses

An API parsing error does not necessarily mean the API returned malformed JSON. The endpoint may have returned HTML, plain text, an authentication page, a proxy error, an empty body, or another format instead. Check the HTTP status, Content-Type, and raw response body before assuming the JSON itself is broken.

When an API Returns HTML Instead of JSON

A particularly common failure occurs when code expects JSON but receives an HTML error page. For example, a missing route, reverse proxy failure, authentication redirect, or server error may produce HTML. The JSON parser then reports an error near the first character because < is not the beginning of a JSON value.

Unexpected non-JSON responsetext

<!doctype html>
<html>
  <body>
    Error
  </body>
</html>

Check Content-Type Before Parsing an API Response

For HTTP responses, inspect the Content-Type header along with the status code and response body. An endpoint intended to return JSON will commonly use an application/json media type, although the exact media type can vary by API. The header is useful evidence, but the body still needs to be handled according to the API's actual contract.

Empty API Responses and JSON Parsing

An empty response body is not the same thing as the JSON value null. Passing an empty string to a JSON parser generally fails because there is no JSON value to parse. API clients should account for endpoints that legitimately return no content and should follow the API's documented response behavior.

JSON Parsing vs API Contract Errors

A successful parse only establishes that the text is syntactically valid JSON. The resulting object can still be missing required properties, contain the wrong data types, or use values that the API does not accept. Those are schema or application-level validation problems rather than JSON parsing errors.

JSON Parse Errors in Webhooks

Webhook handlers often parse a request body as JSON after receiving an HTTP request. If the provider's body is malformed, truncated, encoded incorrectly, or handled incorrectly by middleware, parsing can fail. When webhook signatures are involved, preserve the original raw body because verification may depend on the exact bytes received.

/guides/format-webhook-json

JSON File Parsing Errors

Configuration files, fixtures, exports, and datasets can fail during parsing because of an accidental comma, missing closing bracket, comment, merge conflict marker, or incomplete edit. Open the file in a JSON-aware editor or validate it from the command line to locate the syntax problem before changing application code.

JSON Parse Errors Caused by Git Merge Conflicts

Unresolved Git conflict markers such as <<<<<<<, =======, and >>>>>>> are not valid JSON. If a JSON file was merged manually, search for conflict markers before investigating less obvious parser failures.

Git conflict markertext

<<<<<<< HEAD
{
  "name": "Ramesh"
}
=======
{
  "name": "Alex"
}
>>>>>>> feature

JSON Parse Errors from Truncated Data

If JSON is cut off during a network transfer, file operation, queue message, logging process, or string manipulation step, the parser may reach the end while an object, array, or string is still open. Compare the raw input with the expected payload and investigate where truncation occurred rather than adding arbitrary closing characters.

JSON Parse Errors from Encoding or Control Characters

Unexpected control characters or incorrectly handled encoded data can cause parsing failures. JSON strings have specific escaping rules, so binary data or raw control characters should not be inserted directly into JSON text. When the source is external, inspect the actual bytes or decoded representation if the visible text looks correct but parsing still fails.

JSON Parsing of Nested JSON Strings

Some APIs and databases contain JSON encoded as a string inside another JSON document. This can require more than one parsing step. First parse the outer JSON, then parse the nested string if the application's contract says that the string itself contains JSON.

Nested JSON stringjavascript

const outer = JSON.parse(text);
const inner = JSON.parse(outer.payload);

How Formatting Helps Debug JSON Parse Errors

A formatter is most useful after the JSON is syntactically valid, because valid formatting can expose nesting and make the structure easier to inspect. If the input cannot be parsed, use the parser error, validator, or syntax-aware editor to locate and correct the malformed portion first.

A Practical JSON Parsing Debugging Workflow

When a production or development application reports a JSON parsing failure, work backward from the exact input rather than guessing from the error message alone.

Capture the source of the JSON.
Preserve the raw input when appropriate.
Check whether the input is actually JSON.
Inspect the HTTP status and Content-Type for network responses.
Read the parser's line, column, or character position.
Inspect the surrounding characters.
Check commas, quotes, colons, braces, brackets, escapes, and values.
Look for HTML, plain text, redirects, empty bodies, or proxy errors.
Correct the source of the malformed data.
Parse the corrected input again.
Format the valid JSON for easier inspection.
Apply schema or application-level validation after parsing.

How to Prevent JSON Parse Errors

Prevention is usually easier when JSON generation and parsing are handled by established serializers rather than manually constructing JSON strings. Validate external input, test API contracts, handle unexpected response types, and keep useful but privacy-safe diagnostics around parsing failures.

Use native JSON serializers instead of manually concatenating JSON strings.
Validate external JSON before using it.
Test API responses for success and error conditions.
Check response status and Content-Type before assuming a body is JSON.
Handle empty responses explicitly.
Keep JSON examples and fixtures valid in source control.
Run automated validation in CI for important JSON files.
Avoid logging secrets and personal information when debugging payloads.
Preserve raw webhook bodies when signature verification requires them.
Separate JSON syntax validation from application schema validation.

JSON Parse Error vs JSON Syntax Error

The terms are closely related. A syntax error describes invalid JSON grammar, while a parse error describes the parser failing to interpret the supplied text. In many programming environments, the error message may use one term or the other for essentially the same underlying problem.

JSON Parse Error vs JSON Validation Error

A parsing error happens before the application has a usable JSON value. A validation error generally occurs after parsing, when the data is checked against a schema, type requirement, business rule, or API contract. Keeping these stages separate makes debugging much easier.

When to Use a JSON Formatter

Use a JSON formatter when the JSON is valid but difficult to read, or when you want to inspect its hierarchy after parsing. For malformed input, use a validator or syntax-aware repair workflow first. A formatter is particularly useful for inspecting API responses, configuration files, request payloads, and nested objects.

/json-formatter

JSON Formatting Examples

Catch JSON.parse errors

javascript

try {
  const data = JSON.parse(jsonText);
  console.log(data);
} catch (error) {
  console.error('JSON parsing failed:', error.message);
}

Format parsed JSON

javascript

const formatted = JSON.stringify(JSON.parse(jsonText), null, 2);

Parse JSON in Python

python

import json

try:
    data = json.loads(json_text)
except json.JSONDecodeError as error:
    print(f"Invalid JSON at line {error.lineno}, column {error.colno}")

Validate JSON from the command line

bash

jq empty input.json

Format JSON with jq

bash

jq . input.json

Parse a nested JSON string

javascript

const outer = JSON.parse(text);
const inner = JSON.parse(outer.payload);

JSON Parse Error Debugging Checklist

Read the complete parser error message.
Check the reported line, column, position, or byte offset.
Inspect the characters immediately before and after the reported location.
Look for missing commas.
Check for single quotes instead of double quotes.
Remove trailing commas.
Check object braces and array brackets.
Check colons between property names and values.
Look for unquoted string values.
Check true, false, and null casing.
Inspect backslashes and escape sequences.
Check for comments and Git conflict markers.
Determine whether the input is actually JSON.
For APIs, inspect status, Content-Type, and the raw response.
Handle empty responses explicitly.
Check for truncated or partially received JSON.
Parse the corrected input again.
Format valid JSON for easier inspection.
Run schema validation after successful parsing when required.
Never log secrets or sensitive payload data while debugging.

Frequently Asked Questions

Q:What is a JSON parse error?

A JSON parse error occurs when a parser cannot interpret supplied text as valid JSON. The input may contain invalid syntax or may not actually be JSON.

Q:What causes JSON parse errors?

Common causes include missing commas, invalid quotes, trailing commas, unquoted strings, invalid escape sequences, unmatched braces or brackets, comments, invalid values, incomplete input, and non-JSON responses.

Q:How do I fix a JSON parse error?

Read the parser's reported position, inspect the surrounding text, identify the syntax problem, make the smallest necessary correction, and parse the input again. If the input came from an API, first verify that the response is actually JSON.

Q:What does Unexpected token mean in JSON?

It usually means the parser encountered a character or value that isn't valid at that location. The actual mistake can occur slightly earlier, such as a missing comma.

Q:What does Unexpected end of JSON input mean?

It generally means the parser reached the end before completing a valid JSON value. Common causes are incomplete JSON, missing closing brackets, an unfinished string, or an empty input.

Q:Why does JSON.parse fail?

JSON.parse fails when its argument is not valid JSON text. Single quotes, trailing commas, comments, invalid values, missing punctuation, incomplete data, and HTML responses are common causes.

Q:Why am I getting a JSON parse error from an API?

The API may have returned malformed JSON, HTML, plain text, an authentication response, an error page, or an empty body. Check the HTTP status, Content-Type, and raw response before assuming the JSON syntax is wrong.

Q:Why does JSON.parse say Unexpected token <?

A common cause is an HTML response being passed to JSON.parse(). HTML often begins with <, so the parser reports that character as unexpected. Check the endpoint, status code, Content-Type, and raw response body.

Q:Can a missing comma cause a JSON parse error?

Yes. A missing comma between object properties or array elements commonly causes the parser to fail when it reaches the next token.

Q:Can single quotes cause a JSON parse error?

Yes. Standard JSON uses double quotes for property names and string values. Single-quoted JavaScript object literals are not valid JSON.

Q:Can trailing commas cause a JSON parse error?

Yes. Standard JSON does not permit a trailing comma after the final object property or array element.

Q:Can comments cause a JSON parse error?

Yes. Standard JSON does not support // or /* ... */ comments. A parser that expects standard JSON can reject documents containing them.

Q:Can an empty response cause a JSON parse error?

Yes. An empty string contains no JSON value, so attempting to parse it normally fails. An API client should handle documented no-content responses separately.

Q:Can formatting fix a JSON parse error?

Not by itself. Formatting generally requires valid JSON before it can produce formatted output. Syntax errors must be identified and corrected separately.

Q:Is a JSON parse error the same as a JSON syntax error?

They are closely related. A JSON syntax error means the text violates JSON grammar, while a parse error describes the parser failing to interpret the text. Different tools may use different terminology.

Q:What is the difference between parsing and validation?

Parsing converts JSON text into a data structure. Validation checks whether the JSON syntax is valid and, at a different level, whether the resulting data satisfies schema or application rules.

Q:Why is valid JSON still rejected by my API?

Valid JSON only means the text follows JSON syntax. An API can still reject it because required fields are missing, values have incorrect types, fields are not allowed, or business rules are violated.

Q:How do I find the exact character causing a JSON parse error?

Use the line, column, character position, or byte offset reported by the parser and inspect the surrounding text. Also inspect the token immediately before the reported location because the actual mistake can occur earlier.

Q:How do I handle JSON parsing errors in JavaScript?

Wrap JSON.parse() in try/catch, record safe diagnostic information, and handle invalid input without exposing sensitive payload contents.

Q:How do I handle JSON parsing errors in Python?

Catch json.JSONDecodeError when using json.loads() or json.load(), then use its line and column information to locate the malformed input.

Q:How do I check whether an API response is JSON?

Inspect the HTTP status, Content-Type header, and raw response body. Do not assume every successful or error response contains JSON.

Q:What should I do if JSON parsing fails on a webhook?

Preserve the original request body, inspect the raw payload and request headers, check how middleware handled the body, and parse the payload according to the webhook provider's documented format. If signatures are used, verify against the required raw body before transforming it.

Q:Can Git merge conflicts cause JSON parse errors?

Yes. Unresolved conflict markers such as <<<<<<<, =======, and >>>>>>> are not valid JSON and can cause parsing to fail.

Q:Can JSON be parsed if it contains comments?

Not as standard JSON. Some JSON-like configuration formats allow comments, but a strict standard JSON parser may reject them.

Q:Can JSON.parse parse a JavaScript object directly?

No. JSON.parse() expects a JSON string. If you already have a JavaScript object, you can use it directly or serialize it with JSON.stringify() when you need JSON text.

Q:Why does parsing fail even though the JSON looks correct?

The visible content may hide an unexpected character, invalid escape, encoding issue, truncated response, or non-JSON content. Inspect the raw input and parser location rather than relying only on visual inspection.

Explore More Resources

JSON Formatter

Fix Invalid JSON

How to Format JSON

JSON Pretty Print

JSON Indentation

JSON Beautifier

How to Validate JSON

JSON Validation

JSON Schema

Debug JSON API Response

Format JSON API Response

Read more about Format JSON API Response

Format REST API Response

Read more about Format REST API Response

Format JSON Payload

Format Webhook JSON

JSON Formatting vs Minification

Read more about JSON Formatting vs Minification

JSON Minifier

JSON Parse Errors

Understand what JSON parser errors mean, find the exact syntax problem, and fix malformed JSON in APIs, files, applications, and development workflows.

Format & Check JSON Fix Invalid JSON

What causes a JSON parse error?

Quick Fix Steps

Check the parser error message and reported position.
Inspect the JSON around the reported character.
Look for missing commas, quotes, colons, braces, or brackets.
Check for single quotes, trailing commas, comments, and invalid values.
If the data came from an API, inspect the HTTP status, Content-Type, and raw response body.
Validate the corrected JSON before using it in the application.

JSON Parse Errors: How to Understand and Fix JSON Parsing Problems

What Is a JSON Parse Error?

Parsing vs Formatting vs Validation

operation	purpose	example
Parsing	Convert JSON text into a data structure	`JSON.parse(text)`
Formatting	Make valid JSON easier to read	`JSON.stringify(data, null, 2)`
Validation	Check syntax or data against defined rules	`JSON Schema validation`
Repair	Correct malformed JSON	`Fixing a missing comma or quote`

The Most Common JSON Parse Error Causes

Most parser failures can be traced to a small number of syntax mistakes. When debugging manually, check these before looking for more unusual causes.

Missing comma

Example:

{
  "name": "Ramesh"
  "role": "developer"
}

Add a comma after the name property.

Single quotes

Example:

{'name': 'Ramesh'}

JSON strings and property names use double quotes.

Trailing comma

Example:

{
  "name": "Ramesh",
}

Remove the comma before the closing brace.

Unquoted property name

Example:

{name: "Ramesh"}

Write the property name as "name".

Missing colon

Example:

{
  "name", "Ramesh"
}

Separate the property name and value with a colon.

Unmatched braces or brackets

Example:

{
  "user": {
    "name": "Ramesh"
  }

Make sure every object and array is properly closed.

Invalid value

Example:

{
  "active": True
}

JSON uses true, false, and null in lowercase.

Invalid escape

Example:

{
  "path": "C:\temp"
}

Use valid JSON escape sequences and escape literal backslashes when required.

Unexpected Token Errors

Typical unexpected token situationjavascript

const text = '{"name":"Ramesh" "role":"developer"}';
JSON.parse(text);

Unexpected End of JSON Input

Incomplete JSONjavascript

const text = '{"user":{"name":"Ramesh"}';
JSON.parse(text);

Empty inputjavascript

JSON.parse('');

Unexpected Character Errors

JSON Parse Error Caused by Single Quotes

JSON requires double quotes around property names and string values. JavaScript object literals can use single quotes for strings, but that does not make the resulting text valid JSON.

Invalid JSONjson

{'name': 'Ramesh'}

Valid JSONjson

{"name": "Ramesh"}

JSON Parse Error Caused by Trailing Commas

Invalid trailing commajson

{
  "name": "Ramesh",
}

Valid JSONjson

{
  "name": "Ramesh"
}

JSON Parse Error Caused by Comments

Not standard JSONtext

{
  // user information
  "name": "Ramesh"
}

JSON Parse Errors from Invalid Escape Sequences

Escaped backslashjson

{
  "path": "C:\\Users\\Ramesh"
}

JSON Parse Errors from Invalid Values

Valid JSON valuesjson

{
  "active": true,
  "deleted": false,
  "metadata": null
}

JSON Parse Errors from Unquoted Strings

A bare word cannot be used as a JSON string. String values must be enclosed in double quotes. This is another common difference between JSON and programming-language object literals.

Invalidtext

{
  "name": Ramesh
}

Validjson

{
  "name": "Ramesh"
}

JSON Parse Errors from Unmatched Braces and Brackets

Correctly nested JSONjson

{
  "user": {
    "roles": [
      "developer",
      "admin"
    ]
  }
}

How to Find the Exact JSON Parsing Problem

Read the complete error message.
Record the line, column, position, or byte offset.
Inspect the surrounding JSON.
Check the previous property or array element.
Look for missing punctuation and incorrect quotes.
Check whether the entire input is actually JSON.
Validate the corrected input again.

How to Fix a JSON Parse Error

Keep a copy of the original input.
Read the parser error and location.
Inspect the surrounding structure.
Correct the specific syntax problem.
Run the parser again.
Format the valid JSON to make the hierarchy easier to inspect.
Validate the final structure against the application's expected schema when applicable.

JSON.parse Errors in JavaScript

JavaScript uses JSON.parse() to convert a JSON string into a JavaScript value. If the string is not valid JSON, JSON.parse() throws a SyntaxError rather than returning a partially parsed result.

Handle a JSON.parse errorjavascript

try {
  const data = JSON.parse(jsonText);
  console.log(data);
} catch (error) {
  console.error('Invalid JSON:', error.message);
}

JSON Parse Errors in Node.js

Safe parsing patternjavascript

function parseJson(text) {
  try {
    return JSON.parse(text);
  } catch (error) {
    throw new Error(`Invalid JSON: ${error.message}`);
  }
}

JSON Parsing Errors in Python

Handle JSON decoding errorspython

import json

try:
    data = json.loads(json_text)
except json.JSONDecodeError as error:
    print(f"Invalid JSON at line {error.lineno}, column {error.colno}")

JSON Parse Errors in API Responses

When an API Returns HTML Instead of JSON

Unexpected non-JSON responsetext

<!doctype html>
<html>
  <body>
    Error
  </body>
</html>

Check Content-Type Before Parsing an API Response

Empty API Responses and JSON Parsing

JSON Parsing vs API Contract Errors

JSON Parse Errors in Webhooks

/guides/format-webhook-json

JSON File Parsing Errors

JSON Parse Errors Caused by Git Merge Conflicts

Git conflict markertext

<<<<<<< HEAD
{
  "name": "Ramesh"
}
=======
{
  "name": "Alex"
}
>>>>>>> feature

JSON Parse Errors from Truncated Data

JSON Parse Errors from Encoding or Control Characters

JSON Parsing of Nested JSON Strings

Nested JSON stringjavascript

const outer = JSON.parse(text);
const inner = JSON.parse(outer.payload);

How Formatting Helps Debug JSON Parse Errors

A Practical JSON Parsing Debugging Workflow

When a production or development application reports a JSON parsing failure, work backward from the exact input rather than guessing from the error message alone.

Capture the source of the JSON.
Preserve the raw input when appropriate.
Check whether the input is actually JSON.
Inspect the HTTP status and Content-Type for network responses.
Read the parser's line, column, or character position.
Inspect the surrounding characters.
Check commas, quotes, colons, braces, brackets, escapes, and values.
Look for HTML, plain text, redirects, empty bodies, or proxy errors.
Correct the source of the malformed data.
Parse the corrected input again.
Format the valid JSON for easier inspection.
Apply schema or application-level validation after parsing.

How to Prevent JSON Parse Errors

Use native JSON serializers instead of manually concatenating JSON strings.
Validate external JSON before using it.
Test API responses for success and error conditions.
Check response status and Content-Type before assuming a body is JSON.
Handle empty responses explicitly.
Keep JSON examples and fixtures valid in source control.
Run automated validation in CI for important JSON files.
Avoid logging secrets and personal information when debugging payloads.
Preserve raw webhook bodies when signature verification requires them.
Separate JSON syntax validation from application schema validation.

JSON Parse Error vs JSON Syntax Error

JSON Parse Error vs JSON Validation Error

When to Use a JSON Formatter

/json-formatter

JSON Formatting Examples

Catch JSON.parse errors

javascript

try {
  const data = JSON.parse(jsonText);
  console.log(data);
} catch (error) {
  console.error('JSON parsing failed:', error.message);
}

Format parsed JSON

javascript

const formatted = JSON.stringify(JSON.parse(jsonText), null, 2);

Parse JSON in Python

python

import json

try:
    data = json.loads(json_text)
except json.JSONDecodeError as error:
    print(f"Invalid JSON at line {error.lineno}, column {error.colno}")

Validate JSON from the command line

bash

jq empty input.json

Format JSON with jq

bash

jq . input.json

Parse a nested JSON string

javascript

const outer = JSON.parse(text);
const inner = JSON.parse(outer.payload);

JSON Parse Error Debugging Checklist

Read the complete parser error message.
Check the reported line, column, position, or byte offset.
Inspect the characters immediately before and after the reported location.
Look for missing commas.
Check for single quotes instead of double quotes.
Remove trailing commas.
Check object braces and array brackets.
Check colons between property names and values.
Look for unquoted string values.
Check true, false, and null casing.
Inspect backslashes and escape sequences.
Check for comments and Git conflict markers.
Determine whether the input is actually JSON.
For APIs, inspect status, Content-Type, and the raw response.
Handle empty responses explicitly.
Check for truncated or partially received JSON.
Parse the corrected input again.
Format valid JSON for easier inspection.
Run schema validation after successful parsing when required.
Never log secrets or sensitive payload data while debugging.

Frequently Asked Questions

Q:What is a JSON parse error?

A JSON parse error occurs when a parser cannot interpret supplied text as valid JSON. The input may contain invalid syntax or may not actually be JSON.

Q:What causes JSON parse errors?

Q:How do I fix a JSON parse error?

Q:What does Unexpected token mean in JSON?

It usually means the parser encountered a character or value that isn't valid at that location. The actual mistake can occur slightly earlier, such as a missing comma.

Q:What does Unexpected end of JSON input mean?

It generally means the parser reached the end before completing a valid JSON value. Common causes are incomplete JSON, missing closing brackets, an unfinished string, or an empty input.

Q:Why does JSON.parse fail?

JSON.parse fails when its argument is not valid JSON text. Single quotes, trailing commas, comments, invalid values, missing punctuation, incomplete data, and HTML responses are common causes.

Q:Why am I getting a JSON parse error from an API?

Q:Why does JSON.parse say Unexpected token <?

Q:Can a missing comma cause a JSON parse error?

Yes. A missing comma between object properties or array elements commonly causes the parser to fail when it reaches the next token.

Q:Can single quotes cause a JSON parse error?

Yes. Standard JSON uses double quotes for property names and string values. Single-quoted JavaScript object literals are not valid JSON.

Q:Can trailing commas cause a JSON parse error?

Yes. Standard JSON does not permit a trailing comma after the final object property or array element.

Q:Can comments cause a JSON parse error?

Yes. Standard JSON does not support // or /* ... */ comments. A parser that expects standard JSON can reject documents containing them.

Q:Can an empty response cause a JSON parse error?

Yes. An empty string contains no JSON value, so attempting to parse it normally fails. An API client should handle documented no-content responses separately.

Q:Can formatting fix a JSON parse error?

Not by itself. Formatting generally requires valid JSON before it can produce formatted output. Syntax errors must be identified and corrected separately.

Q:Is a JSON parse error the same as a JSON syntax error?

Q:What is the difference between parsing and validation?

Parsing converts JSON text into a data structure. Validation checks whether the JSON syntax is valid and, at a different level, whether the resulting data satisfies schema or application rules.

Q:Why is valid JSON still rejected by my API?

Q:How do I find the exact character causing a JSON parse error?

Q:How do I handle JSON parsing errors in JavaScript?

Wrap JSON.parse() in try/catch, record safe diagnostic information, and handle invalid input without exposing sensitive payload contents.

Q:How do I handle JSON parsing errors in Python?

Catch json.JSONDecodeError when using json.loads() or json.load(), then use its line and column information to locate the malformed input.

Q:How do I check whether an API response is JSON?

Inspect the HTTP status, Content-Type header, and raw response body. Do not assume every successful or error response contains JSON.

Q:What should I do if JSON parsing fails on a webhook?

Q:Can Git merge conflicts cause JSON parse errors?

Yes. Unresolved conflict markers such as <<<<<<<, =======, and >>>>>>> are not valid JSON and can cause parsing to fail.

Q:Can JSON be parsed if it contains comments?

Not as standard JSON. Some JSON-like configuration formats allow comments, but a strict standard JSON parser may reject them.

Q:Can JSON.parse parse a JavaScript object directly?

No. JSON.parse() expects a JSON string. If you already have a JavaScript object, you can use it directly or serialize it with JSON.stringify() when you need JSON text.