A .tar.zst file is a TAR archive compressed as one Zstandard frame. TAR supplies member names, sizes and metadata; Zstandard compresses the resulting sequential byte stream. The two layers are independent, so a valid Zstandard stream is not automatically a valid TAR archive.
Private for supported formats — processed in your browser
Convert supported files
Runs on your device
+
Drop TAR.ZST files here
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.
Zstandard was developed at Facebook and released in 2016 as a fast modern compression format. Combining it with TAR follows the same Unix pattern as .tar.gz and .tar.xz: one tool creates the archive and another compresses it. The pairing is increasingly common for Linux packages, source distributions and large build artefacts because decompression is fast while compression remains effective.
How TAR.ZST works
The outer stream begins with the Zstandard frame magic 28 B5 2F FD.
The decoded payload must be aligned to 512-byte TAR records and end with two zero records followed only by zero padding.
Every TAR header carries an octal checksum; filenames are also checked for absolute paths and parent traversal before extraction.
The local reader accepts one bounded standard frame and rejects skippable, concatenated, reserved, truncated and trailing frames.
A frame content checksum is verified when present, and the advertised decoded size must match the actual payload.
When to use TAR.ZST
Opening a Linux or build-system TAR.ZST package
Converting a Zstandard archive to ZIP for wider compatibility
Removing Zstandard compression while retaining TAR members
Repacking verified members as TAR.GZ
Strengths and limitations
Strengths
Fast decompression
Good compression ratios
TAR preserves paths and Unix metadata
Open format with broad command-line support
Limitations
Two nested formats must both validate
Some desktop archive tools still lack Zstandard support
One damaged frame can make every TAR member inaccessible
Compatibility
GNU tar with Zstandard, bsdtar, modern 7-Zip and current libarchive builds handle TAR.ZST. Novus Convert validates one Zstandard frame and then requires a checksum-valid complete TAR before offering ZIP, TAR or TAR.GZ. Plain .zst streams may still represent a single compressed file, but .tar.zst never falls back to that interpretation.
TAR member paths, sizes and supported timestamps survive TAR output; ZIP cannot represent every Unix ownership and mode field.