ZIP Viewer
Inspect any ZIP archive instantly: folder tree, sizes, compression ratios, methods, CRC-32, timestamps, encryption and ZIP64 status, plus advanced metadata for every entry. Only the archive index is read, so even huge archives open in a moment.
ZIP Viewer
Look inside an archive without extracting it. Only the index is read.
Drop a ZIP file to inspect
TAR, TAR.GZ and GZ work too
Files stay on your device. Nothing is uploaded.
How to use ZIP Viewer
- 1
Open a ZIP
Drop an archive or choose it with the file picker. Only the archive's index is read; no file inside is decompressed.
- 2
Browse the contents
Switch between a folder tree and a sortable, filterable table showing sizes, packed sizes, ratios and dates.
- 3
Open the details
Expand any entry for advanced metadata, or check the archive summary for totals, the comment, ZIP64 status and warnings.
- 4
Export the listing
Save the full entry list as CSV for a spreadsheet or JSON for scripts.
Why use Aback ZIP's ZIP Viewer?
Large archives open quickly
The viewer reads only the central directory, the index stored at the end of every ZIP. A large archive with a few hundred files lists about as quickly as a small one, because file contents are never decompressed.
Simple view, deep detail
Names, sizes and ratios up front. Method, CRC-32, flags, extra fields, host OS, Unix permissions and DOS attributes are a click away when you need them.
Warnings worth reading
Duplicate names, unsafe paths such as ../, overlapping entries, unusually high compression ratios and data prepended to the archive are all called out in plain language.
Handles huge entry counts
The table is virtualised, so archives with hundreds of thousands of entries stay scrollable. Filter and sort to find what you need, then export the list.
Common use cases
Check an attachment first
See exactly what a ZIP from a colleague or stranger contains before extracting anything, including files hidden several folders deep.
Verify a release build
Confirm a build artifact contains the files it should and nothing it shouldn't, such as .env, node_modules/ or source maps, and that scripts carry executable Unix permissions.
Diagnose extraction errors
When an extractor reports an unsupported method or a password prompt you didn't expect, the per-entry method and encryption columns show why.
Inventory a backup
List a large backup archive and export it to CSV to search, sort or keep as a record of what was archived and when.
Spot macOS clutter
Find __MACOSX/, .DS_Store and ._ files before sharing an archive with Windows users, then strip them with Clean ZIP.
Identify where an archive came from
“Version made by”, host OS, name encoding and prepended data reveal whether an archive came from Windows, macOS, a Linux tool or a self-extracting installer.
About ZIP Viewer
Why nothing needs to be extracted
Every ZIP ends with a central directory: an index recording each entry's name, sizes, CRC-32, compression method, timestamps and position in the file. The viewer reads only that index. It is fast, uses little memory, and never decompresses your files.
The CRC-32 values shown are the ones stored by the program that created the archive. Listing an archive does not prove its data is intact. To check every file, run Test ZIP Integrity.
Reading the columns
| Field | What it tells you |
|---|---|
| Size | The file's original, uncompressed size |
| Packed | How many bytes the file occupies inside the archive |
| Ratio | How much smaller the packed data is than the original |
| Method | How the data was compressed: Store (none), Deflate, or another method such as LZMA |
| CRC-32 | The checksum recorded for the uncompressed data |
| Encryption | None, ZipCrypto, or WinZip AES with its key size |
| ZIP64 | Whether 64-bit fields were needed for sizes, offsets or entry counts |
| Version made by / host OS | Which kind of system and ZIP version wrote the entry |
| Unix permissions / DOS attributes | File modes such as executable, and flags such as read-only or hidden |
| Extra fields | Additional metadata blocks, for example extended timestamps, Unicode paths or AES details |
| Name encoding | Whether the name is UTF-8 or a legacy code page such as CP437 |
What the warnings mean
- Duplicate names: two entries share a path, so extracting the archive can silently overwrite one with the other.
- Unsafe paths: an entry uses
../, an absolute path or a drive letter that could escape the extraction folder in careless tools. - Overlapping entries: entries share the same bytes, a technique used by some zip bombs.
- High ratio: an entry expands far more than normal data does, which can indicate a zip bomb.
- Prepended data: bytes sit before the ZIP data, typical of self-extracting
.exearchives.
Limitations
- Listing an archive doesn't verify its contents. The CRC-32 column shows stored values, not checked ones; use Test ZIP Integrity for that.
- The viewer needs a readable central directory. If it is missing or damaged, for example after an interrupted download, try Repair ZIP.
- TAR.GZ and TGZ archives have no index, so listing them means reading through the whole file, which takes longer than a ZIP.
- RAR and 7z archives are not supported. Very large archives still need enough browser memory for the listing, which can be an issue on low-memory phones.
Processing happens locally in your browser. Your files are not uploaded, and closing the tab discards everything.
Related tools
ZIP Viewer: frequently asked questions
No. The archive's index is read by your browser on your device and nothing is sent to a server. No account is needed, and the file itself is not modified.
Yes, that is exactly what the viewer does. It reads the archive's built-in index and shows every file and folder with sizes and dates, without decompressing anything.
Only partly. It reports structural problems it can see in the index, such as overlapping entries, duplicate names or unsafe paths. It does not decompress files, so it can't confirm the data is intact. Use Test ZIP Integrity to check every file's CRC-32.
Yes. ZIP encryption protects file contents but not the index, so names, sizes and dates are visible to anyone. The viewer shows which entries are encrypted and whether they use ZipCrypto or AES.
The original ZIP format can't describe files or archives larger than 4 GB, or more than 65,535 entries. ZIP64 is the extension that adds 64-bit fields for those cases. The viewer shows which entries and archive records use it.
They were stored without compression, or compression gained nothing. That is normal for JPEG, MP4, MP3, PDF and other formats that are already compressed, and many tools store them on purpose.
Yes. The table and tree are virtualised, so only the rows on screen are drawn. The full listing still has to fit in browser memory, which is rarely a problem on a computer but can be on older phones.
Yes. Export the listing as CSV to open in Excel, Numbers or Google Sheets, or as JSON for scripts. The export is created in your browser.