ZIP, TAR and archive passwords
Pick the container that matches the handoff. Check what a password protects before you send the file.
Free toolZIP ToolsCreate and open ZIP, TAR and TAR.GZ archives. Review files before converting, encrypting or removing a known password.Open ZIP toolsThe short answer
Use ZIP for a familiar bundle. Use TAR when a Unix tool expects an uncompressed tar archive. Use TAR.GZ when that TAR stream should be gzip-compressed. Use an encrypted ZIP when the recipient has an AES-compatible archive program.
The ZIP tools workspace reads supported archives locally, shows the file paths before extraction and lets you select what the next archive should contain.
What changes between ZIP, TAR and TAR.GZ?
| Format | What it does | Good fit | Limit |
|---|---|---|---|
| ZIP | Stores files with separate per-entry compression and a central directory. | General sharing, Windows, macOS and browser downloads. | Encrypted filenames are not normally hidden. AES support differs between built-in tools. |
| TAR | Concatenates file records into one uncompressed archive stream. | Unix packages, source bundles and workflows that expect tar. | Does not compress by itself. Metadata support depends on the writer. |
| TAR.GZ | Wraps a TAR stream in gzip compression. | Source releases, Linux tools and compressed tarballs. | Not the same structure as a ZIP. Gzip has no ZIP-style password field. |
What a ZIP password protects
A ZIP password is an encryption key for file data. AES-256 makes the content unreadable without the key when implemented correctly. File names, paths, counts and other directory details can remain visible, so a password does not turn the archive into an invisible box.
Send the archive and its password through different channels. A long, unique password helps. The browser tool does not save the password to an account or local storage, and it cannot recover a forgotten one.
Why some built-in extractors fail
ZIP is a family of features rather than one identical encryption mode. Some operating-system archive views open ordinary Deflate ZIPs but reject WinZip AES. Use an AES-compatible tool such as 7-Zip or Keka when the recipient cannot open the file.
WinZip’s encryption notes distinguish protected contents from visible entry names and metadata. Encryption compatibility is a format question, not a reason to promise that every built-in extractor will work.
Conversion changes the archive structure
Renaming archive.zip to archive.tar does not convert it. ZIP headers and TAR headers are different. A converter must read the entries and write new headers, padding and metadata.
Regular file bytes and relative paths can carry across a supported conversion. Unix ownership, executable permissions, links, device records, ZIP comments and other archive-specific metadata need a purpose-built desktop workflow. A small compressed input can also become larger after conversion. Compression is a property of the data, not a promise attached to an extension.
Browser or desktop?
| Need | Browser workspace | Desktop archiver |
|---|---|---|
| A few ordinary files | Quick. Nothing is uploaded. Search and select before saving. | Works, but needs an installed app or file manager flow. |
| RAR, 7z, split archives | Not supported here. | Use a tool such as 7-Zip or The Unarchiver. |
| Very large archives | Browser memory and the stated 250 MiB input and 500 MiB expanded limits apply. | Better suited to long-running and large jobs. |
| System backups and permissions | Regular files only. It does not recreate a Unix filesystem. | Use a backup-aware archiver that preserves the metadata you need. |
A measured compression example
On 15 October 2026, we packed one synthetic text file containing 180,000 bytes. The repeating sentence makes it compressible on purpose. These results explain the formats; they do not predict a photo folder.
| Output | Setting | Result bytes |
|---|---|---|
| ZIP | Store | 180,152 |
| ZIP | Fast, level 1 | 1,067 |
| ZIP | Balanced, level 6 | 628 |
| ZIP | Smaller, level 9 | 628 |
| TAR | No compression | 181,760 |
| TAR.GZ | Native gzip default | 561 |
Method: Node 24.18.0 on macOS 27.0.1 ran the same archive engine used by this tool, with zip.js 2.23.0. The file was repeat.txt, containing 'compressible data\n'.repeat(10000). No password was set. The fixed timestamp was 1,700,000,000,000 milliseconds. Run node scripts/check-archives.mjs from the source repository to repeat the format checks. This is a small engine example, not a browser speed benchmark.
The stored ZIP and plain TAR grew because their headers take space. Levels 6 and 9 produced the same ZIP size. A higher setting does not guarantee a smaller file. JPEGs, MP4s and already compressed data can give much less saving.
Use your operating system when it already does the job
Windows
In File Explorer, select your files and use its compression option to create a ZIP. For an ordinary ZIP, open it and choose Extract All. Microsoft’s ZIP and unzip instructions explain the built-in workflow. They also state that Windows 11 24H2 does not support operations on encrypted archives. Use a compatible archive app for those.
Mac
In Finder, select your files, Control-click and choose Compress. Double-click an ordinary ZIP to expand it. Apple documents the steps in its ZIP and unzip guide. For AES ZIP encryption, use a compatible app rather than assuming Archive Utility will open it.
Linux and command-line workflows
For a regular folder, tar -czf archive.tar.gz folder/ creates a compressed tarball. Inspect it with tar -tzf archive.tar.gz before extracting into a new folder. A desktop or command-line archiver is better when permissions and special entries must survive.
What to check before you save
- Search the file list and confirm the folder paths.
- Check the selected count and expanded size.
- Choose the output format the receiving program expects.
- For encryption, confirm the recipient can open AES ZIPs.
- Keep the original until you have opened the saved copy.
What this guide will not promise
It will not promise a smaller archive for every input, a password recovery service, perfect system metadata preservation or support for every archive format. Those limits are why the workspace names the formats it accepts and reports the result it actually built.