Reduce ZIP File Size

This tool targets a narrow but common problem: a ZIP that is larger than it needs to be because of weak compression and operating-system clutter. It fits best for archives of text, code, CSV, logs, SVGs and other uncompressed content that Deflate can still squeeze. If your archive was created by a tool that stored files without compression, or assembled on a Mac that scattered metadata throughout, recompressing at maximum level often trims a meaningful slice off the total.

Practical situations where it helps: getting a project archive under an email attachment ceiling, fitting a ZIP inside a web form's upload limit, tidying a build or source bundle before distribution, and cleaning a folder export before handing it to a colleague. The breakdown it shows first answers a separate question many people have when a ZIP feels too big: which files are actually driving the size, so you know whether the problem is the compression, one large asset, or the same file stored several times.

It is not the right tool for media-heavy archives. A ZIP full of photos, video, or MP3s is already near its floor, and you should expect little or no saving. For those, the realistic path is compressing the source files first with a dedicated image or video tool, then re-zipping.

You drop or select a single .zip file (up to 300 MB). The tool reads it in your browser and shows where the size is: the five largest files, the space each file type takes and its share of the total, and any sets of identical files with how much repeated content they hold. It also counts how many files are in formats that are already compressed. Nothing is sent anywhere, and it leaves no trace once the tab closes.

Press Reduce ZIP size and two things happen. First, recognized system junk is stripped out: .DS_Store, the __MACOSX folder, ._ files, Thumbs.db, and desktop.ini. Second, files that can still shrink are recompressed with Deflate at maximum level (9), while formats that are compressed already, such as JPG, PNG, MP4, MP3, PDF, Office documents, EPUBs and other archives, are copied across unchanged, since recompressing them only costs time. The result panel reports before size, after size, and the saving.

If the result is not smaller than the original, nothing is downloaded: the tool tells you the ZIP is already as small as it can make it and to keep the original. When it is smaller, <name>-optimized.zip downloads and a Download again button stays available. What it deliberately does not do: it does not re-encode images, audio, video, or PDFs, does not remove duplicate files by itself, does not repair damaged archives, and does not add or change passwords. File and folder structure inside the archive is preserved exactly.

The most common disappointment is a media-heavy archive. If most of the space is JPGs, videos or PDFs, the breakdown will show it, and the saving will be small or zero. That is not a fault; the data inside those files is compressed already.

A second pitfall is assuming the tool deduplicates or repairs. Identical copies of a file are listed but kept; use the Duplicate Finder or Remove Files from ZIP to drop them. Likewise, a damaged ZIP that will not open elsewhere will fail to load here with a message rather than being healed. Maximum-level recompression of a large text-heavy archive is also CPU-bound and runs entirely on your machine, so a 300 MB archive will take noticeably longer than a small one, especially on a phone or older laptop.

Finally, remember the output is a new file with an -optimized suffix; it does not overwrite your original. If your real goal was removing a specific big file rather than shaving compression, the breakdown tells you what to target with a different tool instead of optimizing repeatedly for diminishing returns.

Open the optimized ZIP and confirm the file count and folder structure match the original, minus the system junk. Spot-check a few files after extraction, particularly anything important: they should open exactly as before, since the tool repacks rather than alters files. If your reason for shrinking was a specific limit, an email cap or a form's maximum upload size, measure the new file against that limit directly rather than assuming the percentage cleared it.

For official or financial archives, extract the optimized ZIP, compare its file list with the original, and open the key documents before sending it.