Standard ZIP output
The finished file opens in Windows Explorer, macOS Archive Utility, and other tools that read .zip archives.
Free / No sign-up / Local-only processing
Load an existing archive, choose a compression level, and rebuild it in this tab. Compare the real before-and-after size before you download.
Create a ZIP instead.
No uploads
Files stay in your tab.
Paths kept
Folders keep their structure.
Exact sizes
Measured from actual bytes.
Free to use
No account or quota.
How it works
Compressing a ZIP is a rebuild, not a rename. The browser reads the archive, verifies each entry in memory, and writes a fresh DEFLATE archive at the level you choose. There is no upload queue and no server copy.
Before
Folder inputMixed files and nested folders, exactly as they sit on disk.
After
ZIP archiveSame folder structure. One file, ready to share.
0 uploadsDrop a .zip onto the tool or choose it from your device. Entries are verified while the archive loads, before any compression starts.
Drag from Low (1) to Max (9). Max is the default, and every level produces a standard ZIP that opens in everyday ZIP tools.
Select Compress ZIP, then compare the input and output bytes. If rebuilding the archive makes it larger, the original ZIP stays available as the primary download.
Features
Most compressors ask you to upload a folder or install software. This one builds the archive in the browser, keeps the paths you expect, and reports the real result.
The finished file opens in Windows Explorer, macOS Archive Utility, and other tools that read .zip archives.
Nested files keep their relative folders instead of landing in one flat list.
Unpack and rebuild a ZIP at a new level. If the rebuilt archive is larger, the original stays available.
Savings are calculated from actual input and output sizes. No rounded-up claims about how much space you will save.
Compression runs in a Web Worker. Cancel stops the work without downloading a partial archive.
There is no file server and no analytics in the tool. The only network request is the page itself.
Use cases
Useful when a destination asks for one file, when relative paths matter, or when an existing archive needs a smaller rebuild. The work stays in your browser.

Rebuild a bloated ZIP at a higher level before attaching it to a message or sending it through a size-limited portal.

Revisit an archive that was built with a fast or store setting and rebuild it for long-term storage or handoff.

Some forms reject large files. A smaller archive can bring the upload under the cap without changing what is inside it.
Local processing protects where the files go, not whether you are allowed to share them. Only compress files you have permission to use.
Supported files
Add an existing ZIP. The archive is read as bytes and rebuilt with DEFLATE; nothing is opened or executed.
Reports, contracts, notes, and office files. Text-heavy documents usually shrink the most.
Images, audio, and video can be bundled, but most are already compressed and may barely shrink.
Source files, configs, and nested folders. Relative paths are kept inside the archive.
Guide
A real ZIP compressor rebuilds the archive instead of renaming it. This guide explains what happens inside, which files shrink, and how to read the result.
Open the compressor and add the archive you want to reduce. The file is read locally and every entry is checked before compression begins. Set the level from Low for a quick result to Max for the smallest possible output; Max (9) is the default. The result panel reports the original size, the rebuilt size, and the difference. If the rebuild is larger, the original stays available as the primary download, so a bad result never replaces a good file.
ZIP is a container, not a single algorithm. Each file inside is stored as a separate entry, usually compressed with DEFLATE. Rebuilding an existing ZIP means decompressing each entry and compressing it again at a new level. The container also stores names, relative paths, timestamps, and optional permissions. That is why a rebuilt archive can differ slightly even when the contents are identical: headers are new, and uncommon metadata from the original tool may not survive.
DEFLATE looks for repeated patterns. Text, source code, CSV, logs, and similar files usually contain plenty of repetition, so they shrink well. Images, video, audio, and archives that are already compressed have little repetition left.
The result panel compares bytes, not estimates. Input is the size of the ZIP you loaded; output is the size of the rebuilt archive. A positive difference means the rebuild is smaller. A negative difference means it grew, which can happen with small archives or files that were already compressed. When you compress an existing ZIP and the result is larger, the original file remains downloadable. A compressor should report what happened, not promise a saving that did not occur.
Plain text, Markdown, CSV, JSON, HTML, CSS, JavaScript, logs, and uncompressed documents usually shrink the most. JPEG, PNG, WebP, GIF, MP4, MP3, and other already-compressed formats may barely change. Very small archives, archives already rebuilt at Max, and folders dominated by media can even grow slightly.
Compression level matters most on text-heavy inputs. Moving from Low to Max can produce a noticeably smaller archive, but it takes longer. Mid levels are the usual compromise. A ZIP that is already compressed will still change by less than 1%, because DEFLATE has no repetition left to remove. No percentage is guaranteed; the result depends entirely on the bytes inside your archive.
The output is a standard ZIP with DEFLATE compression and no ZIP64 extension. It opens in Windows Explorer, macOS Archive Utility, 7-Zip, WinRAR, and most upload forms that accept .zip files. The tool accepts archives up to 1 GB, individual entries up to 512 MB, and 100,000 entries. Those limits keep the archive inside browser memory. Password-protected archives are not supported; remove the password with your archive tool before compressing.
If the archive barely changes, check what is inside. Media files and previously compressed documents leave little for DEFLATE to remove. If the result is larger, download the original instead; the tool offers it automatically. If the file is rejected as too large, reduce it below 1 GB or split it into smaller sets. If the tool reports an encrypted archive, remove the password first. If the worker stops on a phone or a low-memory laptop, close other tabs and try a smaller archive. Corrupted or unsupported archives are reported before compression starts.
On-device path
Local onlyYour files
Individual files or a folder, up to 250 MB.
This browser tab
Compressed by a local Web Worker.
No uploadFinished archive
Downloaded from an in-memory Blob.
0 bytes uploaded. There is no server-side copy of your files.
Privacy
The compressor reads files with browser APIs and builds the archive in a local Web Worker. There is no content upload step and no analytics script.
Loading the page fetches its HTML, CSS, JavaScript, fonts, and icon. Those requests do not contain your files. As with any website, the hosting provider may process standard connection logs for the page request itself; the tool does not send your content anywhere.
Limitations
No tool is the right fit for every job. These are the boundaries you should know before relying on the output.
FAQ
Still unsure about a limit or a result? Start with the answer here, then try the tool with a small sample.
Open the ZIP Compressor, add an existing .zip file, set the level from Low (1) to Max (9), then select Compress ZIP. The archive is rebuilt in your browser, and the result panel shows the original size, the new size, and the difference. There is no account, payment, or upload step.
Yes, if the files inside still have room to compress. The tool reads each entry in memory and rebuilds compressible entries at your chosen level. Already-compressed formats such as JPEG, PNG, MP4, ZIP, and Office files are stored as-is so they do not grow. A ZIP created by Windows, macOS, or another ZIP tool is already DEFLATE-compressed, so rebuilding it usually changes the size by less than 1%. Only an archive built with a store or fast setting has meaningful room left.
ZIP only removes repetition, and most ZIP files are already compressed. A .zip made by Windows, macOS, 7-Zip, or this tool has already been through DEFLATE; rebuilding it at Max usually changes it by less than 1%, and no lossless ZIP setting can do better. Photos, video, audio, and Office files are also already compressed, so they are stored as-is. Very small archives can even end up slightly larger overall. The result panel reports the real outcome, and when a rebuild is larger, the original ZIP stays available as the primary download.
Yes. The compressor runs in modern mobile browsers, and files are processed on the device rather than uploaded. Phones have less memory than laptops, so very large archives may fail. If that happens, compress a smaller set or use a desktop browser.
Usually nothing. JPEG, PNG, WebP, MP4, and MP3 are already compressed, so the tool stores them as-is instead of deflating them again. ZIP is most effective on text, code, CSV, logs, and other files with repeating patterns. To shrink photos or video, use a format-specific compressor instead.
No. The archive is read and rebuilt inside your browser with JavaScript and a Web Worker. Selecting files, compressing, and downloading all happen on your device. No file content is sent to YunoNext.
Yes. An existing ZIP must be under 1 GB, and its uncompressed contents are limited to 1 GB in total, 512 MB per file, and 100,000 entries. The limits exist because the archive is held in memory in your browser.
No. Encrypted archives are not supported. Remove the password with your archive tool, then compress the unlocked copy. The tool shows a specific message when it detects an encrypted archive instead of failing silently.
Max (9) is the default and gives the smallest archive. Low (1) finishes sooner and is useful for large batches or already-compressed files. Mid levels trade a little size for speed. The difference is largest on text-heavy inputs, and almost nothing on a ZIP that is already compressed.
Yes. The output is a standard ZIP with DEFLATE for compressible entries, stored entries for already-compressed formats, and no ZIP64 extension. That keeps it compatible with Windows Explorer, macOS Archive Utility, and common third-party tools. The limits keep output well below the point where ZIP64 would be needed.
When compressing an existing ZIP, the tool carries over folder entries, file dates, comments, and Unix or DOS permissions where they are present. A rebuilt archive is still a new file, so uncommon extra fields from the original tool may not survive. File contents are preserved exactly.
Yes. While a job is running, the progress panel offers a Cancel button. It stops the worker and discards the partial result. Nothing is downloaded and your selected archive remains available.
No. There is no analytics script in the compressor and no account system. The host may keep ordinary request logs for the page, as it does for any website, but file names and contents are never sent to it.
Ready when you are
No file upload, no account, no ads. Add your files and take the ZIP with you.