Batch Image Resizer

Resizing thirty photos by hand is thirty chances to fat-finger a number. This page takes the whole set, applies one rule to all of them and hands back the results with their new dimensions listed, so you can see at a glance that every file came out as intended.

The rule is yours to pick: fit everything inside a box, give every file the same width, or scale everything by a percentage. The work runs on your device — the batch size is limited by the memory in your browser tab, not by an upload allowance or a paid tier.

1. 1Drop up to fifty images. Each file becomes a row in the queue. Duplicates of a file already in the list are ignored, and anything over the cap is reported rather than silently dropped.
2. 2Pick the resize rule. Fit in box, set width, or percentage. The same rule applies to every file in the batch.
3. 3Choose the output format. “Keep each” preserves the incoming formats. Pick one format instead and everything is written that way, with a shared quality setting for the lossy formats.
4. 4Run the queue. Files are processed one at a time — decoding several large photos at once is the fastest way to have the browser kill the tab. Progress, sizes and dimensions update as each finishes, and you can stop part-way.
5. 5Download. Take individual files from their rows, or the whole set as pixeleditor-resized.zip. The ZIP is built in the page from the finished files.

Fit in box

Give a maximum width and height; each image is scaled to fit inside both, keeping its own aspect ratio. The safest mode for mixed orientations. Defaults to 1600 × 1600.

Never enlarge

On by default in box mode. Images already smaller than the box keep their own size instead of being upscaled.

Set width

Every file gets exactly this width and the height follows its own ratio. Good for a uniform column of images; be aware that tall images will end up much taller than wide ones, which the tool warns about.

Percentage

Scales each image by the same proportion, whatever its starting size. 50 percent halves each side, so the pixel count drops to a quarter.

Output format

“Keep each” or one specific format for the whole batch. Formats are only offered after the browser proves it can encode them.

Quality

Applied to every lossy file in the batch; default 82. Hidden when the output is PNG, which is lossless.

• Fifty files per batch. Every decoded image needs width × height × 4 bytes of memory, so the cap protects the tab from being killed mid-run.
• One file at a time. Sequential processing is slower than parallel but far more reliable on phones and older laptops.
• One setting for the whole batch. Files needing individual treatment belong in the single-image resizer.
• Metadata is not carried across. Every output is written fresh, without EXIF, GPS or colour profile.
• Writing a batch of photographs as PNG makes the total larger, not smaller. The tool warns when PNG is selected.
• Individual images beyond roughly 100 megapixels are refused; that row reports the reason and the rest of the queue continues.

Forty 4032 × 3024 photos straight off a phone come to roughly 140 MB. In box mode at 1600 × 1600 with quality 82, each one lands around 250 KB to 450 KB and the total falls to somewhere near 14 MB — small enough to send in one go, large enough to look right on any screen. The readout shows the real before and after totals for your own files rather than these estimates.

If the goal is a byte budget rather than a pixel size, the batch compressor aims at a target in kilobytes instead. For one image with exact dimensions, the single resizer gives you more control per file.

• No upload wait

  Forty photos would be a long upload and a long download. Here there is neither — the files are already where the work happens.

• Per-file accountability

  Every row shows its output dimensions and size, so an odd result is visible immediately rather than discovered later.

• Failures stay contained

  A bad file marks its own row and the queue continues. You never lose a whole run to one corrupt image.

• One ZIP at the end

  Packaged in the browser from the finished files, so there is nothing to wait for and nothing stored on a server.

• Mixed batches handled properly

  Box mode gives portraits and landscapes the same maximum footprint without stretching or cropping either.

• No account, no watermark, no queue

  Nothing is limited by a plan. The only limit is the memory in your own tab, and it is stated plainly.

Nowhere. Each file is decoded, resized and re-encoded in this tab, and the ZIP is built here too. No upload request is made, nothing is written to local storage, a cache or a cookie, and the queue exists only in the page — reloading clears it.

The page sets no cookies and loads no analytics. The host that served it can log the page request, as every web host can; the Privacy Policy describes that and makes no broader claim.

PixelEditor is a small set of single-purpose image tools that run inside your web browser. Each one does a specific job — resize, crop, rotate, compress, convert, inspect, strip metadata — and each one has its own page so you can bookmark exactly the tool you keep needing.

The tools are built with the Canvas API and Web Workers. When you pick a file, the browser reads it from your own disk, works on it in memory, and hands you the result back as a download. There is no processing server involved, so there is no upload step, no queue, and no account.

Everything is free, there are no watermarks, and there is no paid tier that unlocks the real version. Read more about how PixelEditor works and why.