标签：#extract

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.