Skip to content
Back to Blog
informational

What Is 7Z? The High-Compression Archive Format

2026-05-17 8 min read

What 7Z Actually Is

7Z (written as .7z) is an open-source archive format created by Igor Pavlov and first released in 1999 as part of the 7-Zip project. Unlike ZIP or RAR, which were designed primarily for convenience and broad compatibility, 7Z was engineered from the ground up for maximum compression. The format supports multiple compression algorithms — most notably LZMA and LZMA2 — that routinely shrink files 30–70% smaller than a standard ZIP archive of the same content. The '7' in the name comes from 7-Zip version 0.07, the first public release that supported the format. Since then, the specification has been published openly, which is why tools like PeaZip, WinRAR, macOS Archive Utility, and dozens of command-line utilities can all read and write .7z files without licensing fees. At its core, a .7z file is a container. It stores one or more files along with metadata (filenames, timestamps, attributes) and a compressed data stream. The format also supports solid compression, which means multiple files are compressed together as a single block rather than individually. Solid compression is the main reason 7Z beats ZIP so decisively on folders full of similar files — think a directory of HTML files, source code, or log files where repeated patterns span across many individual documents.

How 7Z Compression Works: LZMA and LZMA2 Explained

The secret to 7Z's compression ratios is the Lempel–Ziv–Markov chain Algorithm, or LZMA. It belongs to the LZ77 family of algorithms but extends them with a range encoder (instead of Huffman coding used by ZIP's DEFLATE) and a much larger dictionary size. In practical terms, dictionary size matters enormously. ZIP's DEFLATE uses a 32 KB dictionary. LZMA defaults to a 16 MB dictionary and can be pushed to 1 GB or more. A larger dictionary means the compressor can find matches further back in the data stream, which dramatically improves ratios on large, repetitive files. Compressing a 500 MB SQL database dump, for example, might yield a 120 MB ZIP but an 80 MB 7Z — a difference that matters when you're paying for cloud storage or sending files over a slow connection. LZMA2 (the default algorithm in modern 7-Zip) adds multi-threading support on top of LZMA. On a quad-core machine, LZMA2 can compress roughly 2–4× faster than LZMA with only a marginal reduction in ratio. You can control this in 7-Zip's GUI under Add to Archive → Compression Method → LZMA2, and set the number of CPU threads explicitly. Beyond LZMA/LZMA2, 7Z also supports BZip2, PPMd (excellent for plain text), and Deflate as fallback algorithms, as well as a Delta filter useful for WAV audio and bitmap images. This flexibility makes .7z a reasonable choice even in edge cases where LZMA isn't optimal.

7Z vs. ZIP vs. RAR: A Realistic Comparison

Choosing between archive formats is mostly about trade-offs between compression ratio, speed, compatibility, and features. Here is how the three most common formats stack up honestly. Compression ratio: On a mixed folder of office documents, source code, and text files, 7Z with LZMA2 typically achieves 60–65% size reduction. ZIP with DEFLATE usually lands around 45–50% on the same content. RAR5 falls somewhere in between, often 55–60%. The gap widens significantly on homogeneous data like log files or XML exports. Speed: 7Z is slower to compress than ZIP because LZMA is computationally expensive. Decompression, however, is fast — comparable to ZIP. If you're archiving a folder once and distributing it many times, the compression cost is paid once. If you need to rapidly archive rotating log files every few minutes, ZIP or even gzip may be more practical. Compatibility: ZIP is universally supported — Windows Explorer, macOS Finder, iOS Files, Android — without any additional software. RAR requires WinRAR or a compatible tool to create archives, though most platforms can extract it. 7Z is well-supported on desktop operating systems but can cause friction on mobile devices and older enterprise systems where 7-Zip hasn't been installed. Features: 7Z supports AES-256 encryption (including encrypting filenames, which ZIP does not do by default), archive splitting, and solid compression. RAR adds recovery records that can repair a damaged archive — something 7Z does not support natively. ZIP lacks filename encryption and solid compression but wins on raw ubiquity. The bottom line: use 7Z when compression ratio is the priority and the recipient can install 7-Zip. Use ZIP when compatibility is non-negotiable.

When to Use 7Z (and When Not To)

7Z earns its place in specific workflows. Archiving large software releases, backing up source code repositories, distributing game mods, or sending bulk document exports over bandwidth-limited connections are all cases where the extra compression pays off. A game mod that would be 800 MB as a ZIP might compress to 520 MB as a 7Z — a meaningful difference for users on metered connections. Solid archives are particularly effective when the files being compressed share similar content. A folder of 10,000 small JavaScript files will compress far better in solid mode than individually, because LZMA can reference patterns across all of them. In 7-Zip's GUI, solid block size is set under Add to Archive → Advanced → Solid block size. The default 'Solid' setting is usually fine; you only need to reduce it if you plan to extract individual files frequently from a very large archive, since solid archives require decompressing from the start of the block. Where 7Z is a poor choice: already-compressed files. Trying to re-compress MP4 videos, JPEG images, or MP3 audio into a 7Z archive will produce a result that is barely smaller — sometimes even slightly larger — than the originals, while taking significant CPU time. The same is true for files already stored in compressed formats like DOCX, XLSX, or EPUB (all of which are ZIP-based internally). Another honest caveat: if you're sending files to someone who isn't technically confident, a .7z attachment may cause confusion. Many corporate email gateways also block .7z attachments by policy, treating them the same as .exe files. In those scenarios, ZIP remains the safer choice regardless of its compression inferiority.

Encryption and Security in 7Z Archives

7Z supports AES-256 encryption, which is the same standard used by financial institutions and government agencies. When you set a password on a .7z archive in 7-Zip (Add to Archive → Encryption → Enter password), the file contents are encrypted with AES-256 in CBC mode. Crucially, if you also check 'Encrypt file names', the directory listing inside the archive is encrypted too — an attacker who intercepts the file cannot even see what files are inside without the password. ZIP's built-in encryption (ZipCrypto) is notoriously weak and has been broken for decades. Even AES-256 encrypted ZIP files expose filenames. This makes 7Z the better choice when you genuinely need to protect sensitive data in an archive. That said, encryption strength is only as good as the password. A dictionary-attackable password like 'password123' renders AES-256 meaningless. Use a randomly generated passphrase of at least 16 characters. 7-Zip does not enforce password strength, so that responsibility falls entirely on the user. One limitation worth noting: 7Z archives do not support digital signatures or integrity certificates. If you need to prove the archive hasn't been tampered with, you'll need to generate a separate checksum (SHA-256 is standard) and distribute it alongside the archive. Tools like CertUtil on Windows (certutil -hashfile archive.7z SHA256) or shasum -a 256 on macOS/Linux handle this in seconds.

Converting and Extracting 7Z Files with CocoConvert

CocoConvert can handle common 7Z conversion tasks directly in your browser without installing software. You can upload a .7z archive and extract its contents, or convert files into a .7z archive from formats like ZIP, TAR, GZ, and RAR. The process is straightforward: upload your source file, select the target format, and download the result. For most everyday use cases — converting a .zip you received into a .7z for more compact storage, or extracting a .7z someone sent you without installing 7-Zip — CocoConvert covers the ground well. File size limits apply (currently up to 2 GB per upload), and conversion happens on secure servers with files deleted automatically after one hour. It's worth being transparent about what CocoConvert cannot do. Fine-grained control over compression settings — dictionary size, solid block configuration, thread count, word size — is not available through the web interface. If you need to squeeze every last kilobyte out of a large archive or configure split volumes for DVD distribution, you'll want the 7-Zip desktop application (free, available at 7-zip.org) or a command-line tool like p7zip on Linux. CocoConvert is built for convenience, not for power users who need to tune LZMA parameters. Similarly, CocoConvert does not currently support creating password-protected 7Z archives. If encryption is a requirement, use 7-Zip locally. Handling encrypted archives for extraction is also not supported — you'll need to decrypt locally before uploading. These are deliberate limitations related to handling sensitive credentials on a third-party server, not technical oversights.

Practical Tips for Working with 7Z Files

A few concrete practices will save you headaches when working with .7z archives regularly. Choose compression level deliberately. 7-Zip offers levels from Store (0, no compression) to Ultra (9). For most use cases, Normal (5) or Maximum (7) is the right balance. Ultra takes significantly longer and typically only improves ratios by 3–5% over Maximum — rarely worth it unless you're distributing a file to thousands of users and every megabyte counts. Use split archives for large distributions. If you need to send a 4 GB archive via a service that caps uploads at 2 GB, 7-Zip can split it automatically. In the GUI: Add to Archive → Split to volumes, bytes → enter '2000m' for 2,000 MB parts. The recipient reassembles by opening the first part (.7z.001) in 7-Zip. Test your archives before deleting originals. 7-Zip's Test Archive function (right-click → 7-Zip → Test Archive) verifies the CRC checksums of every file without extracting. This takes seconds and confirms the archive is intact. It's a habit worth building before you delete the source files. Be careful with very long file paths on Windows. 7Z archives created on Linux can contain paths longer than Windows' default 260-character limit. Extracting such archives on Windows 10 or 11 requires enabling long path support in Group Policy or the Registry (HKLM\SYSTEM\CurrentControlSet\Control\FileSystem → LongPathsEnabled = 1), or using 7-Zip 22.00 or later which handles this automatically when the setting is active. Finally, keep 7-Zip updated. The project releases security patches periodically, and older versions have had vulnerabilities related to malformed archive parsing. The current stable release is always listed at 7-zip.org.