JSON Parse Error: How to Fix All Common Errors (Complete Guide)

If you've ever worked with JSON data in JavaScript, Python, or any other language, you've probably encountered the dreaded JSON parse error. These errors can be frustrating because they often provide cryptic messages like Unexpected token or Unexpected end of JSON input without telling you exactly what's wrong.

In this comprehensive guide, we'll explore every type of JSON parse error you might encounter, explain exactly what causes each one, and show you how to fix them with real code examples. Whether you're a beginner or an experienced developer, this guide will help you become a JSON debugging expert.

What is JSON Parse Error?

A JSON parse error occurs when you try to convert a string into a JavaScript object using JSON.parse(), but the string doesn't contain valid JSON syntax. The JavaScript engine can't understand the data structure, so it throws an error.

// Trying to parse invalid JSON
const badJSON = '{ name: "Alice", age: 25 }'; // Missing quotes around "name"

try {
    const data = JSON.parse(badJSON);
} catch (error) {
    console.log(error.message);
    // Output: "Unexpected token n in JSON at position 2"
}

The error message tells us there's an "Unexpected token n" at position 2. This is because name should be "name" in valid JSON — all property names must be double-quoted strings.

Most Common JSON Parse Errors

Here are the top 5 JSON parse errors that developers encounter most frequently:

• Unexpected token <X> — Invalid character found where it shouldn't be
• Unexpected end of JSON input — JSON is incomplete (missing brackets)
• Invalid JSON — General syntax error
• Trailing comma error — Comma after the last element
• Single quote error — Using ' instead of "

Let's dive deep into each error type with examples and solutions.

Error #1: Unexpected Token

The "Unexpected token" error is the most common JSON parse error. It means the parser found a character that doesn't belong where it was found.

Common Causes:

1. Unquoted Property Names

{
    name: "Alice",
    age: 25
}

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

2. Comments in JSON

{
    "name": "Alice",
    // This is a comment
    "age": 25
}

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

3. Undefined or NaN Values

{
    "value": undefined,
    "number": NaN
}

{
    "value": null,
    "number": 0
}

Error #2: Unexpected End of JSON Input

This error occurs when your JSON string is incomplete — usually because of missing closing brackets or braces.

Common Causes:

1. Missing Closing Bracket

{
    "name": "Alice",
    "skills": ["JavaScript", "Python"]
// Missing } here

{
    "name": "Alice",
    "skills": ["JavaScript", "Python"]
}

2. Parsing Empty String

// This will throw "Unexpected end of JSON input"
const data = JSON.parse("");

const jsonString = getDataFromAPI();

if (jsonString && jsonString.trim()) {
    const data = JSON.parse(jsonString);
} else {
    console.log("No JSON data received");
}

Error #3: Invalid JSON Format

Sometimes JSON can have structural problems that make it completely invalid.

Multiple Root Elements

{"name": "Alice"} {"name": "Bob"}

[
    {"name": "Alice"},
    {"name": "Bob"}
]

Error #4: Trailing Comma

Unlike JavaScript, JSON doesn't allow trailing commas after the last element in arrays or objects.

{
    "name": "Alice",
    "age": 25,   // This comma breaks JSON!
}

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

Error #5: Single Quotes Instead of Double Quotes

JSON requires double quotes for all strings. Single quotes are not valid.

{
    'name': 'Alice',
    'city': 'New York'
}

{
    "name": "Alice",
    "city": "New York"
}

How to Debug JSON Errors

Follow this step-by-step debugging workflow when you encounter JSON parse errors:

Step 1: Read the Error Message Carefully

The error message contains valuable information:

• "Unexpected token X" — tells you which character is problematic
• "at position Y" — tells you exactly where in the string

Step 2: Use a JSON Validator

Paste your JSON into our JSON Formatter tool. It will:

• Highlight the exact line with the error
• Show a descriptive error message
• Auto-format valid JSON with proper indentation

Step 3: Safe Parsing with try-catch

function safeParseJSON(jsonString) {
    try {
        return { data: JSON.parse(jsonString), error: null };
    } catch (error) {
        return { data: null, error: error.message };
    }
}

// Usage
const result = safeParseJSON(userInput);
if (result.error) {
    console.error("JSON Parse Error:", result.error);
} else {
    console.log("Parsed data:", result.data);
}

Best Practices to Avoid JSON Errors

1. Always use double quotes — Never use single quotes in JSON
2. Validate before parsing — Use a validator during development
3. Use JSON.stringify() — Let JavaScript create JSON for you
4. Handle errors gracefully — Always wrap parse in try-catch
5. Check for empty responses — Verify API responses before parsing
6. Avoid manual JSON editing — Use tools or libraries when possible

// Instead of manually writing JSON strings...
const data = {
    name: "Alice",
    skills: ["JavaScript", "Python"],
    active: true
};

// Let JSON.stringify create valid JSON
const jsonString = JSON.stringify(data, null, 2);
console.log(jsonString);
// Output: perfectly formatted valid JSON!

Code Formatter © 2026. Professional developer tools built with privacy and performance in mind.