Sixty images, and your compressor takes twenty at a time

You export sixty images for a handoff. You open the compressor you always use, and it tells you it takes twenty at a time. Fine — three rounds.

Then a dozen of those files turn out to be over 5 MB, and it will not take them at all. Not slower, not queued. Rejected. So now you are pulling those twelve out, finding a second tool for them, and reassembling the folder by hand.

Twenty is the number, wherever they count images

We checked ten free compressors on 22 July 2026, reading the limits off each site rather than off anyone's comparison post. Among the tools that cap you by image count, the answer came back the same over and over:

tinypng.com          20      (and max 5 MB per file)
compressjpeg.com     20
jpeg-optimizer.com   20
squoosh.app           1      no batch mode at all
jpegcompressor.com   no image cap, 250 MB per batch

Squoosh, which is Google's, does not do batches at all — its FAQ has called batch processing "our most-popular request" since 2021.

The rest is arithmetic. Sixty images against a cap of twenty is three uploads, three waits, three zip files, and three trips to your downloads folder to put the pieces back together. Against a cap of a hundred it is one of each.

TinyPNG's 5 MB wall is the one that actually stops you

TinyPNG is the site most people mean when they say "the compression site". Its drop zone states the terms without ceremony: Up to 20 images, max 5 MB each.

Those two limits fail differently. The batch cap costs you time, and time you can spend. The size cap costs you the file. A 4000-pixel product shot, a PNG straight out of a design tool, a photo off any recent phone — for any of those, clearing 5 MB is a Tuesday. They come back rejected and there is nothing to wait for.

PiPic takes 8 MB, and that number comes out of a memory budget. A Worker instance gets 128 MB and serves several uploads at the same time, and each upload in flight holds one full copy of the incoming file, because a stream can only be read once and a retry has to be able to replay it. Eight leaves room for roughly sixteen uploads sharing an instance. We would rather publish the number the machine actually supports than a bigger one that falls over on a busy afternoon.

Check the limits before you upload

You do not have to take our word for any of this, and you should not have to discover a limit by hitting it:

• The drop zone usually says so outright. That grey line under "choose files" is where TinyPNG puts its twenty and its 5 MB.
• If it is not there, search the site's FAQ for limit or how many.
• Read "free and unlimited" carefully. It nearly always means no daily cap, not no per-batch cap, and those are very different promises.
• If nobody states it anywhere, you will find out by hitting the wall. Two of the ten we checked never publish a limit for visitors without an account.

Where PiPic sits

A hundred images per batch, 8 MB per file, JPG, PNG, WebP and AVIF in with the same format back out, no account, and the whole batch back as one zip. The sixty-image folder is a single pass, and the dozen large ones go through with the rest.

The batch ceiling is the number we deliberately pushed on, because it is the one that turns a two-minute job into an afternoon of bookkeeping. If you only ever compress PNGs, the PNG page is the same compressor with the format-specific notes attached.

Sixty images, one upload, one zip. That is the entire pitch.