# Has anyone tried JASONLines? **URL:** \ **Category:** General\ **Created:** [September 25, 2026, 10:27pm UTC](https://forum.xojo.com/t/has-anyone-tried-jasonlines/88933 "2026-09-25T22:27:17Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Philip\_Cumpston](https://forum.xojo.com/user_avatar/forum.xojo.com/philip_cumpston/32/621_2.png) [@Philip\_Cumpston](https://forum.xojo.com/u/Philip_Cumpston)\ **Post date:** [September 25, 2026, 10:27pm UTC](https://forum.xojo.com/t/has-anyone-tried-jasonlines/88933/1 "2026-09-25T22:27:17Z")
This looks like a superior way to use JASON:–\> [JASONL](https://jsonlines.org) ---
**Author:** ![Christian\_Wheel](https://forum.xojo.com/user_avatar/forum.xojo.com/christian_wheel/32/20536_2.png) [@Christian\_Wheel](https://forum.xojo.com/u/Christian_Wheel)\ **Post date:** [September 26, 2026, 12:19am UTC](https://forum.xojo.com/t/has-anyone-tried-jasonlines/88933/2 "2026-09-26T00:19:39Z")
Am I understanding this correctly that this is all valid JSON, just with a convention to use newlines for human readability? ---
**Author:** ![Jared\_Feder](https://forum.xojo.com/user_avatar/forum.xojo.com/jared_feder/32/3036_2.png) [@Jared\_Feder](https://forum.xojo.com/u/Jared_Feder)\ **Post date:** [September 26, 2026, 2:10am UTC](https://forum.xojo.com/t/has-anyone-tried-jasonlines/88933/3 "2026-09-26T02:10:22Z")
Agreed. It is nicely readable, but that isn’t primary purpose of JSON. I do like the idea of some sort of script that could convert JSON into that format just to preview (or edit I suppose). ---
**Author:** ![Philip\_Cumpston](https://forum.xojo.com/user_avatar/forum.xojo.com/philip_cumpston/32/621_2.png) [@Philip\_Cumpston](https://forum.xojo.com/u/Philip_Cumpston)\ **Post date:** [September 26, 2026, 5:36am UTC](https://forum.xojo.com/t/has-anyone-tried-jasonlines/88933/4 "2026-09-26T05:36:12Z")
No - it is faster and doesn’t load the entire code before running it - it does it line by line and skips errors in layout. It looks like a much better way to use JSON syntax ---
**Author:** ![MarkusR](https://forum.xojo.com/user_avatar/forum.xojo.com/markusr/32/685_2.png) [@MarkusR](https://forum.xojo.com/u/MarkusR)\ **Post date:** [September 26, 2026, 6:26am UTC](https://forum.xojo.com/t/has-anyone-tried-jasonlines/88933/5 "2026-09-26T06:26:07Z")
why they not show a example with decimal, date time values or binary data. json is horror if everything can be there or not if you use a rest api. repeating the columns as key every row is for bigger data exchange impractical. ---
**Author:** ![Jeff\_Tullin](https://forum.xojo.com/user_avatar/forum.xojo.com/jeff_tullin/32/693_2.png) [@Jeff\_Tullin](https://forum.xojo.com/u/Jeff_Tullin)\ **Post date:** [September 26, 2026, 8:59am UTC](https://forum.xojo.com/t/has-anyone-tried-jasonlines/88933/6 "2026-09-26T08:59:19Z")
> [@MarkusR](#): > > repeating the columns as key every row is for bigger data exchange impractical. But it will zip efficiently. As an XML user, I see this as much more approachable than ‘standard’ JSON ---
**Author:** ![MarkusR](https://forum.xojo.com/user_avatar/forum.xojo.com/markusr/32/685_2.png) [@MarkusR](https://forum.xojo.com/u/MarkusR)\ **Post date:** [September 26, 2026, 9:35am UTC](https://forum.xojo.com/t/has-anyone-tried-jasonlines/88933/7 "2026-09-26T09:35:28Z")
It depends on the use case. For further processing, unzipping adds another step. OT if possible i like to use Object Serialization and Deserialization. xojo should provide this essential feature and look how ms c# do it. the good thing at Serialization/Deserialization is you can save and load(restore) complex hierarchy of objects. in asp .net you can have a web service input with json or xml and it create/map it to a handy object. ---
**Author:** ![AlbertoD](https://forum.xojo.com/letter_avatar_proxy/v4/letter/a/dbc845/32.png) [@AlbertoD](https://forum.xojo.com/u/AlbertoD)\ **Post date:** [September 26, 2026, 11:42am UTC](https://forum.xojo.com/t/has-anyone-tried-jasonlines/88933/8 "2026-09-26T11:42:18Z")
Sorry, I had to ask ChatGPT for the differences: The main difference is **structure** : ### JSON A single valid JSON document containing one value—often an object or array. ```auto { "name": "Alice", "age": 30 } ``` Or multiple records in an array: ```auto [ {"name": "Alice", "age": 30}, {"name": "Bob", "age": 25} ] ``` ### JSONL / JSON Lines A **text file where each line is a separate, valid JSON value** , usually an object. ```auto {"name": "Alice", "age": 30} {"name": "Bob", "age": 25} {"name": "Charlie", "age": 35} ``` ### Key difference | | JSON | JSONL | | --- | --- | --- | | Structure | One JSON document | One JSON value per line | | Multiple records | Usually an array | Separate lines | | Streaming | Less convenient | Excellent | | Common use | APIs/config files | Logs, datasets, ML pipelines | **Rule of thumb:** Use **JSON** for structured documents; use **JSONL** when you have lots of independent records that you want to process one at a time. ---
**Author:** ![Clifford\_Antrim](https://forum.xojo.com/user_avatar/forum.xojo.com/clifford_antrim/32/507_2.png) [@Clifford\_Antrim](https://forum.xojo.com/u/Clifford_Antrim)\ **Post date:** [September 26, 2026, 12:28pm UTC](https://forum.xojo.com/t/has-anyone-tried-jasonlines/88933/9 "2026-09-26T12:28:41Z")
I have used JSONL once already (at Codex’s suggestion). I can’t remember the exact case for it (probably serialization of lots of records), but I do remember that it fit the bill for what I needed. ---
**Author:** ![Rick\_Araujo](https://forum.xojo.com/user_avatar/forum.xojo.com/rick_araujo/32/251_2.png) [@Rick\_Araujo](https://forum.xojo.com/u/Rick_Araujo)\ **Post date:** [September 26, 2026, 11:58pm UTC](https://forum.xojo.com/t/has-anyone-tried-jasonlines/88933/10 "2026-09-26T23:58:14Z")
Not a fan. I usually pack my data in pure JSON near to TOML. **Regular JSON:** (99 bytes) ```auto [ {"name": "Alice", "age": 30}, {"name": "Bob", "age": 25}, {"name": "Charlie", "age": 35} ] ``` **JSONL:** (87 bytes) ```auto {"name": "Alice", "age": 30} {"name": "Bob", "age": 25} {"name": "Charlie", "age": 35} ``` **Structured JSON:** (72 bytes) I designed the structure, so I know that the first line carries the columns’ titles and the rest are values ```auto [ ["name", "age"], ["Alice", 30], ["Bob", 25], ["Chalie", 35] ] ``` Same as above, just one liner packed for computers, not humans: (55 bytes) ```auto [["name","age"],["Alice",30],["Bob",25],["Chalie",35]] ```