ZIP Inspector
Read a ZIP archive's central directory: entry names, compression methods, sizes and CRC-32, without extracting anything.
What the ZIP Inspector does
A ZIP ends with an end-of-central-directory record that says how many entries there are and where the central directory starts. This page finds that record by searching backwards from the end — it can be up to 65557 bytes back because of a trailing comment — and then reads one fixed-size header per entry.
Because the sizes come from the index rather than from inflating the data, a 2 GB archive is inspected as fast as a 2 KB one: only the tail and the directory are read.
This is an inspector, not an extractor: it never inflates an entry, so it cannot tell you whether the compressed data is intact — the CRC-32 shown is the value the directory declares. ZIP64 archives are refused by name because their 64-bit fields live in a different record this page does not read.
How to use it
Choose the ZIP file from the ZIP file picker.
Press Run and read the Entry table: one row per entry with its name, compression method, compressed and uncompressed size, and CRC-32.
Check the totals under the Entry table — Uncompressed and compressed byte counts — and remember no file was extracted.
Worked example
Input:
(application/zip fixture, about 237 bytes)
Output:
Entries: 2
name method compressed uncompressed crc-32
readme.txt stored 5 5 3610a686
nested/data.bin deflate 7 7 8dbf08ee
Uncompressed: 12 bytes; compressed: 12 bytes.
No entry was extracted: this page reads the central directory and nothing else.
Why it runs in your browser
The result is produced on this page with JavaScript, so it works offline after the page loads and nothing you enter is sent anywhere.
What is inside a ZIP, read from the archive's own index: every entry's name, compression method, compressed and uncompressed size, and CRC-32.
The archive is not opened and no entry is decompressed. The end-of-central-directory record is found, the central directory is walked, and the table is printed from what it declares.
What it does, and what it does not
A ZIP ends with an end-of-central-directory record that says how many entries there are and where the central directory starts. This page finds that record by searching backwards from the end — it can be up to 65557 bytes back because of a trailing comment — and then reads one fixed-size header per entry.
Because the sizes come from the index rather than from inflating the data, a 2 GB archive is inspected as fast as a 2 KB one: only the tail and the directory are read.
This is an inspector, not an extractor: it never inflates an entry, so it cannot tell you whether the compressed data is intact — the CRC-32 shown is the value the directory declares. ZIP64 archives are refused by name because their 64-bit fields live in a different record this page does not read.
How to use ZIP Inspector
Choose the ZIP file from the ZIP file picker.
Press Run and read the Entry table: one row per entry with its name, compression method, compressed and uncompressed size, and CRC-32.
Check the totals under the Entry table — Uncompressed and compressed byte counts — and remember no file was extracted.
What to Expect
Best for
- Checking what is inside an archive before opening it
- Confirming an entry's name or size
- Spotting which entries are stored rather than deflated
Not ideal for
- Extracting files, which this page never does
- Verifying that the compressed data matches its CRC, which needs a real unzip
- ZIP64 archives, which are refused by name
What this tool keeps
- Entry order as the central directory declares it
- The compression method number, named when it is a known one
- The declared CRC-32 in lower-case hex
What may need cleanup
- Re-save a ZIP64 archive without ZIP64
- Look up a method number this page does not name
Common errors
- The page refuses it: no end-of-central-directory record
Example use cases
- Auditing an archive before extraction
- Checking a build artifact's contents
- Confirming a file made it into a package
Sample input
ZIP file: (application/zip fixture, about 237 bytes)
Sample output
Entry table: Entries: 2 …
Who this is for
- Developers checking a release archive
- Anyone who wants to see a ZIP's contents without unpacking it
Frequently asked questions
Does it extract the files?
No. The page reads the central directory and nothing else, so an entry's data is never decompressed and never written. The CRC-32 column is the value the archive declares, not one this page computed.
Why is my archive refused as truncated?
The end-of-central-directory record was not found in the last 65557 bytes. That happens to a partial download, a file that is not a ZIP at all, and an archive whose tail was cut — the refusal names the missing record.
What is the difference between compressed and uncompressed size?
The central directory stores both. A stored entry has identical numbers because nothing was compressed; a deflate entry's compressed size is what it occupies in the archive and the uncompressed size is what it becomes.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.