Batch Process Images in Your Browser, No Desktop Software

Sooner or later you have a folder of forty photos that all need the same treatment: shrunk to fit a website, converted to a format a form will accept, or stamped with a name. Doing that one file at a time is slow and easy to get wrong. Installing a full desktop editor for a one-off job can feel like overkill.

Browser-based batch tools sit in the middle. They handle a set of images with one shared setting, without an install and without uploading the files anywhere. This guide covers when batch beats one-by-one, how to plan a run, what the four bulk image pages here actually do, and where they run out of road.

When batch beats one-by-one

Batch processing pays off when the same rule applies to every file. Good candidates:

• A product or gallery set that needs one consistent size.
• A folder of photos that must be under a size limit for email or a web form.
• A mix of PNG, WebP and other files that must all become JPEG or PNG for one destination.
• A set of images that all need the same visible mark.

It is a poor fit when each image needs a different decision, such as a different crop, a different caption or different quality. In that case a one-by-one tool such as Image Resizer gives you more control per file.

Plan the batch before you start

A few minutes of planning avoids running the batch twice.

• Decide the target size or outcome. For example, everything fits inside 1600 by 1200 pixels, or every file is under a size you can email.
• Decide the output format. If the destination accepts only JPEG, convert first and resize after, or the reverse, but be consistent.
• Decide on names. The tools name each result after the original file, with the extension of the output format. If your files are called IMG_0001.jpg and so on, they stay that way, which is usually what you want.
• Keep the originals. Work from a copy of the folder. Re-encoding an already re-encoded file compounds quality loss, so always start from the source files.

What the four bulk pages do

All four run in your browser and the files are not uploaded. Each accepts image files and up to 100 at a time, and each applies one setting to the whole set.

A few details from the code that matter in practice:

• With aspect ratio kept, the resize page fits each image inside the width and height you enter. It can also enlarge a smaller image to reach that box, so check for images that were already small. If you untick the option, every image is stretched to exactly the numbers you typed, which distorts photos that have a different shape.
• The resize page keeps each file's own format, going by the file extension. A file type it does not recognise comes out as PNG.
• The compressor keeps PNG, JPEG and WebP as they are and turns anything else into JPEG. PNG stays lossless, so the quality slider mainly affects JPEG and WebP. For the theory behind that, see lossy vs lossless image compression, and for realistic expectations, how much can you compress an image.
• AVIF output depends on your browser. Most browsers cannot encode it, and the tool reports an error instead of quietly giving you something else. Choose JPEG or WebP if that happens.
• The watermark font size is a single number of pixels. On a batch that mixes very large and small images, the same mark will look proportionally bigger on the small ones.

If part of your batch is iPhone photos in HEIC, the tools can usually open them, and the guide to converting HEIC photos from iPhone explains what to expect.

How results are delivered

The delivery depends on how many files you add. Put in one image and you get that one image back as a normal download. Put in two or more and everything is packed into a single ZIP file. Inside, each result is named after its original with the new extension, so photo1.png converted to WebP becomes photo1.webp. The ZIP itself takes its name from the first file you added.

One thing to watch: if two input files share the same name, for example two files called cover.jpg gathered from different folders, the ZIP can hold only one of them under that name and the later one replaces the earlier. Rename such files before you start.

The files are processed one after another, not all at once, and a progress message shows which image the tool is working on.

Browser memory limits

The browser has to decode each image into raw pixels before it can change it. A decoded image needs roughly four bytes per pixel, so a 6000 by 4000 photo, which is 24 megapixels, takes about 96 MB in memory while it is being handled, even if the file on disk is only a few megabytes. Handling images one at a time keeps that manageable, but the finished results also accumulate, and the final ZIP is built in memory before you can download it.

For a large batch of large photos that can add up, and on a phone or an older laptop the tab may slow down, show an error or crash. The practical remedy is chunking:

• Split a big folder into smaller groups, for example 20 to 30 photos of large size, and more for small web images.
• Run each group, download its ZIP and unpack it into the same output folder.
• Close other heavy tabs while you work.

There is no exact safe number, because it depends on your device and the size of the pictures. If a run fails, halve the group and try again.

Verify the results

Do not assume the batch succeeded because a ZIP appeared. Unpack it and check:

• The count matches the number of files you put in.
• Open the smallest, largest and oddest images. Look for stretched proportions, watermark placement and visible compression damage.
• Sort the folder by size and confirm the files are actually smaller if you compressed.
• Confirm the file extensions are the format you intended.

Where desktop tools still win

Be realistic about the limits. A browser batch tool has no scripting and no saved recipes. It applies one setting to the entire batch, with no per-file rules such as different sizes for portrait and landscape images. It cannot rename by pattern, sort into folders or run several steps in one pass. If you routinely process hundreds of files with varied rules, a desktop tool or a script is the right choice.

For the common one-off job, though, the rule of thumb is simple. Pick one goal, run a small test batch of three or four images, look at the output, then run the full set in chunks that your device can handle.