ZIP File Viewer

View contents of a ZIP file online without extracting.

About ZIP Viewer Online

Drop an archive and you get its table of contents: every entry, with its full stored path, a folder or file marker, and the modification date the archive recorded. Directories are listed first. Nothing is decompressed, nothing is extracted to disk, and nothing is uploaded.

Reading the index, not the contents

A ZIP file keeps an index called the central directory at the very end, listing every entry and where its data begins. That design is why an archiver can show you the contents of a large archive instantly: it reads the index and never touches the compressed payloads. This viewer does the same thing. The consequence worth understanding is that the listing describes what the archive claims to contain — the entry names and dates are metadata, and no byte of any compressed file is decoded, checked against its stored checksum, or run.

Why look before extracting

Almost every archive-related security problem happens during extraction rather than during reading. A listing lets you spot the classic warning signs first: an entry whose path climbs out of the destination folder with parent-directory segments, an installer or script hiding behind a double extension, a single entry that expands to an implausible size, or thousands of entries where you expected a handful. Checking takes a second and costs nothing, because the names alone cannot do anything to your machine.

ZIP is more common than the extension suggests

A surprising amount of everyday software ships inside ZIP containers under other names. Word, Excel and PowerPoint documents are ZIPs full of XML; Java JARs and Android APKs are ZIPs of class files and resources; EPUB books, browser extensions and many plugin bundles are the same. The reader handles all of them, but the file picker does not: it accepts only .zip, .rar and .7z, and anything else is dropped without a listing and without an error. Duplicate the file, rename the copy to .zip, and it opens. That is a fast way to confirm a document is structurally intact rather than corrupt, to see which fonts or images a deck is dragging around, or to check what a downloaded bundle actually contains before installing it.

Limits worth knowing before you start

The picker offers .rar and .7z but the reader understands only ZIP, so those formats fail with the same message as a corrupt file. Encrypted archives cannot be listed at all — there is no decryption support, so a password-protected ZIP is rejected outright rather than showing names with contents withheld. Sizes are not displayed. And because the entire file is loaded into memory before the index is parsed, the ceiling is your available RAM rather than a configured limit; a multi-gigabyte archive may simply exhaust the tab.

About those timestamps

The dates come from ZIP's original MS-DOS timestamp field, which resolves to two seconds and carries no timezone. An archive built in another country therefore records a wall-clock time with no indication of which clock, so a date can appear a day off either side of what you expect. Use them to order entries and to spot an obviously stale file; do not use them as evidence of when something was created.

Index Only, Nothing Executed

The archive index is parsed and rendered while every compressed payload is left untouched — not decoded, not written to disk, not run. Inspecting an untrusted download is therefore risk-free in a way extracting it is not.

Never Leaves Your Machine

The ZIP reader is a JavaScript library running in this tab, so an archive full of client documents or internal source can be inspected without an upload, an account or a temporary copy on someone else’s server.

Disguised ZIPs, After A Rename

Office documents, JARs, APKs and EPUBs are ZIP containers wearing another extension. The picker only takes .zip, .rar and .7z, so copy one and change the extension to .zip and its internal structure lists like any other archive.

Frequently Asked Questions

Does the archive get uploaded?

No. The file is handed to a JavaScript ZIP library inside this tab, which reads the archive's central directory — the index at the end of the file that lists every entry — and renders it. No request is made and nothing is stored, so you can inspect an archive containing confidential material without it leaving the machine.

What exactly does the listing show me?

One row per entry, in the archive's own order with directories floated to the top. Each row gives the full path as stored, a folder or file icon, and the modification date, and the header above the list gives the total number of entries, counting folders. Sizes and compression ratios are not shown, and neither is the content of any file — this is an index of what the archive holds, not a preview of it.

Can I extract or preview a file from inside?

No — this lists the contents and stops there. That restraint is the point: nothing inside the archive is decompressed, opened, rendered or executed, so a malicious archive has no opportunity to do anything. Once you know what is inside and you trust it, extract with your operating system's own tools.

It accepted my .rar file and then said it was invalid.

The file picker lists .rar and .7z alongside .zip, but the reader only understands the ZIP format. RAR and 7z are entirely different container formats with different compression, so they fail as soon as the reader looks for a ZIP central directory. Use the archiver that created them, or repack as ZIP.

Can I inspect a .docx, .jar or .epub?

Yes, but only after renaming a copy to end in .zip. Those formats are ZIP archives holding XML, class files or assets, so the reader handles them perfectly well — the obstacle is the file picker, which accepts .zip, .rar and .7z and silently ignores everything else. Dropping a .docx straight in produces no listing and no error message, which looks like a broken page rather than a rejected file. Duplicate the document, change the extension, and it lists normally.

My password-protected ZIP will not open.

Encrypted archives cannot be listed here. The reader has no decryption support at all, so it fails on the archive as a whole rather than showing names and hiding contents. You will get the same message as for a corrupt file, which is worth remembering when diagnosing: the error cannot distinguish between encrypted and damaged.

How large an archive can it handle?

There is no coded limit, but the whole file is read into memory before parsing, so the practical ceiling is your available RAM and the browser's own allocation cap — usually somewhere in the low gigabytes on desktop and much less on a phone. A very large archive will make the tab unresponsive while it loads, or fail outright with an out-of-memory error.

Why is only a date shown, and why is it sometimes a day out?

Each row carries the calendar date alone, formatted for your locale — there is no clock time in the listing. The underlying field is ZIP's original MS-DOS timestamp, which has two-second resolution and stores no timezone at all, so an archive created in another region records a wall-clock time with no record of which wall it came off. That is why an entry can land a day either side of what you expect. Treat the dates as approximate ordering information, never as evidence.

Why is inspecting first safer than just extracting?

Because extraction is where archive attacks land. A listing reveals a path traversal attempt — entries whose names climb out of the target directory — an executable disguised with a double extension, or an implausible number of entries suggesting a decompression bomb. Reading the names costs nothing and rules all of that out before you commit.