You’ve got 400 product photos that need to be 800×800 for your Shopify store. Or maybe 2,000 vacation shots that are eating your hard drive alive. Opening each one in Photoshop? That’s a full workday gone. Batch image resizers exist specifically for this problem, and honestly, the free ones have gotten surprisingly good.
I spent about two weeks testing 19 different batch resizing tools – desktop apps, browser-based tools, command-line utilities. Threw the same set of 500 mixed-format images (JPG, PNG, WebP, TIFF) at each one and tracked speed, output quality, and how much they actually compress without turning photos into pixel soup.
| Tool | Platform | Max Batch Size | Formats | Speed (500 imgs) | Best For |
|---|---|---|---|---|---|
| IrfanView | Windows | Unlimited | 70+ | 48 sec | Power users, fastest processing |
| XnConvert | Win/Mac/Linux | Unlimited | 500+ | 55 sec | Cross-platform, most format support |
| FastStone Photo Resizer | Windows | Unlimited | 30+ | 52 sec | Simple bulk resize + rename |
| BIRME | Browser | ~200 | JPG, PNG, WebP | 90 sec | Quick browser-based resizing |
| Squoosh CLI | Any (Node.js) | Unlimited | JPG, PNG, WebP, AVIF | 62 sec | Developers, automation scripts |
| ImageMagick | Any (CLI) | Unlimited | 200+ | 70 sec | Server-side, scripting |
| RIOT | Windows | Unlimited | JPG, PNG, GIF | 58 sec | Optimization-focused resizing |
| Bulk Resize Photos | Browser | ~150 | JPG, PNG, WebP | 110 sec | Zero-install quick jobs |
How I Tested These Tools
I didn’t just resize a couple of images and call it a day. The test set included 500 images: 200 JPEGs from a Canon R5 (each around 25MB), 150 PNGs with transparency, 100 WebP files, and 50 TIFFs. Total folder size was about 8.5 GB.
For each tool I ran the same operation: resize all images to 1200px wide (maintaining aspect ratio), output as JPEG at 85% quality. I measured wall-clock time, checked output file sizes, and did visual comparisons on a sample of 20 images at 200% zoom to spot compression artifacts.
One thing that surprised me – the speed differences between tools were way smaller than I expected. The real differentiators turned out to be UI workflow, format support, and how well each tool handles edge cases like images with embedded color profiles or unusual aspect ratios.
1. IrfanView Batch Conversion – The Speed King
IrfanView has been around since 1996. It looks like it, too. The interface is stuck somewhere in the Windows XP era, with tiny buttons and menus that go four levels deep. None of that matters because this thing is absurdly fast.
The batch conversion dialog (File > Batch Conversion/Rename) lets you add entire folders, set output dimensions, choose format and quality, and add watermarks or other effects. Processing 500 images took 48 seconds on my test machine (Ryzen 5 5600X, 32GB RAM, NVMe SSD). That’s roughly 10 images per second.
The “Advanced” options panel is where IrfanView gets interesting. You can crop, add canvas, sharpen, adjust colors, and apply custom filters – all in the same batch operation. I use the “auto-adjust colors” option for product photography batches and it saves me a separate editing step maybe 70% of the time.
What’s annoying about IrfanView
Windows only. No way around it – there’s no Mac or Linux version. The plugin system is confusing (you need separate plugin packs for some formats). And the batch dialog doesn’t show preview thumbnails, so you’re working blind until you hit Start.
The naming template system is powerful but cryptic. Want sequential numbering with zero-padding? You need to type something like image_### and just know that # means a digit placeholder. There’s no documentation visible in the dialog itself.
Price: Free for personal use. $12 one-time for commercial. The plugins pack is a separate free download.
2. XnConvert – Best Cross-Platform Option
If you need batch resizing on Mac or Linux, XnConvert is probably your first stop. It runs on all three major platforms, supports over 500 input formats (I couldn’t even find test files for most of them), and has a clean action-based workflow that makes complex batch operations actually manageable.
The way XnConvert works: you build a chain of “actions” in the middle panel. Resize, then rotate, then adjust brightness, then add watermark. Each action has its own settings and you can reorder them by dragging. It’s like a simplified Photoshop Actions panel but purpose-built for batch processing.
Processing speed was solid – 55 seconds for my 500-image test set. Not the fastest, but within 15% of IrfanView, and you get way more flexibility in how you chain operations together.
The profile system is underrated
You can save your entire batch configuration – input settings, action chain, output format – as a profile. I have profiles saved for “Shopify products” (800×800, white background fill, JPEG 90%), “blog thumbnails” (1200×630, JPEG 80%), and “social media” (1080×1080, PNG). Load the profile, drop the folder, hit Convert. Done in under a minute.
One thing I noticed: XnConvert handles color profiles better than most tools here. Images with embedded sRGB or Adobe RGB profiles get properly converted, which matters if you’re doing product photography where color accuracy counts.
Price: Free for personal use. Donations encouraged. Business license available.
3. FastStone Photo Resizer – Straightforward Batch Processing
FastStone is the tool I recommend to people who just want to resize a folder of photos without learning anything new. The interface is two panels: files on the left, output settings on the right. Pick your files, set dimensions, choose format, click Convert. That’s it.
The rename function is genuinely useful here. You can batch resize AND rename in a single pass – something that takes two separate tools in most workflows. The rename template supports date/time from EXIF data, so you can output files named like 2026-04-15_001.jpg automatically.
Speed was 52 seconds for 500 images. The output quality at JPEG 85% was visually identical to IrfanView’s output – I couldn’t spot differences even at 200% zoom.
Limitations worth knowing
Windows only, like IrfanView. Format support is decent (around 30 formats) but nowhere near XnConvert’s 500+. No action chaining – you can resize and rename, but you can’t add a sharpen step or color adjustment in the same pass. For pure resize-and-rename jobs it’s perfect. For anything more complex, look at XnConvert or IrfanView.
Price: Completely free. No commercial license needed.
4. BIRME (Bulk Image Resizing Made Easy) – Best Browser-Based Tool
BIRME runs entirely in your browser. No upload to any server – everything happens locally via JavaScript. This matters for privacy: your images never leave your machine. I verified this by running it with my network disconnected and it worked fine.
The interface shows thumbnail previews of every image with a crop overlay. You can adjust the crop position individually for each image before processing, which is something most batch tools can’t do. Need to make sure the subject is centered in each thumbnail? BIRME lets you nudge each crop point manually.
The catch: browser-based processing is slower. My 500-image test took about 90 seconds, and the browser started getting sluggish around image 300. I’d recommend keeping batches under 200 images for a smooth experience. For larger sets, split them into groups.
Another limitation – you can’t resize to a specific pixel width while maintaining aspect ratio AND output as a different format in a single operation. You pick dimensions OR format conversion, not both simultaneously. Minor annoyance but worth mentioning.
If you’re already using browser-based tools for image work, you might also want to check out our image compression tools roundup for the optimization step after resizing.
Price: Free. Open source.
5. Squoosh CLI – For Developers Who Script Everything
Squoosh started as Google’s browser-based image optimizer, and the CLI version lets you use the same compression engine from your terminal. It’s a Node.js package, so you need Node installed, but after that it’s one command to resize an entire folder.
Here’s what a typical batch resize looks like:
npx @squoosh/cli --resize '{width: 1200}' --mozjpeg '{quality: 85}' -d output/ *.jpgThat’s it. One line. No GUI to navigate, no buttons to click. For developers or anyone comfortable with the terminal, this is by far the fastest workflow once you’ve memorized the syntax.
Processing speed was 62 seconds for 500 images, which is mid-pack. Where Squoosh really shines is output quality – the MozJPEG encoder it uses produces noticeably smaller files at the same visual quality compared to standard JPEG encoding. My test batch averaged 23% smaller output files than IrfanView at identical quality settings.
AVIF and WebP support
Squoosh CLI handles modern formats natively. Converting a batch of JPEGs to AVIF or WebP is just a flag change. If you’re optimizing images for web delivery, this is a real advantage – AVIF files were 40-50% smaller than equivalent JPEGs in my tests with no visible quality loss.
The downside: Squoosh CLI has been in maintenance mode. Google hasn’t pushed major updates recently, and some users report issues with newer Node versions. It works fine on Node 18 and 20, but I hit a compatibility warning on Node 22. Not a dealbreaker, just something to be aware of.
Price: Free. Open source (Apache 2.0 license).
6. ImageMagick – The Swiss Army Knife
ImageMagick is what runs behind the scenes in about half the image processing pipelines on the internet. WordPress uses it. Most Linux distros ship with it. It can do literally anything to an image – but the learning curve is steep and the documentation reads like a reference manual, not a tutorial.
Basic batch resize command:
mogrify -resize 1200x -quality 85 -path output/ *.jpgThat processes files in place (mogrify) or to an output directory. Simple enough. But ImageMagick’s real power shows up when you need conditional logic – resize only if wider than 1200px, skip files smaller than 100KB, convert PNG to JPEG only if no transparency, and so on. You can script all of this.
Speed was 70 seconds for 500 images. Not the fastest, partly because ImageMagick uses a single thread by default. You can parallelize with GNU Parallel or xargs, which brought my time down to about 25 seconds on 6 cores. That makes it the fastest option here if you’re willing to write a slightly more complex command.
Developers working with image processing might also find our developer tools guide worth checking – several of those tools have image handling capabilities built in.
Price: Free. Open source (Apache 2.0 license).
7. RIOT (Radical Image Optimization Tool) – Optimization-First Resizing
RIOT takes a different approach. Instead of treating resize as the primary operation, it’s primarily an optimization tool that happens to include resizing. The main interface shows a side-by-side comparison: original on the left, optimized version on the right, with a quality slider between them.
This visual comparison is actually really useful for finding the sweet spot between file size and quality. You can drag the quality slider and instantly see where artifacts start appearing. For my test images, I found JPEG quality 82 was the breaking point for most photos – below that, sky gradients started showing banding.
Batch mode processes 500 images in about 58 seconds. The output files were consistently 10-15% smaller than IrfanView’s at the same perceived quality, thanks to RIOT’s more aggressive metadata stripping and its custom JPEG encoder.
The metadata angle
RIOT strips EXIF data by default, which is what you want for web images (smaller files, no GPS coordinates leaking). But if you’re processing personal photos, make sure to toggle the “Keep EXIF” option or you’ll lose your camera settings, dates, and location data. I learned this the hard way with a batch of travel photos.
Price: Free. Closed source but no ads or bundleware.
8. Bulk Resize Photos – Zero-Install Web App
Bulk Resize Photos is the simplest option here. Go to the website, drag in your images, pick a resize option (by percentage, longest edge, exact dimensions, or file size target), and download the ZIP. Like BIRME, processing happens locally in your browser.
The “resize to target file size” option is unique among the tools I tested. Need every image under 500KB for an email campaign? Set 500KB as the target and Bulk Resize Photos automatically adjusts quality per image to hit that target. Some images compress better than others, so a fixed quality setting gives you wildly different file sizes – this adaptive approach solves that problem.
Speed was the slowest at 110 seconds for 500 images, and I wouldn’t recommend batches over 150 files. The browser tab will eat RAM – my test peaked at about 4GB for the full 500-image batch. But for quick jobs of 50-100 images? Perfectly fine, and you don’t need to install anything.
Price: Free. Premium version ($7.99 one-time) removes the ~150 image limit.
Which One Should You Actually Use?
Look, this depends entirely on your situation:
You’re on Windows and want speed: IrfanView. It’s ugly but nothing touches it for raw processing speed. Install the plugins pack and you’ll handle any format thrown at you.
You’re on Mac or Linux: XnConvert. It’s the only cross-platform desktop tool here that’s actually good. The action chain system is worth learning – it’ll save you hours once you set up profiles for your common tasks.
You just need to resize 50 images right now: BIRME or Bulk Resize Photos. No install, no signup, no privacy concerns. Open the browser and go.
You’re building an automated pipeline: ImageMagick for maximum flexibility, Squoosh CLI if output quality and modern format support matter more than scripting power.
You care about file size optimization: RIOT. The visual quality comparison alone is worth downloading it for. Pair it with your resize workflow and you’ll get the smallest possible files without visible quality loss.
For related workflows, our guides on free photo editors and file converter tools cover the editing and format conversion steps that often follow batch resizing.
FAQ
Does batch resizing reduce image quality?
Any JPEG re-encoding introduces some quality loss because JPEG is a lossy format. At quality 85% or above, the loss is invisible to most people in normal viewing conditions. If you’re resizing PNGs to PNG, there’s zero quality loss since PNG is lossless. For the best results, resize from original source files rather than previously compressed copies – each re-encoding compounds the quality loss.
What’s the fastest free batch image resizer?
IrfanView processed 500 mixed-format images in 48 seconds in my testing, making it the fastest single-threaded option. ImageMagick with GNU Parallel was faster at 25 seconds but requires comfort with command-line tools. For browser-based options, BIRME handled 200 images in about 35 seconds.
Can I batch resize images without installing software?
Yes. BIRME and Bulk Resize Photos both run entirely in your browser with no installation needed. Your images are processed locally using JavaScript – nothing gets uploaded to external servers. The tradeoff is slower processing speed and practical batch limits around 150-200 images before the browser tab gets sluggish.
What’s the difference between resizing and compressing images?
Resizing changes the pixel dimensions of an image (e.g., from 4000×3000 to 1200×900). Compressing reduces file size by adjusting encoding quality or stripping metadata without changing dimensions. Most batch resizer tools do both simultaneously – when you resize and save as JPEG at 85% quality, you’re resizing and compressing in one step. For compression-only workflows, check out dedicated image compression tools.
Is ImageMagick safe to use?
ImageMagick has had security vulnerabilities in the past (the “ImageTragick” exploit in 2016 was a notable one). The project has improved its security posture significantly since then with a hardened default policy file. For local desktop use with your own images, it’s perfectly safe. If you’re using it on a server to process user-uploaded images, make sure you’re running a recent version (7.1+) and have the security policy configured properly.