Extra data: line L column C (char N)
This message comes from CPython json.loads on CPython 3.12.3. In this registry it is produced by 3 distinct mistakes. Positions in the real message vary with your input; the causes do not.
What produces this message
Extra data after a JSON document
{"a": 1}{"b": 2}Exact message: Extra data: line 1 column 9 (char 8)
Fix: Split the documents, or if you meant a stream of records, use NDJSON and parse one line at a time.
NDJSON fed to a whole-document JSON parser
{"a":1}
{"a":2}Exact message: Extra data: line 2 column 1 (char 8)
Fix: Read line by line and parse each line separately.
Trailing characters after a JSON document
{"a": 1} garbageExact message: Extra data: line 1 column 10 (char 9)
Fix: Trim everything after the final closing brace, and check whatever produced the file for stray writes to stdout.
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 |
|---|---|
| Gson | Use JsonReader.setLenient(true) to accept malformed JSON at line L column C path $… |
| Gson JsonParser (lenient off) | Use JsonReader.setLenient(true) to accept malformed JSON at line L column C path $… |
| JSON5 | JSON5: invalid character 'g' at 1:10JSON5: invalid character '{' at 1:9JSON5: invalid character '{' at 2:1 |
| JSON::PP | garbage after JSON object, at character offset N (before "…") |
| JavaScriptCore JSON.parse | JSON Parse error: Unable to parse JSON string |
| Newtonsoft.Json JsonConvert | Additional text encountered after finished reading JSON content: g. Path '', line L, position N.Additional text encountered after finished reading JSON content: {. Path '', line L, position N. |
| Newtonsoft.Json JsonTextReader | Additional text encountered after finished reading JSON content: g. Path '', line L, position N.Additional text encountered after finished reading JSON content: {. Path '', line L, position N. |
| Ruby JSON.parse | unexpected token at '…' |
| SpiderMonkey JSON.parse | JSON.parse: unexpected non-whitespace character after JSON data at line L column C of the JSON data |
| System.Text.Json Deserialize | 'g' is invalid after a single JSON value. Expected end of data. Path: $ | LineNumber: L | BytePositionInLine: C.'{' is invalid after a single JSON value. Expected end of data. Path: $ | LineNumber: L | BytePositionInLine: C. |
| System.Text.Json JsonDocument | 'g' is invalid after a single JSON value. Expected end of data. LineNumber: L | BytePositionInLine: C.'{' is invalid after a single JSON value. Expected end of data. LineNumber: L | BytePositionInLine: C. |
| V8 JSON.parse | Unexpected non-whitespace character after JSON at position N (line L column C) |
| encoding/json Unmarshal | invalid character 'g' after top-level valueinvalid character '{' after top-level value |
| hjson | Syntax error, found trailing characters at line L,1 >>>{"a":2} {"a":3} ...Syntax error, found trailing characters at line L,8Syntax error, found trailing characters at line L,9 |
| json-bigint | Syntax error |
| json_decode | Syntax error |
| orjson | unexpected content after document: line L column C (char N) |
| serde_json::from_str | trailing characters at line L column C |
| ujson | Trailing data |
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.