CompressNeo

Unlimited Bulk Image Compressor

Optimize dozens of images simultaneously. High-speed client-side batch processing with instant ZIP download. No limits, no uploads, and no signup.

Launch bulk compressor

Unlimited Files

Select and compress as many files as your system memory allows. We place no arbitrary caps on batch uploads.

Zero Wait Times

Your browser executes multiple CPU threads using Web Workers. Parallel processing means no queuing delays.

Auto ZIP packaging

Once batch compression completes, you can download all compressed files in a single, clean `.zip` archive.

Why Local Bulk Image Compression is Superior

Standard bulk image compression tools limit you to 20 files per upload, enforce file size restrictions, or stall because uploading 100MB of images takes minutes. This occurs because files must be uploaded to their physical hosting servers for processing.

CompressNeo is different. By running 100% client-side inside Web Workers, your browser compresses files locally. File reading is instant, processing is parallelized across your CPU threads, and downloading is immediate. You can compress thousands of images offline without any network overhead.

Comparison of Bulk Compression Capabilities

Metric CompressNeo TinyPNG Squoosh ILoveIMG
Batch Size Limit Unlimited Max 20 files Single file only Limited (Free tier)
File size limit Unlimited 5MB (Free tier) Unlimited Limited
Download Format Single Files or ZIP ZIP or Individual Individual Only ZIP or Individual
Offline Support Yes (100% local) No Yes No

Frequently asked questions

How does the ZIP compression work?

We use a local JavaScript port of `fflate` inside the browser to compile all compressed image files into a single zip archive. This packaging occurs entirely client-side with zero data leaks.

Will bulk compression slow down my computer?

Since we run in browser Web Workers, we limit main thread interference to prevent tab freezing. For extremely large batches (hundreds of high-resolution images), you may notice temporary CPU utilization spikes as files process in parallel.

Is there any file size limitation?

There is no hardcoded limitation. However, very large raw files (e.g. 50MB+) require sufficient system RAM to be decoded on the local HTML5 canvas.