Resize Multiple Images at Once
This free bulk image resizer takes up to 50 images in one go and resizes them all on your own machine: shrink everything by a percentage, fit every file inside a maximum width and height, or force the whole batch to exact dimensions. JPG, PNG, WebP, AVIF or GIF up to 25 MB each, downloaded as a zip, with nothing uploaded and nothing to sign up for.
Drop your images here to resize them all
JPG, PNG, WebP, AVIF or GIF, up to 25 MB. Up to 50 at a time, resized in your browser, never uploaded.
Two Hundred Photos.
One Size Decision.
Resizing images one at a time is not difficult, it is just the same six clicks repeated until you stop paying attention, and somewhere around the fortieth file you type 1080 where you meant 1920. Drop the whole folder instead. You answer the size question once, every file is measured against that answer using its own dimensions, and each card shows you what it became before you download anything.
Need a file size instead of a size in pixels?
Resizing changes dimensions, which usually makes a file smaller as a side effect but never to a number you can promise. When something downstream wants 'under 100 KB', that is compression, and these pages do it to a whole batch the same way this one does.
Tools that pair well with this one
All free, all in your browser, no signup.
How to resize multiple images at once
Three steps, no account, up to 50 files a run.
Select all your images
Drop a folder's worth onto the box, or use the picker and select as many as you need. They stay on your device.
Answer the size question once
Choose a percentage, a maximum box, or exact width and height. Every card updates to show the size that file will become.
Run it and download the zip
Watch each file finish with its own before and after, then take the whole batch as one archive.
The whole point
What 'the same size' means when the images are different shapes
This is the question every batch resizer has to answer and most of them dodge. For one image, 'width 1200, height 800' is a complete instruction. For a queue of portraits and landscapes it is not: applied literally it squashes everything to one aspect ratio, and applied with the ratio locked it contradicts itself, because two numbers cannot both be honoured while each file keeps its own proportions. So this tool asks which of three questions you are actually asking.
- Scale: 'Half the size', measured against each file's own dimensions. A 4000px photo becomes 2000px and a 1000px one becomes 500px. This is the only mode where files that started different stay different, which is usually what somebody shrinking a folder of holiday photos actually wants.
- Fit: 'Nothing bigger than 1920 by 1080'. Every file keeps its own aspect ratio and comes down until it fits inside the box, and anything already smaller is left completely alone. This is the mode for a website, where the requirement is a ceiling rather than a size.
- Exact: 'Every file 1000 by 1000, no exceptions'. This is the mode that resizes multiple images to the same size, and it is what an ecommerce catalogue or a print sheet needs. Leave the ratio locked and the width is the instruction while each file's height follows its own proportions; unlock it and you get the literal dimensions on every file.
Fit never enlarges, on purpose. 'Fit inside 1920 by 1080' applied to a 400px thumbnail would invent three quarters of its pixels to satisfy a rule that only ever existed to stop things being too big. Scale will enlarge if you ask it to, up to four times, because there you have asked in so many words.
A batch image resizer applies one setting to every file
This is the difference between a bulk tool and the same tool run thirty times. You make the decision once, it is the same decision for every file, and that is also why the results are consistent enough to publish next to each other.
Every card in the queue shows the size that file will become before anything runs, calculated from its own dimensions against your setting. So you can see the odd one out, the screenshot that came in at 3840 wide or the logo that was always going to be too small, while you can still change your mind about it.
Tick individual cards and the run touches only those, which is how you give the two banner images a different treatment from the twenty thumbnails without starting a second batch. Tick none and it touches everything, which is what somebody who never noticed the checkboxes expects.
Quality and DPI are batch-wide as well. Quality only does anything for formats whose encoder has a quality argument, so the panel says 'Lossless formats' rather than showing you a slider that is quietly doing nothing to your PNGs.
Batch resize JPG, PNG, WebP, AVIF and GIF together
You do not have to sort the folder first. Mix them, and each file comes back as the format it went in as.
- JPG and JPEG: The common case for a batch of photographs, and the one where the quality setting earns its keep. Resize jpg images in bulk and the encoder re-compresses each one at the quality you set for the run.
- PNG: Resize png images and transparency survives, including the partial transparency along antialiased edges. PNG has no quality dial, so the setting is ignored rather than silently applied.
- WebP and AVIF: Both keep their alpha channel through a resize. AVIF encoding depends on the browser, so the tool checks what yours can actually write rather than guessing from a user agent.
- GIF: Still GIFs resize normally. Animated ones are refused with a reason instead of being flattened, because a canvas only ever sees the first frame and handing back a still image that still ends in .gif is the kind of thing you discover in a group chat.
Nothing is converted behind your back. A batch of PNGs comes back as PNGs, which matters because the cheapest way to post an impressive number on a results screen is to quietly turn them into JPGs, discard the alpha channel and paint white behind whatever was transparent. If converting is genuinely what you want, the converter does it on purpose.
Resizing multiple images without losing quality you can see
'Without losing quality' is doing a lot of work in that sentence, so here is the version we can stand behind across thirty files at once.
Making an image smaller is the well-behaved direction. You are throwing away pixels you were not going to display anyway, and a 4000px photo shown in a 1200px column loses nothing anybody can point at. What costs quality is the re-encode that follows, which is why the quality control is separate from the size control and defaults high.
Enlarging is the other direction and it cannot add detail that was never captured. Scale mode will take a batch up to four times its size because sometimes that is genuinely what you need, but the result is interpolated rather than recovered, and no tool that claims otherwise is telling you the truth.
In a batch the risk is not that one file goes too far, it is that you do not notice which one did. Every finished row carries its own before and after and its own dimensions, so check the two or three files you care most about rather than all thirty, and re-run at a different setting if one of them is wrong.
Bulk resize product images, website assets and social posts
Three jobs that arrive as a folder rather than a file, and the mode each one wants. The sizes below are the requirements people are usually handed, not our invention.
| The job | Typical requirement | The mode to use |
|---|---|---|
| Ecommerce product shots | 1000 x 1000 or 2000 x 2000, square, identical across the catalogue | Exact, ratio unlocked |
| Images for a website or blog | Nothing wider than 1920, everything under control | Fit |
| A folder of camera photos | Half or a quarter of the original, still in proportion | Scale |
| Social media posts | 1080 x 1080 square, or 1080 x 1350 portrait | Exact, ratio unlocked |
| Print at 300 DPI | The size in cm or inches, with the resolution written in | Exact, with DPI set |
Resizing images for a website is the one worth a second sentence, because the requirement there is genuinely a ceiling rather than a size. Fit mode leaves your already-small icons alone and only touches the twelve photographs that were 4000px wide, which is exactly the behaviour you want and exactly what an exact-dimensions batch would get wrong.
Dimensions are half the job for the web. A 1920px JPEG can still be 1.4 MB, and page speed is measured in bytes rather than pixels, so resize here and then run the same folder through the bulk compressor.
Why a bulk photo resizer stops at 50 images
50 is where the queue stops being something you can scan, not where the engine stops coping. It is a readability limit rather than a technical one, and it is worth stating which kind it is, because most tools with a cap will not tell you.
The files are resized one after another rather than all at once, on purpose. Each one is decoded to a full bitmap first, and a 12 megapixel photo is roughly 48 MB of raw pixels before anything happens to it. A dozen of those in flight together is a browser tab that gets killed, with no warning and no error to explain it.
Sequential also makes the progress honest. '7 of 30' means something when one file is genuinely being worked on. So if you came here to resize 50 images, that is one run; 50+ images is two runs, and the tool holds no state between them and asks nothing of you at the start of one, so the second batch costs a drag and a click.
Each file is also capped at 50 megapixels going in and coming out, which is what stops somebody enlarging a queue of photos to a size no browser can hold. Genuinely enormous jobs, thousands of files or RAW, are where desktop software still wins and we would rather say so.
A free bulk image resizer online, with nothing to install
Bulk features are usually where a free tool starts asking for something: an account, a daily quota, a watermark, a paid tier at ten files. This one does not, and the reason is structural rather than generous.
- Your device does the work: So 50 images cost us exactly what one image does, which is nothing. There is no per-run bill for us to pass on and therefore no quota to enforce.
- Nothing is uploaded: A batch of forty photos never leaves the machine it is on. That is a stronger promise than any privacy policy, including ours, because there is no server holding the files to make a promise about.
- No account, no watermark, no daily limit: Not on the first batch and not on the fiftieth, and no resolution tier that sells you a better copy of your own photos. The download is never the thing we ask you to pay for.
The one real limit is per file rather than per batch: 25 MB each. A file over the limit is refused with a reason instead of gambling with the rest of your queue.
Built for the folder, not the file.
Everything here is written for many images at different sizes. One image is just the smallest batch there is.
Up to 50 images in one run
Drag a folder's worth in, or keep adding once the queue is open. Each file can be up to 25 MB, so full-resolution phone and camera photos are the normal case rather than the exception.
Three ways to mean one size
Scale by a percentage, fit everything inside a box, or force exact dimensions. Portrait and landscape files in the same queue are the reason there are three, not one.
Download the batch as a zip
One button, one archive, original filenames intact. Or save individual results from the list if only four of the thirty were the point.
A bad file does not end the run
If one image is corrupt, animated, or in a format the browser cannot decode, that row is marked failed with a reason and the queue carries on. Twenty-nine good files are not punished for one bad one.
50 images, still nothing uploaded
The batch is processed by your own browser, one file after another. No server queue, no upload bar, and no copy of your photos anywhere for us to lose.
Resize a camera roll on the phone itself
Select multiple photos straight from the camera roll and resize them without opening a laptop. Slower than a desktop, because the work is real, but the same three modes and the same zip at the end.
Frequently asked questions
How a batch runs, and where it stops.
Drop all of them onto the box above, or open the picker and select up to 50 files. They arrive as a queue of cards, you choose one of the three size modes and type your numbers once, and you press the button once for the whole batch.
You can keep adding files after the queue is open, and you can remove any you changed your mind about. Nothing runs until you tell it to.
Yes. Choose Exact, turn the aspect ratio lock off, and type the width and height. Every file in the queue comes out at those dimensions regardless of what shape it started as, which is what a product catalogue or a print sheet needs.
Leave the lock on instead and the width becomes the instruction while each file's height follows its own proportions. That is the right answer far more often than it sounds, because upload forms and page layouts almost always specify a width.
Up to 50, at up to 25 MB each. Past 50 the list stops being something you can actually read, which is the limit we hit long before the browser does.
There is no cap on how many batches you run. Nothing is counted, nothing is stored between runs, and no batch costs us anything, so there is nothing for us to ration.
Both are there. The results screen has a single button that packs the whole batch into one zip with the original filenames, and every row also has its own download if you only wanted four of the thirty.
Yes, and you do not need to sort them first. Each file is resized and comes back as the format it arrived in, so the PNGs keep their transparency and the JPEGs stay JPEGs.
Animated GIFs are the one exception, and they are refused rather than mishandled. A browser canvas only sees the first frame, so resizing one would hand you back a still image that still ends in .gif.
Not with this tool, and it is worth being precise about why rather than pretending. Resizing changes an image's dimensions, measured in pixels. 100 KB is a file size, measured in bytes. Fewer pixels usually means fewer bytes, but there is no width you can type that guarantees a particular number of kilobytes, because that depends on the content of each photograph.
The bulk image compressor is the tool for that: type a target in KB once and every file in the queue comes back under it. If you need both, resize here first and compress the results, in that order.
No, and this is the part bulk usually changes. Most batch resizers need your files on their servers to do the work, which is why they show you an upload bar. This one decodes and redraws every file in your own browser, so the batch never leaves your device and there is nothing to delete afterwards.
The practical proof: turn off your network after the page has loaded and the batch still runs.
That row is marked failed with a reason, and the rest of the queue keeps going. A corrupt file, an animated GIF, a HEIC from an iPhone, or an image past the pixel ceiling stops itself and nothing else.
You can remove it and re-run, or just download what worked. A batch where one bad file discards the other twenty-nine results is not a batch tool.
Free, and no. No signup, no watermark on any output, no daily limit, and no paid tier that unlocks more files or bigger dimensions. Every setting is available on every run.
That is possible because your own machine does the resizing. A hundred batches cost us exactly what zero do, so there is nothing to recover and nothing to gate.
Resize the whole folder now
Drop up to 50 images, answer the size question once, take the zip. Nothing gets uploaded and nothing gets counted.