<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>JSON Repair Tool — Blog</title>
    <link>https://json-repair-tool-a5c.pages.dev/blog/</link>
    <description>Guides and explainers from JSON Repair Tool</description>
    <language>en-us</language>
<item>
      <title>How to Handle Dates in JSON: Why JSON.parse Gives You a String, Not a Date</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-date-format-parse-handling</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-date-format-parse-handling</guid>
      <description>How to handle dates in JSON: JSON has no date type, so stringify writes ISO 8601 strings and parse hands back strings. The reviver fix, the midnight UTC trap, and the format rule that prevents both.</description>
      <pubDate>Thu, 29 Oct 2026 12:00:00 GMT</pubDate>
    </item>

<item>
      <title>Why Your JSON Is Double Encoded (Stringified Twice) and How to Fix It</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-double-encoded-stringified-twice-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-double-encoded-stringified-twice-fix</guid>
      <description>Your JSON parses to a string full of backslashes instead of an object. That is double encoding: JSON.stringify ran twice. How to spot it, undo it, and stop it at the source.</description>
      <pubDate>Wed, 28 Oct 2026 12:00:00 GMT</pubDate>
    </item>
<item> <title>Fix JSON Trailing Comma Error in VS Code settings.json: Why It Passes There and Fails Everywhere Else</title> <link>https://json-repair-tool-a5c.pages.dev/blog/fix-json-trailing-comma-vscode-settings</link> <guid>https://json-repair-tool-a5c.pages.dev/blog/fix-json-trailing-comma-vscode-settings</guid> <description>Fix JSON trailing comma errors in VS Code settings.json: why settings.json tolerates them under JSONC while strict JSON parsers reject them, and how to catch the error before it ships.</description> <pubDate>Tue, 27 Oct 2026 12:00:00 GMT</pubDate> </item> <item>
      <title>Why JSON.stringify Drops Undefined and Functions (and the Replacer Fix)</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-stringify-removes-undefined-functions</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-stringify-removes-undefined-functions</guid>
      <description>Why JSON.stringify removes undefined and functions: JSON has no way to write them, so object properties vanish and array items become null. The replacer fix, and the PATCH trap to watch for.</description>
      <pubDate>Mon, 26 Oct 2026 12:00:00 GMT</pubDate>
    </item>
<item>
      <title>How to Fix JSON Unquoted Keys: You Pasted JavaScript, Not JSON</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-unquoted-keys-parse-error-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-unquoted-keys-parse-error-fix</guid>
      <description>Every key in JSON must be a double-quoted string. The error messages, the regex fix and its traps, and the serializer-first rule.</description>
      <pubDate>Sun, 25 Oct 2026 12:00:00 GMT</pubDate>
    </item>
<item>
      <title>How to Fix NaN and Infinity in JSON (and Stop JSON.parse Failing)</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-nan-infinity-parse-error-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-nan-infinity-parse-error-fix</guid>
      <description>How to fix NaN and Infinity in JSON: why JSON.parse rejects both, the null, string, and replacer fixes, and the Python allow_nan trap that ships invalid JSON.</description>
      <pubDate>Sat, 24 Oct 2026 12:00:00 GMT</pubDate>
    </item>
<item>
      <title>How to Fix Truncated JSON From AI Output</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/truncated-json-ai-output-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/truncated-json-ai-output-fix</guid>
      <description>Your LLM call returned JSON that stops mid-string and JSON.parse fails. Why models cut off output, how to detect it with finish_reason, and why closing the brackets is not always the right fix.</description>
      <pubDate>Fri, 23 Oct 2026 12:00:00 GMT</pubDate>
    </item>
<item>
      <title>Bad Escaped Character in JSON: Why Your Regex Breaks the Parser</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-bad-escaped-character-in-json-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-bad-escaped-character-in-json-fix</guid>
      <description>How to fix the JSON parse error "bad escaped character in JSON": JSON allows only eight escapes plus unicode, so \d, \w, \U and \x all fail. Where bad escapes hide and the serializer-first fix.</description>
      <pubDate>Thu, 22 Oct 2026 12:00:00 GMT</pubDate>
    </item>
<item>
      <title>Smart Quotes in JSON: Why Your Parser Chokes on Curly Quotes</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-smart-quotes-curly-quotes-parse-error-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-smart-quotes-curly-quotes-parse-error-fix</guid>
      <description>The fix for smart quotes curly quotes breaking your JSON parse error: why U+201C looks like a real quote, the four code points to replace, and the two-line normalize pass that ends it.</description>
      <pubDate>Wed, 21 Oct 2026 12:00:00 GMT</pubDate>
    </item>
<item>
      <title>How to Fix &quot;Do Not Know How to Serialize a BigInt&quot; in JSON.stringify</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-stringify-bigint-error-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-stringify-bigint-error-fix</guid>
      <description>The value arrived as a BigInt, usually a database id. Find the key, then pick from three fixes: convert at the source, use a replacer, or patch toJSON.</description>
      <pubDate>Tue, 20 Oct 2026 12:00:00 GMT</pubDate>
    </item>

<item>
      <title>How to Fix Python's JSONDecodeError: Expecting Value at Line 1 Column 1</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/python-jsondecodeerror-expecting-value-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/python-jsondecodeerror-expecting-value-fix</guid>
      <description>Python's "JSONDecodeError: Expecting value: line 1 column 1 (char 0)" means the parser found nothing valid at the first character. The four real causes (empty input, HTML instead of JSON, a BOM, the wrong file) and the safe-parse pattern that ends it.</description>
      <pubDate>Mon, 19 Oct 2026 12:00:00 GMT</pubDate>
    </item>

<item>
      <title>Unexpected Non-Whitespace Character After JSON: What It Means and How to Fix It</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-unexpected-non-whitespace-character-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-unexpected-non-whitespace-character-fix</guid>
      <description>JSON.parse throws “unexpected non-whitespace character after JSON” when two JSON values sit side by side. What the position number points to, the four ways it happens, and when to wrap values in an array versus parsing line by line.</description>
      <pubDate>Sun, 18 Oct 2026 12:00:00 GMT</pubDate>
    </item>

<item>
      <title>Unexpected Token '&lt;' in JSON at Position 0: Your API Returned HTML, Not JSON</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-unexpected-token-less-than-position-0-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-unexpected-token-less-than-position-0-fix</guid>
      <description>JSON.parse says "unexpected token &lt; at position 0" when the response is HTML, not JSON: an error page, a wrong URL, or an expired login. The three causes and the check-before-you-parse fix.</description>
      <pubDate>Sat, 17 Oct 2026 12:00:00 GMT</pubDate>
    </item>

<item>
      <title>Fixing the JSON BOM Byte Order Mark Parse Error: An Invisible Character at Position 0</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-bom-byte-order-mark-parse-error-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-bom-byte-order-mark-parse-error-fix</guid>
      <description>Your JSON looks valid but JSON.parse fails at position 0? A hidden byte order mark (BOM) is the likely culprit. What U+FEFF is, where it comes from, and the one-line fix that strips it.</description>
      <pubDate>Fri, 16 Oct 2026 12:00:00 GMT</pubDate>
    </item>

<item>
      <title>JSON5 vs JSON: What JSON5 Allows That Strict JSON Rejects</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json5-vs-json-what-json5-allows</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json5-vs-json-what-json5-allows</guid>
      <description>Every valid strict JSON file is valid JSON5, but not the reverse. What JSON5 allows that JSON rejects: comments, trailing commas, unquoted keys, single quotes, hex numbers, and when to use each.</description>
      <pubDate>Thu, 15 Oct 2026 12:00:00 GMT</pubDate>
    </item>

<item>
      <title>Unexpected Token &#x27;o&#x27; in JSON at Position 1: You Parsed an Object, Not a String</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-unexpected-token-o-parsed-object-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-unexpected-token-o-parsed-object-fix</guid>
      <description>JSON.parse unexpected token o in JSON at position 1 means you parsed something already parsed. The &#x27;o&#x27; is from [object Object]. How to find the double parse and fix it.</description>
      <pubDate>Wed, 14 Oct 2026 12:00:00 GMT</pubDate>
    </item>
<item>
      <title>JSON Duplicate Keys: Which Value Is Used, and Which One You Lose</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-duplicate-keys-which-value-wins</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-duplicate-keys-which-value-wins</guid>
      <description>RFC 8259 discourages JSON duplicate keys but never defines which value wins. In practice the last value wins in JavaScript, Python, and jq with no warning. Where dupes come from, and the copy-paste check that catches them.</description>
      <pubDate>Tue, 13 Oct 2026 12:00:00 GMT</pubDate>
    </item>
<item>
      <title>Unexpected Token 'u' in JSON at Position 0: You Parsed the Word "undefined"</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-unexpected-token-u-undefined-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-unexpected-token-u-undefined-fix</guid>
      <description>The parser saw the letter u because the value was undefined. Where undefined values sneak in, and the safeParse helper that ends this error for good.</description>
      <pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate>
    </item>
<item>
      <title>"Unexpected End of JSON Input": Empty Body, Cut-Off Payload, or Unclosed Bracket</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-unexpected-end-of-json-input-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-unexpected-end-of-json-input-fix</guid>
      <description>The parser reached the end while still waiting for a value. The three real causes: an empty response body, a truncated response, or hand-written JSON with a missing closer.</description>
      <pubDate>Sun, 11 Oct 2026 12:00:00 GMT</pubDate>
    </item>
                <item>
      <title>Why Does JSON Round Large Numbers? The 2^53-1 Precision Trap, Fixed</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-large-number-precision-loss-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-large-number-precision-loss-fix</guid>
      <description>The digits are exact in the text. The rounding happens in the JavaScript Number past 9,007,199,254,740,991. How to spot it and fix it.</description>
      <pubDate>Sat, 10 Oct 2026 12:00:00 GMT</pubDate>
    </item>
<item>
      <title>How to Fix the JSON Missing Comma Error (It Points at the Wrong Line)</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-missing-comma-parse-error-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-missing-comma-parse-error-fix</guid>
      <description>The parser reports the spot where it gave up, not where you slipped. Why missing commas point at the wrong line, the merge variant, and the auto-fix caveat.</description>
      <pubDate>Fri, 09 Oct 2026 12:00:00 GMT</pubDate>
    </item>
                <item>
      <title>How to Fix "Converting Circular Structure to JSON" in JavaScript</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-circular-structure-stringify-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-circular-structure-stringify-fix</guid>
      <description>The error names the property that closes the loop. Where circular references hide, the one copyable replacer fix, and the four real options ranked.</description>
      <pubDate>Thu, 08 Oct 2026 12:00:00 GMT</pubDate>
    </item>
                <item>
      <title>Bad Control Character in String Literal: The Invisible Newline That Breaks JSON</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-bad-control-character-string-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-bad-control-character-string-fix</guid>
      <description>The error reads "position 26" and position 26 looks empty. Where invisible newlines and tabs hide inside JSON strings, and the one repair rule that escapes them.</description>
      <pubDate>Wed, 07 Oct 2026 12:00:00 GMT</pubDate>
    </item>
<item>
      <title>Fixing Unescaped Quotes in JSON String Values (the Error That Points at the Wrong Spot)</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-unescaped-quotes-string-value-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-unescaped-quotes-string-value-fix</guid>
      <description>Your parser blames position 205. The real culprit is an unescaped quote inside a string value, sixty characters earlier. The one repair rule that finds it every time.</description>
      <pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate>
    </item>
<item>
      <title>How to Fix the JSON Single Quotes Error (Python Dicts, LLM Output, Apostrophes)</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-single-quotes-error-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-single-quotes-error-fix</guid>
      <description>JSON.parse chokes on {'name': 'Ada'} because JSON only allows double quotes. Where single-quoted JSON comes from, how to fix it safely, and the apostrophe trap.</description>
      <pubDate>Mon, 05 Oct 2026 12:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The Trailing Comma That Breaks Your JSON (And the 30-Second Fix)</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-trailing-comma-parse-error-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-trailing-comma-parse-error-fix</guid>
      <description>JSON.parse says "Unexpected token }" and the line looks fine. Why trailing commas break JSON, the deletion habit that causes them, and how to stop it for good.</description>
      <pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate>
    </item>

        <item>
      <title>NDJSON Broke My Parser: How to Fix JSON Lines Errors</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/ndjson-json-lines-parse-error-fix</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/ndjson-json-lines-parse-error-fix</guid>
      <description>Every line of your .jsonl file is valid JSON but JSON.parse fails on the whole file. Why NDJSON needs line-by-line parsing, the four common mistakes, and a copy-paste fix.</description>
      <pubDate>Sat, 03 Oct 2026 12:00:00 GMT</pubDate>
    </item>
<item>
      <title>JSON with Comments (JSONC): What It Is and How to Handle It</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/json-with-comments-jsonc</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/json-with-comments-jsonc</guid>
      <description>JSONC is JSON with comments, used by VS Code and TypeScript. Learn where JSONC is safe, where it breaks parsers, and how to strip comments correctly without regex mistakes.</description>
      <pubDate>Thu, 01 Oct 2026 18:42:53 GMT</pubDate>
    </item>
    <item>
      <title>Why Is My JSON Invalid? The 7 Syntax Errors That Break JSON.parse</title>
      <link>https://json-repair-tool-a5c.pages.dev/blog/why-is-my-json-invalid</link>
      <guid>https://json-repair-tool-a5c.pages.dev/blog/why-is-my-json-invalid</guid>
      <description>The seven mistakes behind nearly every invalid JSON error: trailing commas, single quotes, comments, unquoted keys, smart quotes, bad values, and unescaped control characters, with before and after examples.</description>
      <pubDate>Thu, 01 Oct 2026 18:42:53 GMT</pubDate>
    </item>
  </channel>
</rss>
