Why do smart quotes break JSON?

JSON requires plain ASCII double quotes (U+0022). Smart/curly quotes are different Unicode characters (“ U+201C, ” U+201D). JSON parsers do not recognise them as string delimiters and throw an Unexpected token error.

Where do smart quotes come from?

Word processors (Word, Google Docs), messaging apps (Slack, Teams), note-taking tools (Notion, Confluence), and macOS autocorrect all substitute curly quotes automatically when you type.

Does JSONBlitz fix single smart quotes too?

Yes. The left (‘) and right (’) single quotation marks are also replaced, along with backticks used as quote characters.

{}

JSONBlitz 100% PRIVATE

Input — paste anything

Fix Smart Quotes in JSON — Replace Curly Quotes with Straight Quotes

Content copied from Microsoft Word, Notion, Slack, or most word processors replaces standard straight quotes (") with typographic curly quotes (“ ”). These look almost identical on screen but break every JSON parser immediately. Paste your JSON below and JSONBlitz replaces all smart quotes with valid straight quotes automatically.

Ready — paste JSON or any text containing JSON

🌳

Tree view appears here after processing

Click nodes to copy JSONPath • Single-click a leaf to copy value

Formatted output appears here...

Process JSON to generate code...

Insights appear after processing

Shows what JSONBlitz changed to fix your JSON. Process some broken JSON first.

No changes recorded yet.

Fix Smart Quotes in JSON — Curly Quotes Cause Unexpected Token Errors

Typographic or "smart" quotes (“ ” ‘ ’) are used by word processors, messaging apps, and design tools to make text look better. JSON requires plain ASCII straight quotes (" and '). When JSON is written or edited in Word, Notion, Slack, or any tool with autocorrect enabled, these characters replace the valid ones invisibly — the JSON looks correct but fails to parse.

Why Smart Quotes Break JSON

JSON string delimiters must be the ASCII double quote (U+0022). The left double quotation mark (U+201C) and right double quotation mark (U+201D) are different Unicode characters. Any compliant JSON parser rejects them immediately, throwing an "Unexpected token" error pointing at the first curly quote it encounters.

Common Sources of Smart Quotes in JSON

Microsoft Word and Google Docs autocorrect, Slack and Teams message composition, Notion and Confluence editors, macOS autocorrect in any text field, and PDF copy-paste all commonly substitute typographic quotes. JSONBlitz detects and replaces all variants including single smart quotes and backticks used as quotes.

Frequently Asked Questions

Why do smart quotes break JSON?: JSON requires plain ASCII double quotes (U+0022). Smart/curly quotes are different Unicode characters (“ U+201C, ” U+201D). JSON parsers do not recognise them as string delimiters and throw an Unexpected token error.
Where do smart quotes come from?: Word processors (Word, Google Docs), messaging apps (Slack, Teams), note-taking tools (Notion, Confluence), and macOS autocorrect all substitute curly quotes automatically when you type.
Does JSONBlitz fix single smart quotes too?: Yes. The left (‘) and right (’) single quotation marks are also replaced, along with backticks used as quote characters.