The same size search as the fixed-target pages, but you choose the number and feed it a whole folder. Every image is compressed individually to land just under your target, which is the important part — a batch tool that applies one quality setting to everything produces wildly inconsistent file sizes, because what a given setting costs depends entirely on the picture.
Why local batch processing behaves differently
Upload-based bulk compressors have to move every file to a server and back, which is why they cap the number of files, limit the total size, and put you in a queue at busy times. None of that applies here. Your files are already on the device doing the work, so there is nothing to transfer and no queue to join.
The trade is that your own hardware sets the pace. A hundred images will take a while, and a phone will be slower than a laptop. Files are processed one after another rather than all at once — deliberately, because running many large images through canvas simultaneously is a reliable way to exhaust a browser tab’s memory and lose the whole batch.
Choosing a target
- 100–200KB for website images. This is where page weight stops being a problem while quality stays high.
- 300–500KB for photographs you want to keep looking good, such as an archive you are trimming down.
- 50KB or below only when a form demands it. At that budget most photographs will be visibly degraded and many will be resized.
- Whatever number the destination specifies, if something is imposing a limit on you.
What to expect from the results
Every file comes back close to but under your target, each having found its own quality setting. Simple images will have used a high one; detailed images a lower one. Where quality alone could not reach the target, the image will have been scaled down and the result says so, with the dimensions it settled on.
Files that were already smaller than the target are still re-encoded, which means they are recompressed. If a batch contains images that are already small, be aware you are spending a little quality for no size benefit on those.
Downloading a batch
Download all triggers each file in turn with a short pause between them, because browsers throttle or silently drop a burst of simultaneous downloads. Your browser may ask once for permission to download multiple files — allowing it lets the rest through. There is no zip, since building one would mean holding every result in memory at the same time, which is exactly what processing them sequentially avoids.
Everything runs in this tab. No file count limit, no total size cap, and nothing uploaded.