[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"howto:jsonl:mac:en":3},{"resolvedFromAlias":4,"canonicalExt":5,"ext":5,"name":6,"category":7,"categoryName":8,"updatedAt":9,"os":10,"osLabel":11,"quickSolution":12,"stepByStep":13,"recommendedSoftware":16,"alternativeMethods":17,"commonIssues":18,"securityNote":43,"extensionPath":44,"extensionLabel":45,"breadcrumbs":46,"metaDescription":56},false,"jsonl","JSON Lines (newline-delimited JSON)","data","Data","2026-06-12T08:16:40.900Z","mac","Mac","To open .JSONL files on Mac, open the file in a plain-text editor (for example, TextEdit in plain-text mode) to view the per-line JSON records.",[14,15],"Open the file in a plain-text editor (for example, TextEdit in plain-text mode) to view the per-line JSON records.","For analysis, load it in Python/pandas using pandas.read_json(path, lines=True).",[],[],[19,25,31,37],{"title":20,"description":21,"steps":22},"“It won’t parse as JSON” (expected a single JSON document)","A .jsonl file is not typically a single JSON array or object; it is many JSON values separated by newlines. Tools that expect one JSON document for the entire file may fail with errors after the first line.",[23,24],"Use a reader that supports line-delimited JSON (for example, pandas.read_json(..., lines=True)).","If a tool requires a single JSON array, convert by wrapping records into an array and inserting commas between lines (only if every line is valid JSON).",{"title":26,"description":27,"steps":28},"Some lines fail to parse (malformed JSON records)","Each line must be valid JSON text per RFC 8259. A single broken line (truncated output, unescaped quotes, trailing garbage) can cause partial imports to fail.",[29,30],"Check the failing line(s) in a text editor; validate that each line is complete JSON (often a single object).","Regenerate the file from the source system if it was truncated, or remove/repair only the malformed lines before re-importing.",{"title":32,"description":33,"steps":34},"Character encoding issues (garbled text or decode errors)","JSON is defined as Unicode text and is commonly encoded as UTF-8. If the file was produced in a different encoding or contains invalid byte sequences, some readers will error or display mojibake.",[35,36],"Try reopening the file with UTF-8 encoding in your editor or import tool.","If you control generation, ensure the producer writes UTF-8 and that each record remains valid JSON text.",{"title":38,"description":39,"steps":40},"Looks like JSON Lines but is actually JSON Text Sequences (RFC 7464)","Some streaming JSON uses RFC 7464 framing (record separator + JSON text) and is associated with application/json-seq, not newline-delimited JSON. A JSON Lines reader may not handle the extra framing character.",[41,42],"Check for a leading ASCII Record Separator (0x1E) before each JSON text; that indicates RFC 7464 JSON text sequences.","If it is RFC 7464, use tooling that supports JSON text sequences or strip the RS framing before treating it as line-delimited JSON.","A .jsonl file is plain text and does not contain executable code by itself, but it can still be dangerous to process if downstream systems treat its fields as code (for example, injecting untrusted strings into SQL, shell commands, or templates).","/file-extension/jsonl",".JSONL",[47,50,53],{"label":48,"to":49},"Home","/",{"label":51,"to":52},"How To","/file-extension",{"label":54,"to":55},"Open .JSONL on Mac","/how-to/open-jsonl-on-mac","Learn how to open .JSONL files on Mac with step-by-step instructions, recommended software, and troubleshooting tips."]