Convert ZST to TSV
Turn ZST archives into TSV. The Zstandard layer is removed and the bytes inside are written as they were.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop ZST files on the dialor turn it to pick what to do
The tab-separated file inside your ZST.The Zstandard layer comes off. The bytes inside are written as they were.
What you get
One TSV file. The conversion removes the Zstandard compression and writes out the bytes inside without changing them. Nothing is reformatted, re-encoded or rearranged.
What you need to know first
Ask for the format you know is inside. If the file in the ZST is not tab-separated values, the conversion refuses it.
This is not a conversion between table formats. It only unpacks the archive, so the result is only as much a TSV as the file you packed.
When it stops
A file that cannot be parsed as ZST stops with
input_corrupted.A file stops with
unsupported_elementswhen it holds something the target cannot carry, or when some inputs cannot become the format the join takes.Related conversions
To compress a TSV again, use TSV to ZST. To combine several TSV files into one, merge TSV does that.
ZST and TSV.What each format is.
The formats
Zstandard
A single file compressed with Zstandard, fast to compress and to decompress.
- Extensions
- .zst
- MIME type
- application
/zstd - 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 ZST to TSV conversion through the API, for your app or your agent.
$ cv convert archive.zst archive.tsv$ cv convert archive.zst archive.tsvQuestions.What people ask about ZST to TSV.
No. The Zstandard layer is removed and the bytes inside are written as they were.
The conversion is refused. Ask for the format you know is inside the ZST.
One file.
The file could not be parsed. The conversion cannot read it as a ZST, so it stops.