Batch Resize Hundreds of Photos at Once

Resizing a whole folder of photos is a five-minute job in the browser. Add the files to the Batch Image Resizer, pick one rule that applies to all of them, and download the results as a single ZIP. Nothing is uploaded, so it works the same for 10 family photos or 600 product shots, and it’s as fast as your device.

The workflow at a glance

1. Open the Batch Image Resizer.
2. Drop in up to 200 photos, choose them from a folder, or paste them.
3. Choose a resize mode and enter the size.
4. Leave Don’t enlarge smaller images on.
5. Pick an output format.
6. Select Process, then Download all to get a ZIP.
7. Repeat with the next 200 if you have more.

The sections below explain each choice, because the right settings depend on what the photos are for.

Step 1: Choose the right resize mode

The mode decides how every photo in the batch is treated. With a mixed folder of portrait and landscape shots, this matters more than the number you type.

Mode	What it does	Good for
Width	Sets the width; height follows the aspect ratio	Website columns, blog images
Height	Sets the height; width follows	Thumbnails in a row of equal height
Exact width × height	Forces every photo to one frame	Product grids, marketplace listings
Percentage	Scales each photo by the same factor	Cutting a whole camera roll down by half
Presets	Ready-made social sizes	Batches for one platform

For a folder that mixes orientations, a common goal is “no side longer than 2000 px.” Width mode would make portrait photos very tall, so test both width and height on a sample, or use a percentage if all photos come from the same camera.

Exact size is the only mode that changes shape. When a photo’s aspect ratio differs from the target, you choose how to handle it:

• Crop to fill fills the frame and trims the edges from the center. Use it for uniform grids.
• Fit inside keeps the whole photo and pads the gap with a color or a blurred copy of the image. Use it when nothing may be cut off.
• Stretch distorts the photo. It’s rarely what you want for photos.

If a centered crop would cut through something important on certain photos, crop those first with the Crop Image tool and resize afterward.

Step 2: Keep “Don’t enlarge” on

Don’t enlarge smaller images is on by default, and you should usually leave it that way. In a large batch there are almost always a few small images, such as screenshots, old phone photos or images saved from a chat. Enlarging them adds no detail. It only makes them blurry and heavier. With the option on, those files keep their original size while the rest shrink.

Lock aspect ratio is also on by default in width, height and percentage modes, so nothing gets squashed.

Step 3: Pick the output format

You can keep each photo’s original format or convert the whole batch to JPG, PNG or WebP at the same time.

• JPG is the safe choice for photos that will be emailed, printed or uploaded to forms and marketplaces. It opens everywhere.
• WebP gives noticeably smaller files at similar quality and is a good choice for websites.
• PNG is for screenshots, graphics and anything with transparency. It makes large files from photos, so avoid it for camera images.
• Keep original is useful when the folder mixes photos and graphics and each should stay in its own format.

iPhone HEIC photos can go into the same batch. They’re decoded in the browser and saved in the format you choose.

Step 4: Download and name your files

When processing finishes, each file shows a preview, its original and new file size, and the percentage saved. Select Download all to save one ZIP, or download single files. On a phone, Share / Save opens the system share sheet so you can save to Photos or Files.

A few habits keep large jobs organized:

• Never overwrite the originals. Unzip the results into a new folder, for example trip-2026-1600px, so the full-size photos are untouched.
• Name output folders by size and purpose. shop-1200x1200 and blog-1600w tell you months later what’s inside.
• Keep batches in matching order. If you split 600 photos into three batches, give the ZIPs numbered names like part-1, part-2 and part-3 before you unzip them.
• Remember that metadata is removed. Resized files don’t keep EXIF data like camera settings, dates or GPS location. Orientation is applied to the pixels, so photos stay upright. If you sort photos by date taken, sort them before resizing or keep the originals for your archive.

Step 5: Compress the batch, if needed

Resizing does most of the work: halving the width cuts the pixel count to a quarter, and the file size drops with it. If you need smaller files still, for example to meet an upload limit or speed up a website, run the resized ZIP’s contents through the Bulk Image Compressor. It applies the same compression to every file, shows the percentage saved and keeps the original whenever compressing would make a file larger.

Resize first, then compress. Compressing a full-size photo and then shrinking it wastes quality, because the resize step re-encodes the image again.

Limits and working with hundreds of photos

Pixellin processes up to 200 files per batch, up to 50 MB per file and up to 100 megapixels per image. For 500 photos, run three batches: 200, 200 and 100. Download each ZIP before starting the next batch, then remove the finished files from the list.

Tips for phones and tablets

Phones have far less memory than computers, and every photo in the list is held in the browser tab’s memory until you remove it or close the tab. To keep things smooth:

• Use smaller batches. 30 to 50 photos at a time is comfortable on most phones. Large camera photos take the most memory.
• Close other tabs and apps before starting a big batch.
• Keep the screen on and the tab in front. Mobile browsers may pause or reload background tabs, which can stop processing.
• Save as you go. Download or share each batch, then clear the list before adding the next one.
• Expect large photos to be scaled on iPhone and iPad. Safari limits canvas size, so images above roughly 16.7 megapixels are scaled down automatically, and the result says so. If you’re resizing to a normal web or sharing size, this has no visible effect.

If a batch on a phone stops or the page reloads, try again with fewer photos. For very large jobs, a laptop or desktop is noticeably faster.