How to Bulk Resize Images Without Uploading Them
Resizing one photo is a ten-second job anywhere. Resizing sixty — product shots for a listing, a photo dump for a website, a semester of scanned documents — is where most free tools give up: they cap batches, queue your files behind other users, or demand a subscription.
Why browser-side bulk resizing is different
When a tool processes images on a server, every file you add costs the operator bandwidth and compute — that's why caps exist. This resizer runs on your own device instead, so there's no economic reason to limit you: drop as many images as you like. The practical limit is your hardware — a modern phone handles dozens of photos comfortably; a laptop, hundreds.
Step by step
- Open the resizer and pick the mode that matches the job — a KB target for upload limits, Pixels for a uniform width, Print size for physical dimensions.
- Select all your files at once in the picker, or drag the whole selection onto the drop zone.
- Press Resize. Files are processed one at a time; each row shows its own progress and result.
- When more than one file is done, a Download all (.zip) button appears — one click collects everything.
Settings that work well for batches
- Uniform web images: Pixels mode, width 1280 or 1920, aspect ratio locked — every image comes out the same width with heights that fit naturally.
- Portal uploads: Target KB mode with the portal's limit. Each photo gets its own quality search, so a dark photo and a bright one both land under the cap.
- Mixed formats: set Output format to JPEG for the smallest results, or "Keep original" if some files must stay PNG.
What slows a batch down
Two things: very large originals (a 40-megapixel photo takes longer to decode than a 4-megapixel one) and very tight KB targets, which need more search steps per image. Neither breaks anything — the batch just takes proportionally longer. Keep the tab in the foreground on phones; browsers throttle background tabs.
And because nothing uploads, a batch of two hundred client photos carries zero data-handling risk — they never left your machine.