Convert LZ4 to TSV
Turn LZ4 archives into TSV. 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
TSV text out of an LZ4 file.The LZ4 layer comes off and the TSV inside is written out as it was.
What you get
One TSV file. The conversion removes the LZ4 layer and writes the bytes inside exactly as they were stored. Nothing in the content is changed, reordered or rewritten.
There are no options to set. The result depends only on what the LZ4 file holds.
Ask for what is inside
Choose TSV only when you know the LZ4 file holds tab-separated text. Any other target format than the one inside is refused. The conversion unpacks the data but does not turn one format into another.
To go the other way, use TSV to LZ4.
When it stops
A file that cannot be parsed as LZ4 stops with
input_corrupted.A file stops with
unsupported_elementswhen it holds something TSV cannot carry, or when the input cannot become the format the join takes.
LZ4 and TSV.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
Tab-Separated Values
Tab-separated values.
- Extensions
- .tsv .tab
- MIME type
- text
/tab -separated -values - Kind
- Text and data
In your code.The same LZ4 to TSV conversion through the API, for your app or your agent.
$ cv convert archive.lz4 archive.tsv$ cv convert archive.lz4 archive.tsvQuestions.What people ask about LZ4 to TSV.
No. The bytes inside the LZ4 file are written as they were. Only the LZ4 layer is removed.
No. Ask for the format you know is inside. A request for any other format is refused.
The file could not be parsed as LZ4. The conversion stops there.
No. The output is one TSV file. To combine several TSV files, you can merge TSV.