How to Resize Hundreds of Images at Once Without Ruining Any of Them
Resizing a folder of mixed portrait and landscape photos to one size is where batch jobs go wrong. Here is how to set it up so every image survives.
Updated August 11, 20265 min read
Batch resizing sounds like the easiest automation there is: pick a size, point it at a folder, walk away. It goes wrong because real folders are not uniform. They contain portrait and landscape shots, the occasional screenshot, one panorama and a logo somebody dropped in. A single "resize to 1200 × 800" applied to that mix produces stretched portraits and an unusably squashed panorama. The fix is choosing the right *kind* of constraint, not the right numbers.
Constrain one dimension, not both
This is the whole trick. If you specify width and height, every image is forced into that exact rectangle and anything with a different shape is either stretched or padded. If you specify only one — say, 1600 pixels on the long edge — each image keeps its own proportions and simply scales until it hits the limit.
| Constraint | What happens to mixed shapes | Use when |
|---|---|---|
| Long edge only | Every image scales proportionally | General purpose — the safe default |
| Width only | Portraits end up much taller than landscapes | Web content in a fixed-width column |
| Height only | Landscapes end up much wider | Image rows, thumbnails of uniform height |
| Width and height | Distortion, or bars, or a centre crop | Only when every source is already the same shape |
Never upscale in a batch
Somewhere in the folder there is a small image — a logo, a screenshot, something saved off a website. If your batch says "make everything 2000 pixels wide," that 400-pixel file gets blown up to 2000 and becomes a soft, blocky mess, while the 6000-pixel photos come down correctly.
Treat the number as a ceiling rather than a target: shrink anything above it, leave anything below it alone. In the resizer that means switching off Allow enlarging, which is on by default. If a genuinely small image does need enlarging, that is a separate, deliberate job — see enlarging an image without turning it to mush — and not something to do a hundred times unattended.
A batch workflow that holds up
Copy the folder first
Batch operations are unattended and destructive by nature. Work on a copy so a wrong setting costs you a re-run rather than the originals.
Sort out the odd ones
Pull the panorama, the logo and the screenshot into a separate pile. Five outliers handled by hand beat a compromise setting that serves none of the hundred well.
Resize on the long edge
In the resizer, choose Longest side and turn off Allow enlarging, which is on by default — that makes your number a ceiling rather than a target. Multiple files at once is a Pro feature; on the free tier the tool takes one file at a time.
Apply adjustments separately if you need them
Brightness, contrast, sharpening and grayscale across a whole set are what the batch image editor is for. It also has its own resize step (long edge, exact size or percentage), so if you are adjusting anyway, one pass can do both — up to three files at a time on the free tier.
Rename for order
The batch renamer gives you a consistent, sortable naming scheme. Zero-pad the numbers or 10 will sort before 2 everywhere.
Spot-check the extremes
Open the widest, tallest and smallest results. If those three are right, the middle of the distribution almost certainly is too.
Runs on your own device, so a large folder (with Pro) is limited by your machine rather than an upload queue — and nothing is transmitted.
Resize imagesSize ceilings versus dimension limits
These solve different problems and people frequently reach for the wrong one. A dimension limit controls how big the picture appears. A file-size ceiling controls how many kilobytes it occupies. If your constraint is "the CMS rejects anything over 2MB," a dimension limit only gets you there by luck.
For a hard byte limit, run the set through the compressor, which applies the same ceiling to every file (compressing several files at once is a Pro feature) and finds the best quality that fits each one. Doing both — long-edge limit first, then size ceiling — gives predictable results on both axes, and in that order, because compressing before resizing wastes bits on pixels you then discard.
Why local processing matters for batches
Batch work is where uploading hurts most. Two hundred phone photos is often a gigabyte or more; on a typical home connection that is an upload that can easily take ten minutes or more before any processing starts, then a download of the results. Doing the work on your own device skips both transfers — the constraint becomes how fast your disk reads, which is a different order of magnitude.
It also removes a real question about what a service is doing with a few hundred of your photographs. Every tool linked here reads and writes the files locally on your device; nothing is transmitted, and the job keeps running with the network disconnected.
One last habit that pays for itself the second time you do this: write down the settings you used. A batch is only reproducible if you can repeat it — six months later, when the same client sends another folder, "1800px long edge, JPG at 85, renamed with a three-digit prefix" takes ten seconds to reapply and is otherwise a guessing game.
Frequently asked questions
How do I resize multiple images to the same size?
Constrain a single dimension — usually the longest edge — rather than both width and height. That way portraits, landscapes and squares each scale proportionally to the same maximum, instead of being forced into one rectangle and distorted.
Will batch resizing distort my images?
Only if you specify width and height together and the sources are not all the same shape. Setting one constraint preserves every image's proportions. Also make the number a ceiling — in the resizer, turn off Allow enlarging, which is on by default — so small files are left alone rather than being upscaled.
What size should I resize a folder of photos to?
1600–2000 pixels on the longest edge covers almost every on-screen use including high-density displays, and typically cuts a folder of phone photos by 80–90%. Go larger only if the images will be printed or cropped into later.
Can I batch resize images for free?
The resizer handles one file at a time on the free tier; processing multiple files in a single pass is a Pro feature. Either way the work happens on your own device, so there is no upload wait and no cap on total volume over time.