Convert XZ to TSV
Turn XZ archives into TSV. 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 text inside, unpacked.The xz layer comes off and the TSV inside is written as it was.
What you get
One file. The xz layer is removed, and the bytes inside are written out as they were. Nothing in the content is rewritten.
This works when the file inside the XZ is TSV. The conversion trusts you on that: you ask for the format you know is inside.
What is refused
Anything else is refused. If you ask for TSV but the XZ holds a different format, the conversion does not reshape it into TSV.
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. It stops withinput_corruptedwhen the file could not be parsed.Options and the other direction
This conversion has no options. There is nothing to set.
To pack a TSV file back into an archive, use TSV to XZ. To see the rest of the family, browse every XZ conversion.
XZ and TSV.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
Tab-Separated Values
Tab-separated values.
- Extensions
- .tsv .tab
- MIME type
- text
/tab -separated -values - Kind
- Text and data
In your code.The same XZ to TSV conversion through the API, for your app or your agent.
$ cv convert archive.xz archive.tsv$ cv convert archive.xz archive.tsvQuestions.What people ask about XZ to TSV.
No. The bytes inside the XZ are written as they were. Only the xz layer is removed.
It is refused. Ask for the format you know is inside the archive.
The file could not be parsed. The conversion stops with input_corrupted in that case.
The XZ here is a single file compressed with xz. The result is one file.