.zst File Extension
.zst file is, how to decompress Zstandard data, how Poly supports it, and when to use TAR, Gzip, XZ, or ZIP instead. File extension details for .zst
Storage Only| File type | Zstandard-compressed data |
|---|---|
| MIME type | |
| Encoding | Binary Zstandard frame or sequence of frames |
| Operating systems | Windows, macOS, Linux |
| Opens with | Zstandard CLI, GNU tar |
| Poly support | Yes. Poly stores, syncs, shares, versions, and downloads .zst files. |
| Indexed by Poly | Partial. Poly indexes the filename and ordinary file properties, not compressed contents. |
| Preview in Poly | No. Download the file and decompress it with a compatible utility. |
| Poly agent | No. The Poly agent cannot read data inside the compressed stream. |
What kind of file is a .zst?
A .zst file contains data compressed with Zstandard, usually called zstd. It normally uses the application/zstd MIME type. Zstandard is lossless, so decompression restores the original bytes exactly.1
Zstandard compresses a byte stream, not a folder tree. A backup.tar.zst file therefore has two layers: TAR supplies filenames, directories, permissions, and other archive metadata, while Zstandard compresses the complete TAR stream.
A regular Zstandard frame starts with the bytes 28 B5 2F FD. Checking that signature is more reliable than trusting the suffix, although a decoder must still validate the complete stream.1
backup.tar.zst to backup.tar does not decompress it. Renaming another file to .zst does not convert its contents either.How do I open a .zst on my computer?
Install the reference zstd command on Windows, macOS, or Linux, then decompress while keeping the input:
zstd -dk report.csv.zst
You can first test the compressed stream with zstd --test report.csv.zst. The unzstd command is equivalent to zstd -d, while zstdcat writes decompressed data to standard output.2
For a TAR archive compressed with Zstandard, GNU tar can list or extract the members:
tar --zstd -tf backup.tar.zst
tar --zstd -xf backup.tar.zst
GNU tar recognizes both .zst and .tzst when automatic compression selection is enabled.3 The decompressed result may be a document, database, disk image, TAR archive, or any other file type, so use an appropriate app for that result.
Poly support for .zst
Poly recognizes .zst as Zstandard-compressed data. It stores, syncs, shares, versions, and finds the file by name, but treats the compressed payload as opaque. Poly does not decompress it, preview archive members, index the expanded content, or send that content to the Poly agent.
Download and decompress the file with a trusted utility. If you then add the expanded file to Poly, it can receive the preview, indexing, and agent features available for its own format.
History of .zst
Yann Collet developed Zstandard at Facebook for fast, general-purpose lossless compression. Facebook announced the stable 1.0 release on August 31, 2016.4 RFC 8478 documented the format in 2018, and RFC 8878 replaced it in 2021. The newer RFC registers .zst, application/zstd, the zstd HTTP content coding, and the +zstd structured syntax suffix.1
The name does not imply that RFC 8878 is an Internet Standards Track specification. The RFC is Informational, while the media type and filename extension are registered for common use.
Working with .zst and alternatives
Choose the surrounding format based on the job:
| Format | Best fit |
|---|---|
.zst | Fast, tunable compression of one byte stream |
.tar plus Zstandard | Multiple files with Unix-style metadata |
.gz | Broad compatibility with older Unix workflows |
.xz | Strong compression where slower processing is acceptable |
.zip | Widely supported multi-file archives |
Zstandard's ordinary CLI compression levels run from 1 through 19; --ultra enables levels 20 through 22 at greater memory cost.2 Test representative data rather than assuming one level or codec will always be smallest.
Compressed data may expand dramatically. Apply size, time, and memory limits to untrusted inputs, and inspect TAR member paths before extraction. A valid optional Zstandard checksum detects corruption, but it does not establish that the expanded content is safe.1
Footnotes
- Internet Engineering Task Force. RFC 8878: Zstandard Compression and the
application/zstdMedia Type. The RFC defines the format, registered extension and media type, frame signature, optional checksum, and security considerations. ↩ ↩2 ↩3 ↩4 - Meta Platforms. Zstandard Command-Line Interface Manual. The manual documents decompression, integrity testing, command aliases, and compression levels. ↩ ↩2
- Free Software Foundation. GNU tar Manual: Creating and Reading Compressed Archives. GNU tar documents its Zstandard filter and recognized suffixes. ↩
- Meta Engineering. Smaller and Faster Data Compression with Zstandard. The release announcement describes Zstandard 1.0, its author, and its design goals. ↩