Home / Image tools / bulk resize
Batch
Bulk resize images
The tedious job. Forty photos off a camera that all need to be 1600 pixels wide and under a few hundred kilobytes before they go anywhere near a website.
Processed
Why doing this locally is the right call
Batch resizing is where upload-based tools become genuinely painful. Forty photos off a modern camera is several hundred megabytes, so you wait for the upload, wait in a queue, then wait for the download, and a site with a five file limit makes you do it in batches. Here the files never move, so the only cost is your own processor, and there is no cap on how many you drop in.
The trade is that a very large batch will make the browser work hard, and files are processed one after another rather than all at once so the tab stays responsive. A hundred large photos will take a couple of minutes. Leave the tab in the foreground; browsers throttle background tabs and it will run slower if you switch away.
Sensible settings
For a website, 1600 pixels on the longest edge at quality 82 is a good default that almost nobody can fault visually. For email attachments, 1200 is plenty. WebP will typically produce files a quarter to a third smaller than JPEG at the same quality, and every current browser reads it, but some upload forms and older desktop software still reject it.
Common questions
Can I download them all as a zip?
No, because zipping in the browser would mean loading another library and this site keeps its dependencies to a minimum. Save all triggers the downloads one after another; your browser will ask once whether to allow multiple files.
Are small images enlarged to my chosen width?
No. Anything already narrower is left at its own size, since upscaling invents detail rather than recovering it.
Is the metadata kept?
No. Re-encoding through a canvas drops Exif, including GPS, which for photos going onto a website is usually what you want anyway.
Other image tools