Convert TXZ to TZST
Turn TXZ archives into TZST. The tar inside is kept byte for byte and only the compression changes, so every entry keeps its path, owner, permissions and times.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop TXZ files on the dialor turn it to pick what to do
Same archive, new compression.Only the compression changes. Every entry stays as it was.
What you get
A TZST file that holds the same tar as your TXZ. The tar inside is kept byte for byte, so every entry keeps its path, owner, permissions and times.
The result is one file. Nothing is added, removed or renamed inside the archive.
What changes
Only the outer compression. XZ is swapped for Zstandard. XZ archives are smaller than gzip, and Zstandard archives are fast to unpack and close to xz in size.
No options are needed, so there is nothing to set.
When it stops
If the file cannot be parsed, the conversion stops with
input_corrupted. This means the TXZ is not a readable XZ archive, so no TZST is produced.To go the other way, use TZST to TXZ.
TXZ and TZST.What each format is.
The formats
XZ Tar Archive
XZ-compressed tar archives. Smaller than gzip, common for source releases.
- Extensions
- .txz
- MIME type
- application
/x -xz - Kind
- Archives
Zstandard Tar Archive
Zstandard-compressed tar archives. Fast to unpack, close to xz in size.
- Extensions
- .tzst
- MIME type
- application
/zstd - Kind
- Archives
In your code.The same TXZ to TZST conversion through the API, for your app or your agent.
$ cv convert archive.txz archive.tzst$ cv convert archive.txz archive.tzstQuestions.What people ask about TXZ to TZST.
Yes. Each entry keeps its path, owner, permissions and times, because the tar inside is not changed.
No. The tar is kept byte for byte. Only the compression around it changes.
The file could not be parsed. The conversion stops and gives no TZST.
Yes. Use TZST to TXZ for that.