Runs in your browser: your images never leave your device
Bulk image resizer
Drop a whole folder: up to 50 images, 25 MB each. One zip comes back. No upload time, no server queue, no per-image cost.
The upload is the slow part, and there isn't one
Fifty files at 25 MB each is 1.25 GB of images. On a tool that resizes on a server, that is 1.25 GB you have to upload before any work starts, then download again afterwards. On a home connection that is the entire job. Here it is zero: the files are read straight off your disk, and the only thing that ever crossed the network was the page itself.
Images are processed one at a time, in order, and each card updates as its turn comes. That is deliberate. Running ten at once would multiply peak memory by ten and, on the CPU path, freeze the whole tab. Sequential is slower to finish the first file and faster and safer to finish fifty.
| Limit | Value |
|---|---|
| Images per batch | 50 |
| Size per file | 25 MB |
| Formats in | JPEG, PNG, WebP |
| In flight at once | 1 |
Mixed sizes and shapes are fine
Each image is measured on its own and scaled by its own proportions, so a batch of portrait phone shots, landscape screenshots and square crops all come back correct against the same instruction. You are not forced into one output shape, and nothing gets letterboxed to match its neighbour.
A source that is smaller than the size you asked for is flagged before the batch runs, not quietly returned at the wrong size. Images are never enlarged.
The zip, and why it is not compressed
"Download all" packs the finished set into a single archive with no compression at all. That sounds wrong until you remember what is inside: JPEG and PNG are already compressed formats. Running them through deflate a second time saves almost nothing and costs a long pause on a 50-file batch. So the archive stores them as-is and appears immediately.
Names are kept and made unique. Two files called photo.jpg from different folders become photo.jpg and photo-2.jpg. Nothing silently overwrites anything else.
How to resize multiple images at once
- Set one size for the whole batch. A width, a height, or both as a maximum box. Every image is fitted to it by its own proportions.
- Drop the folder. Select or drag up to 50 files. They queue immediately and work through in order, with a live count of how many are ready.
- Download all as a zip. One file, original names preserved, no compression pause.
Frequently asked questions
How many images can I resize at once?
Fifty per batch, 25 MB each. Clear the batch and start another as many times as you like. There is no daily quota, because there is no server keeping score.
Why is there no upload progress bar?
Because nothing is being uploaded. The only download that ever happens is the background-removal model, and only if you switch that option on.
Do the images have to be the same size or shape?
No. Every image is scaled by its own proportions against the size you set, so mixed portrait, landscape and square sources all come out correct in one pass.
Will a big batch run my browser out of memory?
One image is in flight at a time, so peak memory is roughly one decoded image, not fifty. That is the main reason the queue is strictly sequential.
Can I remove backgrounds in bulk too?
Yes, with the same 50-image batch. Tick the background option here, or start from the background remover, which is set up for it. Expect it to take noticeably longer: that step is a neural network running once per image.
Every tool here follows the same rule
Whatever you came to do, it happens on your own machine. Nothing is uploaded, nothing is stored, and none of it costs anything.
Your images are still on your device
That is the whole idea. Drop them, take the results, close the tab. Nothing was sent anywhere and nothing was kept.
Drop your imagesNo account. No watermark. No upload.