Bulk Image Compression Guide: Compress Many Photos at Once

Compressing one photo takes half a minute. Compressing 60 product shots or 180 scanned pages is a different job: the hard part is not the compression but holding every file to the same rule without opening each one. Bulk image compression solves that. This guide covers when it is worth setting up, which tools accept many files at once, what happens to each picture inside a batch tool, and a six-step workflow for folders with hundreds of files.

Quick answer: use a batch tool that applies one target size to every file, cap the longest side at the resolution you will actually show, test the settings on three or four typical images first, and keep the untouched originals. Our free bulk image compressor takes up to 200 images per run, compresses them on your own device without uploading anything, and bundles the results into one ZIP.

When You Need to Compress Multiple Images

A batch tool earns its place when many files share a destination and a rule. Four situations come up again and again.

Building or redesigning a website. A new site usually inherits a media folder of camera-sized files. A hero image straight from a phone is often 3–5 MB, yet at 1600 px wide and about 200 kB it looks the same on screen and loads in a fraction of the time. Our article on why images should be compressed for the web covers the speed side.

Cleaning up during a platform migration. Moving a shop or blog between platforms is when people discover that years of uploads were never resized. Export the media library, run it through a batch tool with a longest-side cap, and import the clean set instead of the old bloat.

Galleries and portfolios. A photographer delivering 300 event previews, or a designer publishing a case study, needs every file under the gallery’s per-image ceiling and consistent beside its neighbours. Viewers on a weak mobile connection notice the difference more than the creator does.

Scanned paperwork and ID documents. Students and job applicants in India often have a folder of certificate scans, each several megabytes from a phone scanner app, while the portal wants each under 100 kB or 200 kB. One batch run replaces an afternoon of rejected uploads; for a specific portal’s limits, see our Indian government website requirements guide.

Options for Bulk Compression

Three routes are realistic; which one fits depends on the file count, whether each file needs an exact size, and whether you are happy with a command line.

Route	Files per run	Size control	Runs where	Best for
Single image compressor	1	Exact kB target, exact-dimension crop, before/after slider	Your browser	Form uploads, passport photos, one hero image
Bulk image compressor	Up to 200	One kB or MB target for all, optional longest-side cap, Auto/JPG/WebP/PNG	Your browser	Galleries, product sets, scan folders, migrations
ImageMagick mogrify (desktop)	Unlimited	Fixed quality and resize, no byte target	Installed software	Thousands of files, scripted or repeated jobs

The bulk image compressor runs the same engine as the single-file tool across a queue. Add up to 200 JPG, PNG, WebP, GIF, BMP or HEIC files (HEIC only where the browser can decode it, such as Safari), type one target, optionally cap the longest side in pixels, choose an output format and press Compress all. Files are processed one after another on your device, each row gets its own Save button, and Download all as ZIP builds one archive inside the browser. Auto suits a mixed folder, JPG suits portals and email, and WebP suits your own website: Google’s WebP documentation puts lossy WebP at 25–34% smaller than JPEG at comparable quality.

For very large or recurring jobs, desktop software remains the heavyweight option. ImageMagick’s mogrify command resizes and re-saves thousands of files in one line, but its documentation warns that it overwrites the originals in place unless you send output elsewhere with -path or change the extension with -format, so copy the folder first. Graphical converters such as XnConvert do similar work through a settings panel. Both set a fixed quality rather than a byte target, so a rule like “100 kB per file” still needs checking afterwards.

How Bulk Compression Works

Every batch tool repeats what a single-file tool does: open, decide dimensions, re-encode, save, move on. The interesting part is how quality is decided.

Browser-based tools draw the picture onto a canvas and ask the browser to encode the pixels again. According to MDN, that encoder takes a quality value from 0 to 1 for lossy formats such as JPEG and WebP, and falls back to PNG when no supported format is requested. A simple batch tool picks one value, say 0.8, for every file. The catch is that one quality value does not mean one file size: at that setting a 4000 × 3000 px photo of a plain sky could come out at 400 kB while a crowd scene at the same dimensions comes out at 2 MB, because JPEG spends more bytes on detail. One setting for the whole folder therefore gives uneven sizes, and sometimes uneven quality.

Mb2KbSizer works the other way round. For each file it runs a binary search over quality until the output lands at or just under your target. If that would push quality below roughly 45%, it reduces the pixel dimensions in high-quality steps and searches again, because a slightly smaller, clean picture beats a full-size blocky one. The sky photo and the crowd photo both finish under 200 kB; the crowd photo simply gives up a few more pixels. Because the browser rebuilds each file from pixels, camera metadata including GPS location is dropped, orientation is applied so portraits stay upright, and transparent PNG areas become white when saved as JPG.

Even so, a size guarantee is not a quality guarantee. After the run, open the two or three images you care most about at full size; a group photo that lost more pixels than expected is better redone alone at a higher target.

Tips for Consistent Results Across Batches

• Batch similar images together. Product shots on white, outdoor photographs, screenshots and document scans each respond differently to the same target. Run them as separate groups so one setting suits the whole group.
• Normalise dimensions before you worry about kilobytes. Decide the largest size the images will ever be shown at, such as 1600 or 2000 px on the long edge, and set that as the cap. Uniform dimensions make the size search easier and the gallery tidier.
• Trial the settings on three or four representative files. Choose the largest, the most detailed and one average file. If those look right at the target, the rest will almost certainly follow.
• Keep the untouched originals. Compression throws detail away for good. Store the originals in a separate folder before you start, and never let a batch tool write over them.
• Use one tool and one set of settings for the whole project. Mixed tools give mixed colour handling, dimensions and naming. Finish with the settings you tested, and write them down for the next batch.

Our guide to reducing image size without losing quality explains which settings matter most, and JPEG vs PNG vs WebP helps you pick the output format.

Mobile vs Desktop Bulk Compression

A laptop or desktop has more memory and processing power to spare, so a 200-file batch of large camera photos finishes sooner there, and reviewing the output in a file manager is easier. Given the choice, run big batches on the computer.

Phones cope well within sensible limits. Our bulk tool processes files one at a time and runs the heavy work in a background Web Worker, so memory use stays level and the page stays responsive. Two habits help: keep the tab in the foreground until the summary shows every file counted, because mobile browsers may pause a background tab, and on an older device prefer runs of a few dozen large photos rather than the full 200. The tool can be added to your home screen like an app, though it still needs an internet connection to load. We do not offer a native app, and you do not need one.

Recommended Workflow for Large Batches

1. Group by type. Photos, graphics with transparency and document scans go in separate folders.
2. Pick the dimensions. Set the longest-side cap to the largest size the images will be shown at.
3. Test on a small sample from each group. Three or four files per group at the chosen target, inspected at full size.
4. Run the full batch. Add up to 200 files, confirm the target, format and cap, and press Compress all.
5. Scan the output. Check the row list for anything marked Over target or Failed, then open a handful of results.
6. Redo the exceptions individually. Send flagged files through the single image compressor at a higher target or different dimensions.

Three typical projects with that process:

Project	Input	Settings	Likely result
120 product photos for an online shop	4000 × 3000 px, about 3.5 MB each (roughly 420 MB)	Target 200 kB, longest side 1600 px, JPG	1600 × 1200 px files at or just under 200 kB, about 24 MB in total
25 event photos to send by email	Phone photos of roughly 2–8 MB each	Target 700 kB, longest side 2000 px	Under 18 MB in total, inside Gmail’s 25 MB attachment limit even after the roughly one-third growth that email encoding adds
80 certificate scans for job portals	A4 at 300 dpi, about 2480 × 3508 px, 1.5–4 MB each	Target 100 kB, longest side 1600 px, JPG	Mostly white pages compress well, so most land under 100 kB at the capped size; dense pages lose a few more pixels

Write down the target, cap and format that worked. A shop adding products every week, or a photographer delivering a gallery every weekend, should get the same look from every batch, and reusing the exact settings is the quickest way to get it. For the most common portal limits, the 200 kB preset and 100 kB preset pre-fill the target.

If the destination is an inbox rather than a website, the limits are stricter. Our guide to image compression for email attachments works through the per-message caps of the major services and how many photos fit under each.