Skip to content
Aback ZIP

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.

Processed locally

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. 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. 2

    Browse the contents

    Switch between a folder tree and a sortable, filterable table showing sizes, packed sizes, ratios and dates.

  3. 3

    Open the details

    Expand any entry for advanced metadata, or check the archive summary for totals, the comment, ZIP64 status and warnings.

  4. 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

FieldWhat it tells you
SizeThe file's original, uncompressed size
PackedHow many bytes the file occupies inside the archive
RatioHow much smaller the packed data is than the original
MethodHow the data was compressed: Store (none), Deflate, or another method such as LZMA
CRC-32The checksum recorded for the uncompressed data
EncryptionNone, ZipCrypto, or WinZip AES with its key size
ZIP64Whether 64-bit fields were needed for sizes, offsets or entry counts
Version made by / host OSWhich kind of system and ZIP version wrote the entry
Unix permissions / DOS attributesFile modes such as executable, and flags such as read-only or hidden
Extra fieldsAdditional metadata blocks, for example extended timestamps, Unicode paths or AES details
Name encodingWhether 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 .exe archives.

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.

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.