Convert LZ4 to JSONL
Turn LZ4 archives into JSONL. The LZ4 layer is removed and the bytes inside are written as they were.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop LZ4 files on the dialor turn it to pick what to do
JSONL from an LZ4 file.The LZ4 layer comes off and the bytes inside are written out as they were.
What you get
One JSONL file. The LZ4 compression is removed, and the bytes that were inside are written as they were, so the content is the same as before it was compressed.
JSONL holds one JSON object per line. It is the format of logs and datasets.
Ask for what is inside
Choose JSONL only when you know the compressed file holds JSONL. Any other content is refused, so the format you ask for has to match what the LZ4 file contains.
A conversion stops with
unsupported_elementswhen the file holds something the target cannot carry, or when some inputs cannot become the format the join takes. A conversion stops withinput_corruptedwhen the file could not be parsed.Going the other way
To compress a JSONL file again, use JSONL to LZ4. To combine several JSONL files into one, see merge JSONL.
LZ4 and JSONL.What each format is.
The formats
LZ4
A single file compressed with LZ4, built for speed over ratio.
- Extensions
- .lz4
- MIME type
- application
/x -lz4 - Kind
- Archives
JSON Lines
JSON Lines, one JSON object per line, the format of logs and datasets.
- Extensions
- .jsonl .ndjson
- MIME type
- application
/jsonl - Kind
- Text and data
In your code.The same LZ4 to JSONL conversion through the API, for your app or your agent.
$ cv convert archive.lz4 archive.jsonl$ cv convert archive.lz4 archive.jsonlQuestions.What people ask about LZ4 to JSONL.
No. The LZ4 layer is removed and the bytes inside are written as they were.
No. Ask for the format you know is inside. Anything else is refused.
The file could not be parsed. The conversion stops with input_corrupted in that case.
One file. The output is a single JSONL file.