Your files never leave this device — 100% in-browser

Extract ZIP Archives

Open a ZIP, see every file, download the ones you need — extracted on your device with integrity checks.

Drop a .zip and get a per-file download list — no "upload your archive" step, no waiting for a server. Every file is CRC-verified during extraction, and file names written by Korean Windows tools (알집, 반디집, Explorer) decode correctly as EUC-KR instead of turning into ûñ¬ garbage.

Last verified 2026-08-15 — this tool passed 79 automated end-to-end checks

⇪

Drop a .zip archive here, or click to browse

converts to extract · per-file downloads · CRC verified · EUC-KR names OK

01 — THE 한글 FILE NAME FIX

ZIPs from Korean Windows store names as EUC-KR without declaring it; macOS and most web tools show mojibake. This reader detects and decodes them correctly.

02 — INTEGRITY CHECKED

Every extracted file is verified against the CRC-32 the archive recorded — corrupt downloads fail loudly instead of silently.

03 — PICK, DON'T SPRAY

Each file gets its own download link — take the one document you need without writing 200 files to disk.

How to use

Drop your file(s) into the box above — or click it to browse.
Conversion starts immediately — no settings needed.
Click Download on each finished file — or Download all (.zip) for a batch. Nothing was uploaded at any point.

Why a browser unzipper exists at all

Two situations: a device without an unzip tool at hand (locked-down work machines, tablets, someone else's computer) — and the more interesting one, archives you don't fully trust. Extracting in the browser sandbox lets you inspect names and pull out single files without handing the archive to a website's server or running desktop software against it. The reader is our own implementation: central directory parsing, deflate-raw decompression through the browser's native engine, and a CRC-32 check on every file.

The Korean file-name problem deserves its own mention: ZIP predates Unicode, and Korean Windows tools still write names in EUC-KR without the UTF-8 flag. Tools that assume UTF-8 (macOS Archive Utility included) show Æ÷Æ®Æúž where 포트폴리오.pdf should be. This reader tries UTF-8 strictly, then EUC-KR, then Latin — so both modern and legacy archives come out readable.

Extraction behavior
Property	Behavior
Formats	.zip — stored (0) and deflate (8) entries
Integrity	CRC-32 verified per file
Names	UTF-8 flag honored; fallback UTF-8 → EUC-KR → Latin
Encrypted / ZIP64	Rejected with a clear message
Limit	200 MB per archive

Honest limits

Password-protected ZIPs are rejected — encryption support (and password cracking) is deliberately out of scope.
ZIP64 (4 GB+/65k+ entries) not yet — the practical browser limit is the 200 MB cap anyway.
Other archive formats — RAR and 7z use different (and for RAR, proprietary) formats; this tool is ZIP only.

Frequently asked questions

Why do my Korean file names finally look right here?

The reader detects the actual encoding instead of assuming UTF-8. Korean Windows tools write EUC-KR names without a flag; we try strict UTF-8 first, then EUC-KR — the mojibake path never triggers for valid archives.

Can it open password-protected ZIPs?

No — encrypted archives are rejected with a clear message. Decrypt with the tool that created them; password recovery is deliberately not offered.

Is the archive uploaded?

No — parsing and decompression run in your browser (the decompressor is the browser's own native engine). The network tab shows zero upload traffic.