Why Does This Download End in .tar.zst?

You download a backup, software package, or dataset and find a file with an unusually long extension:

something.tar.zst

It looks like two file formats have somehow been glued together.

That is essentially what happened — but each part has a different job.

The .tar part bundles files and folders together. The .zst part compresses that bundle.

Understanding the difference also explains why these files can be awkward to open on a Mac.

Two formats, two jobs

ZIP is both an archive format and a compression format. It can collect multiple files and folders while also reducing their size.

Zstandard works differently.

Zstandard is primarily a compression format. It can compress a file very quickly and efficiently, but it does not by itself turn a folder containing many files into a conventional archive.

That is where TAR comes in.

TAR collects files, folders, filenames, permissions, and directory structures into one .tar file. Despite its common association with compressed downloads, TAR does not necessarily compress that data.

The result can be large, but it contains everything in one structured file.

Zstandard then compresses that TAR file:

folder with files
        ↓
something.tar
        ↓
something.tar.zst

This produces the double extension.

tar tells you what is inside the compressed data.

zst tells you how that data was compressed.

Why not just use ZIP?

ZIP remains convenient because nearly every operating system can open it without additional software.

But convenience is not its only consideration.

Zstandard was designed for fast, lossless compression. It can provide a useful combination of compression ratio and decompression speed, especially for large backups, software packages, logs, databases, and datasets.

That makes .tar.zst attractive for systems that regularly process large amounts of data.

The sender gets a compact archive that can be created and extracted quickly. The problem only becomes visible when that file reaches an operating system without native Zstandard support.

Where macOS gets stuck

macOS understands TAR archives. If you have a normal .tar file, Finder can extract it using the built-in Archive Utility.

But a .tar.zst file is still wrapped in an outer Zstandard layer.

Archive Utility cannot natively decompress that layer. Double-clicking the file therefore does not reveal the TAR archive inside.

The Mac never reaches the part it understands.

Conceptually, opening the file requires two separate operations:

something.tar.zst
        ↓ decompress ZST
something.tar
        ↓ extract TAR
folder with files

The second step is not the problem. macOS can handle TAR.

The missing part is the first step.

The Terminal approach

It is possible to add Zstandard support manually.

After installing a Zstandard command-line utility, the outer layer can be decompressed with a command such as:

zstd -d something.tar.zst

That produces:

something.tar

The TAR archive must then be extracted:

tar -xf something.tar

This works, but it involves installing an additional command-line tool, entering two commands, and optionally removing the intermediate TAR file afterward.

That is a lot of ceremony just to open a downloaded file.

Open both layers in one step

unpackZST handles the missing Zstandard layer through a small native macOS interface.

Drop a .tar.zst file onto the app and it first decompresses the ZST data. It can then detect the resulting TAR archive and extract that automatically.

Instead of leaving you with another file to open, it takes you directly to the original folder and its contents:

something.tar.zst
        ↓ unpackZST
folder with files

The intermediate .tar file can also be deleted automatically after successful extraction.

No Terminal commands are required, and no files are uploaded anywhere. Decompression happens locally on the Mac.

What about a plain .zst file?

Not every ZST file contains a TAR archive.

A file called:

database.sql.zst

will normally become:

database.sql

A file called:

records.json.zst

will become:

records.json

In these cases, Zstandard has compressed one individual file. There is no TAR layer and therefore no second extraction step.

This is why .zst and .tar.zst should not be treated as exactly the same thing:

• .zst usually contains one compressed file or data stream.
• .tar.zst contains a TAR archive compressed with Zstandard.

unpackZST handles both. A plain .zst file is decompressed to its original file, while a .tar.zst archive can be decompressed and extracted automatically.

The extension explains the workflow

A .tar.zst file is not one unusually complicated format.

It is two established tools working together:

TAR bundles the files. Zstandard compresses the bundle.

That combination is fast and efficient, but macOS lacks native support for its outer ZST layer.

Once that layer is handled, the rest is straightforward.

unpackZST opens .zst and .tar.zst files on macOS without Terminal commands or additional setup.