Bulk image resizer

Why a separate tool for batches

The single-image resizer is built around one photo at a time: you drop a file, watch a before/after preview, and download one result. That works well when you care about a specific photo's exact framing, but it gets tedious fast if you actually have thirty vacation photos, a folder of product shots, or a batch of scanned documents that all need the same treatment. This page runs the identical resizing engine (the same browser drawing surface, the same PNG/JPG encoder) across every file you select in one go, so a batch that would take thirty separate visits to the single-image tool takes one visit here instead.

How the target size works for a mixed batch

A batch of real photos rarely shares one aspect ratio: a phone's portrait shots, a camera's landscape shots, and a screenshot or two can all be sitting in the same folder. Forcing every one of them to an identical width AND height would stretch or squash whichever photos don't already match that exact ratio, which is the opposite of what a useful batch tool should do.

Instead, the width and height you type here define a bounding box, not an exact output size. Each photo is scaled to the largest size that fits entirely inside that box while keeping its own original proportions, the same idea as fitting a photo inside a picture frame without cropping it. A 4000×3000 landscape photo and a 3000×4000 portrait photo dropped into the same 1920×1920 box come out at 1920×1440 and 1440×1920 respectively: both shrink to fit, neither gets distorted, and neither gets cropped.

Worked example: a phone's camera roll folder before a website upload

Say a website's media library rejects anything over 1920 pixels wide, but a folder pulled straight from a phone has thirty photos ranging from 3024×4032 (portrait) to 4032×3024 (landscape). Set the target box to 1920×1920, choose JPG output at quality 85 (a good balance of file size and sharpness for ordinary photos, see the resizing guide's section on file formats), and run the batch. Every photo shrinks to fit inside that 1920×1920 box on its longer side, none get stretched, and the whole set downloads as one ZIP ready to unpack straight into the upload folder.

Worked example: preparing a product photo set for a fixed social media size

For a batch that genuinely does need one identical output size (say every product photo needs to be exactly 1080×1080 for a single Instagram grid, one of the sizes covered on the size presets page), switching on Allow enlarging smaller photos to fill the box and using square source photos gets the closest result: each photo fills the box completely rather than leaving empty space on one side. For photos that are not already square, cropping to a 1:1 ratio in a separate step before resizing gives a cleaner result than relying on the fit-to-box behaviour alone, since fit-to-box preserves the WHOLE photo rather than cropping any of it away.

Individual downloads or one ZIP file

After a batch finishes, every result appears in a grid with its own thumbnail and its own Download link, exactly like picking results out one at a time from the single-image tool. For anything more than a handful of files, the Download all as ZIP button is the faster path: it bundles every resized photo into a single archive with one click, using the same ZIP format that every operating system's built-in "extract" feature already understands (Windows Explorer, macOS Finder, and every major Linux file manager open a plain ZIP archive without any extra software). The archive is built entirely in your browser at download time; the individual photos never pass through a server to get bundled.

Output format and quality apply to the whole batch

The output format (PNG or JPG) and, for JPG, the quality slider apply identically to every photo in the batch, the same choice explained in full on the resizing guide. PNG stays lossless and keeps transparency but produces noticeably larger files across a whole batch; JPG at quality 80 to 90 is the usual choice for ordinary camera photos where total download size matters, especially once thirty or more files are bundled into one ZIP.

• PNG: choose this if any photo in the batch has transparency, or if the source photos are screenshots/graphics with sharp text and hard edges.
• JPG, quality 85 to 95: the usual choice for a batch of ordinary camera photos, keeping the whole ZIP a manageable size.
• JPG, quality 60 to 75: useful when a strict total upload size matters more than maximum sharpness across the batch.

What happens if one photo in the batch fails

A single unreadable or corrupted file does not stop the rest of the batch. If a photo cannot be decoded (an unsupported or damaged file, for example), the tool skips only that file, keeps processing the remaining photos, and lists the skipped filename in a visible error message once the batch finishes, so nothing fails silently and the rest of a large batch is never held hostage by one bad file.

Batch size and performance

This tool accepts up to 60 images per batch, each up to 30 MB, processed one after another rather than all simultaneously, which keeps memory use predictable regardless of how large the individual source photos are. A phone's camera roll folder or a typical product photo shoot both comfortably fit inside that limit in a single pass; a larger collection can simply be split into two batches run back to back. Processing speed depends entirely on the device doing the work (a modern laptop or phone handles a full batch of thirty ordinary photos in a few seconds), since, exactly like the single-image resizer, none of the work is sent to a server to be queued behind anyone else's job.