ZIP Creator
Drop files in, get one ZIP out. Real compression where it helps, and none where it would only waste your time.
Drop files or a folder here
The archive is built in this page. Nothing is uploaded.
The .zip is added for you.
Your files on disk are never touched.
{n} number, {name} original, {ext} extension.
- Files
- —
- Original
- —
- Archive
- —
Already-compressed files are stored, not crunched
JPEG, PNG, MP4 and MP3 have no redundancy left for DEFLATE to find, so they are packaged as they are. That is why a photo folder zips instantly and comes out the same size. Text, CSV, JSON and logs compress properly.
Everything here runs on your device. Nothing you enter is uploaded or stored.
Drop in files or a whole folder, get one ZIP out. Compression is real — DEFLATE, the same algorithm every ZIP tool uses — and it is applied where it actually helps. You can also renumber everything inside the archive without touching a single file on your disk.
How to use it
Add files by dropping them on the panel, choosing them, or picking a folder to preserve its structure. The list shows each file with its size and whether it will be compressed or stored. Pick a compression level, optionally turn on batch rename, then press Create ZIP. The estimate above the list updates as you go, and is replaced by the real figure once the archive exists.
Compression is chosen per file, not per archive
Most online ZIP tools do one of two things: compress everything, or compress nothing. Both are wrong for a mixed folder.
Compressing everything means spending real CPU time running DEFLATE over your JPEGs, which are already entropy-coded. The measured saving on a folder of camera photos is under one per cent, and for some files the compressed result is slightly larger than the original — you paid for the wait and got a worse archive.
Compressing nothing means a folder of CSV exports comes out at full size when it could have been a third of that.
So the choice is made per file, by extension. Roughly fifty already-compressed formats — the image, audio, video, archive and Office families — are stored. Everything else is deflated, and then checked: if the compressed result is not genuinely smaller, the stored copy is written instead. An entry that grew is a cost you would pay on every future extraction, so it never gets written.
Batch rename applies inside the archive
The rename pattern uses three tokens. {n} is the number, {name} is the original filename without its extension, and {ext} is the extension. Start number and zero-padding are yours to set, so photo-{n} with padding 3 gives you photo-001.jpg, photo-002.jpg, and so on.
The extension is handled separately and re-attached automatically, because a rename that quietly drops .jpg produces a file your computer no longer knows how to open. If your pattern already ends in the right extension it is left alone rather than doubled.
What it does not do
No password protection. Encrypted ZIP is either the ancient ZipCrypto scheme, which is broken and trivially cracked, or AES-256, which needs a key-derivation step this page has no safe way to do — and offering weak encryption labelled as protection is worse than offering none. No RAR or 7z output; those formats are patent-tangled or need a large WASM decoder for very little gain over ZIP. No splitting an archive into volumes — that is File Splitter’s job, and it does it with a rejoin script and a hash check.
Which tool for which job
| You want to | Use |
|---|---|
| Bundle files into one download | ZIP Creator |
| Look inside a ZIP before extracting | ZIP Extractor |
| Cut one huge file into transferable parts | File Splitter |
| Find out what is eating your disk | File Size Analyzer |
| Make images themselves smaller | Image Compressor |
Compressing images properly is a different operation from archiving them — Image Compressor re-encodes the pixels, which is where the real saving on a photo folder comes from.
Questions
Why did my photos not get smaller?
Because they were already compressed, and that is worth understanding rather than treating as a bug. JPEG, PNG, WebP, MP4 and MP3 are all entropy-coded formats — the redundancy DEFLATE hunts for was already removed when the file was encoded. Running it again typically saves under one per cent and occasionally makes the file marginally bigger. This tool detects those formats and stores them instead, which is why a folder of holiday photos zips almost instantly and comes out roughly the same size. Text, CSV, JSON, logs, source code and most documents compress properly, often to a third of their original size.
What does Store only actually do?
It skips the compression attempt on everything and just packages the bytes as they are. The archive ends up the same size as its contents plus about eighty bytes per file. It is worth choosing when you are archiving a large amount of video or photos and you want the ZIP finished as fast as your disk can read, since compression is pure wasted CPU on that content. For anything text-shaped, leave it on Compress.
Does batch rename change my actual files?
No, and this is a deliberate line. The renaming applies only to the names written inside the archive — your files on disk keep the names they had. A browser page cannot rename files on your computer, and even if it could, silently rewriting names on disk is a destructive action that should never happen as a side effect of making a ZIP. Extract the archive and you get the new names; keep the originals and nothing has changed.
What happens if two files have the same name?
They get numbered, because the alternative loses data. A ZIP with two entries called photo.jpg is technically legal but most extractors will write one over the other without a word, so you would open the archive later and find one file where you put two. Two files named the same become photo.jpg and photo-2.jpg. If you added a folder rather than loose files, the folder path is kept and there is usually no collision to resolve.
How large an archive can it build?
Comfortably into the hundreds of megabytes, and it depends on your device rather than on a fixed limit. Everything is held in memory while the archive is assembled, so a phone will tap out well before a desktop does. If you are trying to package several gigabytes, a ZIP is the wrong shape for the job anyway — use File Splitter to cut the large file into transferable parts instead.
Last updated