Extract and browse ZIP archive contents in the browser with selective file download.
Every ZIP file ends with a table of contents: a central directory recording each entry's name, size, and compression method. This tool reads that directory in your browser, shows the archive as a browsable folder tree, and downloads only the entries you select, with no unzip tool and no server involved. The surprise for most people: the archive is never uploaded, and no folder materializes on your disk. Each chosen file is simply downloaded as-is. For unpacking everything, your operating system's own archive tool is the better fit; this tool is for reaching in and pulling out specific files.
A concrete input and expected output from the current implementation.
Input
A ZIP file named summer-2026.zip containing three entries: docs/readme.txt (Deflate, 6,144 bytes uncompressed), assets/logo.svg (Stored, 12,480 bytes), photos/cat.jpg (Deflate, 352,256 bytes).
Expected output
Entry list rendered by the tool: docs/readme.txt - Deflate - 1,864 B compressed / 6,144 B assets/logo.svg - Stored - 12,480 B / 12,480 B photos/cat.jpg - Deflate - 348,112 B / 352,256 B Archive total: 362,456 B compressed / 370,880 B uncompressed
The listing is read from the archive's central directory, which records both size fields per entry, so the totals are exact sums of the entries. The numbers also reflect the format: text deflates to roughly a third of its size, while JPEG data is already compressed and shrinks by barely one percent.
A ZIP archive is a container: file data sits near the front, and a central directory near the end lists every entry with its name, compression method, both sizes, and CRC-32 checksum. The tool locates the End of Central Directory record, reads that table, and renders the archive as a folder tree. Because the listing comes from the directory alone, browsing is instant even for archives with thousands of files.
Entries are compressed independently, so downloading one file touches only that entry's bytes. The tool uses the entry's offset, recorded in the central directory, to reach its compressed data, decompresses it in the browser, and offers the result as a download; nothing else is touched and nothing is uploaded. Stored entries (method 0) pass through unchanged. Rarer methods, such as BZIP2, LZMA, or Deflate64, cannot be decompressed by a browser, so those entries fail at download time.
No. The archive is read and decompressed entirely in your browser, and nothing is uploaded anywhere, so the file and its contents never leave your device. The processing happens locally on your machine; the tool does not need a server to do any of the work.
Not as a real folder. Browsers cannot write real folders to your disk, so extracting everything here would mean downloading entries one by one. That selective workflow is the tool's purpose. If you need the whole archive unpacked in place, your operating system's built-in archive tool (double-click the ZIP) is the better path.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Convert CSV data into structured JSON arrays or objects with automatic type detection.
Transform JSON arrays and objects into downloadable CSV spreadsheet format.
Convert YAML configuration files to JSON format with validation and formatting.
Parse XML documents and convert them to equivalent JSON structure with attributes.
Convert tab-separated values to comma-separated format with proper escaping.
Convert numbers between binary, octal, decimal, and hexadecimal bases.