JsonForge · JSON errors
Unexpected token at position 0
Something invisible sits before the first brace — most often a UTF-8 byte order mark written by Excel, Notepad or a Windows export.
Position 0 with a document that looks correct is the signature of a BOM. Strip it: raw.replace(/^\uFEFF/, "").
The smallest input that causes it
{"a": 1}JSON.parse on that gives, verbatim:
Unexpected token '', "{"a": 1}" is not valid JSONThe fix
{"a": 1}That version parses.
Find it in your own document
Paste the JSON and get the error located by line and column, the document formatted, a schema inferred from it, and a diff against another version.
Open JsonForgeOther JSON errors
- Unexpected end of JSON input
- Unexpected token '<', "<html>" is not valid JSON
- "undefined" is not valid JSON
- Expected double-quoted property name in JSON
- Expected property name or '}' in JSON at position 1
- Single quotes are not valid JSON
- Unexpected non-whitespace character after JSON
- Unexpected number in JSON
- Bad control character in string literal in JSON
- Bad escaped character in JSON