Convert XZ to JSONL
Turn XZ archives into JSONL. The xz layer is removed and the bytes inside are written as they were.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop XZ files on the dialor turn it to pick what to do
The JSON Lines inside, unwrapped.The xz layer comes off and the file inside is written as it was.
What you get
One JSONL file. The conversion removes the xz compression and writes the bytes inside exactly as they were stored.
Ask for JSONL only when you know the xz file holds JSON Lines, one JSON object per line. Any other format is refused.
What it does not do
This is not a conversion of the content. The conversion takes off the xz layer and does nothing else, so the file inside has to be JSONL already.
To go the other way and compress a JSONL file, use JSONL to XZ.
When it stops
If the xz file cannot be parsed, the conversion stops with
input_corrupted.If the file holds something the target cannot carry, it stops with
unsupported_elements.
XZ and JSONL.What each format is.
The formats
XZ
A single file compressed with xz, the LZMA format of most Linux distributions.
- Extensions
- .xz
- MIME type
- application
/x -xz - 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 XZ to JSONL conversion through the API, for your app or your agent.
$ cv convert archive.xz archive.jsonl$ cv convert archive.xz archive.jsonlQuestions.What people ask about XZ to JSONL.
No. The xz layer is removed and the bytes inside are written as they were.
It is refused. Ask for the format you know is inside the xz file.
One file. The xz file holds a single file, and that file is the output.
The file could not be parsed as xz. The conversion stops with input_corrupted in that case.