JSON Parse error: Unrecognized token ''
This message comes from JavaScriptCore JSON.parse on JavaScriptCore (Bun 1.4.1). In this registry it is produced by 1 distinct mistake. Positions in the real message vary with your input; the causes do not.
Causes
What produces this message
UTF-8 BOM before a JSON document
Input
{"a": 1}Exact message: JSON Parse error: Unrecognized token ''
Fix: Save the file as UTF-8 without BOM. In PowerShell use `Set-Content -Encoding utf8NoBOM`; in Notepad choose 'UTF-8' rather than 'UTF-8 with BOM'.
Same bug, other languages
What other parsers say about the same input
If a colleague reports a different message for what looks like the same file, this is why.
| Parser | Message for the same inputs |
|---|---|
| CPython json.loads | Unexpected UTF-8 BOM (decode using utf-8-sig): line L column C (char N) |
| JSON::PP | malformed JSON string, neither array, object, number, string or atom, at character offset N (before "…") |
| Jackson ObjectMapper | Unexpected character ('?' (code 65279 / 0xfeff)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false') |
| Newtonsoft.Json JsonConvert | Unexpected character encountered while parsing value: . Path '', line L, position N. |
| Newtonsoft.Json JsonTextReader | Unexpected character encountered while parsing value: . Path '', line L, position N. |
| Ruby JSON.parse | unexpected token at '…' |
| SpiderMonkey JSON.parse | JSON.parse: unexpected character at line L column C of the JSON data |
| System.Text.Json Deserialize | '0xEF' is an invalid start of a value. Path: $ | LineNumber: L | BytePositionInLine: C. |
| System.Text.Json JsonDocument | '0xEF' is an invalid start of a value. LineNumber: L | BytePositionInLine: C. |
| V8 JSON.parse | Unexpected token '', "{"a": 1}" is not valid JSON |
| encoding/json Unmarshal | invalid character 'ï' looking for beginning of value |
| json-bigint | Unexpected '' |
| json_decode | Syntax error |
| orjson | UTF-8 byte order mark (BOM) is not supported: line L column C (char N) |
| serde_json::from_str | expected value at line L column C |
| ujson | Expected object or value |
Sources
Standards this registry is checked against
- RFC 8259 (STD 90) — The JavaScript Object Notation (JSON) Data Interchange Format, T. Bray, Ed., 2017. The IETF Internet Standard for JSON. Obsoletes RFC 7159 and RFC 4627.
- ECMA-404, 2nd edition — The JSON Data Interchange Syntax, Ecma International, 2017. Ecma’s grammar for JSON. A normative reference of RFC 8259; the two define the same syntax.
- The Unicode Standard — The Unicode Standard, Core Specification, The Unicode Consortium, current. Normatively referenced by RFC 8259 for the definition of a character.
- IEEE 754-2019 — IEEE Standard for Floating-Point Arithmetic, IEEE, 2019. Referenced by RFC 8259 §6 as the basis for its interoperability guidance on numbers.
Only standards bodies and peer-reviewed venues are cited. Error strings on this site are observed by executing each parser; the standards above define what the parser is reacting to.