Unzip Files
Pick one ZIP archive of up to 50 MB and get a list of everything inside, with each file ready to preview or download. The unzipping runs in your browser, so the archive never leaves your device.
How to use
- Choose a ZIP archive: Drop a .zip file onto the box or click to choose one. One archive at a time, up to 50 MB; to swap it for another, press ✕ on the file row first — that button is disabled while an extraction is running.
- Click Extract ZIP: The archive is decoded on your device. While it runs the button reads Extracting… and the page waits, because the work happens on your own processor rather than on a server.
- Preview and save the files: Each file appears with its full path inside the archive and its unzipped size. Use the numbered buttons to look at one, then Download it — or Download all to save them one after another.
How this ZIP extractor works
Nothing is uploaded. The page ships a small JavaScript ZIP decoder (fflate 0.8.3), reads the archive you picked straight from your disk into memory, and builds the file list there. No request carries your archive anywhere, and the preview and download links point at copies held in your browser's own memory. That makes it a reasonable place to open payslips, scanned IDs, client deliverables or anything else you would rather not hand to a web service.
ZIP is a container that allows many different compression methods, and this tool reads the two that matter in practice: stored (method 0, meaning the file was packed without compression) and Deflate (method 8). Those are what Windows File Explorer, macOS, 7-Zip and WinRAR produce by default, so ordinary archives open normally. An archive whose entries were packed with BZip2, LZMA or PPMd cannot be decoded here and is reported with the same message as a damaged file.
Three checks run before any data is expanded. First, the archive's central directory is read on its own — no decompression — to see whether any entry carries the encryption flag; if one does, you get the password notice instead of a pile of scrambled bytes. Second, while the decoder walks the entry list it adds up the sizes the archive declares and stops before allocating memory if the archive crosses one of four guardrails: more than 10,000 entries — folder entries included, even though they are never downloaded — a single file over 256 MB unzipped, more than 512 MB unzipped in total, or an entry that claims at least 10 MB and expands more than 200 times (the signature of a ZIP bomb). Entry names that point outside the extraction folder — paths starting with / or a drive letter, UNC paths, or any name with a path segment equal to .. — cause the whole archive to be refused. (A segment has to be exactly .., so an ordinary name such as report..txt is fine.)
Third, the entry names are compared with one another, because the decoder gathers the files it extracts under their full paths: two entries recorded under exactly the same path overwrite each other, and an entry named __proto__ at the root of the archive is swallowed entirely. Either way the list would come back one file short and nothing would say so, which is the one failure worth refusing outright — so an archive like that is stopped by name, with the path in question quoted in the message, and a list you do get back accounts for every file inside. Note that this is about identical full paths: two files called report.xlsx in different folders are separate entries and extract normally. To open an archive that was refused, use a desktop tool such as 7-Zip, WinRAR or Archive Utility — and when it asks what to do about the duplicate path, choose to rename the second copy or save each one separately rather than overwrite or skip, then check the extracted folder to confirm every entry is there.
What you get back, and what the archive loses
File contents come back byte for byte. Unzipping is restoration, not conversion: there is no re-encoding step, so a photo, a spreadsheet or an installer is bit-identical to what was packed. Whatever the file was before it went into the archive, that is exactly what you download.
The list shows each file's full path inside the archive, such as docs/notes.md, together with its unzipped size, so you can see the original folder structure at a glance. The summary line counts files only; folder entries are listed separately as skipped, because empty folders and folder markers contain nothing to download.
Folders are not rebuilt when you save. A browser can only write single files to your downloads, so docs/report.xlsx is saved as report.xlsx. The tool hands over that base name and nothing more, so when two different folders inside the archive hold a file with the same name, both downloads arrive under the same name and what happens next is your browser's decision: some add a number and keep both as report.xlsx and report(1).xlsx, others ask you what to do, and a share sheet on a phone may behave differently again. Check that prompt rather than assume the second file is safe, and if the folder structure matters, note the paths from the list before downloading, or unzip on a desktop instead.
File metadata does not survive either. The result is names and bytes, so modification dates, created dates and Unix permission bits are gone; the files you save carry the time you saved them. Finally, nothing is stored: the archive and the files extracted from it live only in the tab's memory, with no cookie and no local storage, and a refresh or a closed tab wipes them.
Limits, and when this is the wrong tool
One archive at a time, up to 50 MB, and only .zip. Larger files are stopped at the drop box with a size notice, and other file types are filtered out before anything happens. Because the archive expands in memory, peak usage is roughly the size of the archive plus the total unzipped size — a 50 MB archive of text or source code can expand to several hundred megabytes, which an older phone may not have free. The decoding also runs on the main thread, so the page stops responding until it finishes.
Password-protected archives are identified, not opened. The ZIP decoder this page uses (fflate) has no decryption step at all, and for the common ZipCrypto case the failure is silent rather than loud: in testing, a 15-byte file inside an encrypted archive came back as 27 bytes of scrambled data (a 12-byte header plus the ciphertext) with no error at all. Reading the encryption flag first and stopping is the honest outcome. Open the archive on your computer with 7-Zip, WinRAR or Archive Utility, type the password there, and work with the unpacked files.
RAR, 7Z, TAR and GZ are different formats and are not handled here, whatever their file name says. Split or multi-volume archives (.z01, .zip.001, .part1.rar) are also out of reach, because a browser only receives the single file you picked and cannot join volumes — feeding it one volume just produces a damaged-archive message. Truncated downloads and files that were never ZIPs in the first place get the same message.
There is no way to extract just one entry: the whole archive is decoded in one pass and then you choose what to save. And the tool only goes one way. It does not create or repack archives, cannot bundle the results into a new ZIP for a single download, and cannot repair a broken archive or re-read a file name in a different character encoding.
Unzipping on a phone, and previewing before you save
A typical phone situation: a ZIP arrives by email or chat, you need one document out of it, and the file manager on the device either has no extract option or will not open that archive. Tap the drop box, choose the archive from Files on an iPhone or Files by Google on Android, and extract. When you save a file, the browser is asked to hand it to the system share sheet — where that is supported you can store it in Files, send it on, or open it in another app; where it is not, the file simply downloads the usual way. Download all saves each file in turn, which on a phone can mean one save prompt per file, so for a large archive it is usually faster to pick the two or three files you actually need.
Previews cover the formats a browser can display on its own: images are shown inline, PDFs open in an embedded viewer, and an MP4 gets a video player — though a clip your browser cannot decode drops back to the download card. Anything else — a spreadsheet, a nested ZIP, an installer — shows the note that the format cannot be previewed here but can still be downloaded. The numbered buttons follow the same order as the file list above, so entry 7 in the list is button 7.
If file names look like nonsense, the archive is old rather than broken. Current archivers record names in UTF-8, which displays accented, Vietnamese or Spanish names correctly; archives written by older software stored names in a local code page such as GBK or Windows-1252, and those names cannot be recovered in the browser. This affects the names only — the file contents are still exact, so you can download a mis-named file and rename it yourself.
Frequently asked questions
- Is my ZIP file uploaded to a server?
- No. The archive is read from your disk and unzipped inside the browser tab, and the download links point to copies in your browser's memory. No request sends the archive anywhere. Closing or refreshing the tab clears the archive and the extracted files from the page's memory; files you saved yourself stay on your device.
- Can it open a password-protected ZIP file?
- No, it only tells you the archive has a password. The ZIP decoder behind this tool has no decryption step, so the archive is checked for the encryption flag and stopped. Open it on your computer with 7-Zip, WinRAR or Archive Utility and enter the password there.
- Can I extract RAR or 7Z files here?
- No. This tool reads ZIP archives only, and RAR, 7Z, TAR and GZ are different formats that need their own tools. Split ZIP volumes such as .z01 or .zip.001 are not supported either, because a browser can only read the one file you picked.
- What is the largest ZIP I can unzip?
- Up to 50 MB per archive, one archive at a time. The contents are also capped for safety: 10,000 entries, including folder entries, 256 MB for any single file, and 512 MB unzipped in total. An archive beyond any of those is refused rather than left to fill your memory.
- Why did it say my archive was blocked?
- It crossed one of the safety limits, each of which produces the same message. One possible cause is the compression-ratio check: an entry that declares at least 10 MB and expands more than 200 times is treated as a ZIP bomb and stopped before it is unpacked. The others are the caps on entry count (10,000, folder entries included), on a single unzipped file (256 MB) and on the unzipped total (512 MB).
- Why don't the folders appear when I download the files?
- Browsers can only save single files, so the folder path is dropped and docs/report.xlsx is saved as report.xlsx. Only that base name is passed on, so two same-named files from different folders are offered under the same name: your browser may number the second one report(1).xlsx, or ask you whether to replace the first. Read the prompt before confirming so nothing gets overwritten. The full paths stay visible in the list, so you can rebuild the structure yourself.
- Why are some file names garbled?
- The archive was created by older software that stored names in a local code page instead of UTF-8, and that cannot be undone in the browser. Only the names are affected — the file contents are byte-for-byte correct, so download the file and rename it.
- Does this work on iPhone and Android?
- Yes, in any modern mobile browser. Choose the ZIP from Files or Files by Google, extract, and save what you need: if your browser supports sharing files, the system share sheet opens, and if it doesn't, the file downloads as normal. Keep archives small on a phone: unzipping happens in memory, so a near-50 MB archive can be slow or fail on an older device.