Local browser processing

Resize multiple images in one private batch

Apply one maximum width, height, format, and quality policy to as many as 20 images. Files are processed sequentially and packaged into a ZIP inside this browser tab.

How it works

01

Choose 2–20 images

Select JPG, PNG, or WebP files under the per-file and aggregate browser limits.

02

Set shared bounds

Choose maximum width and height, output format, quality, and whether smaller images may upscale.

03

Verify and download

Review every measured output and download one locally assembled ZIP with collision-safe names.

What stays private here

  • Each source image is decoded and encoded sequentially in this browser tab.
  • The finished ZIP is assembled locally and is never uploaded to Peelaway.
  • Analytics receive only aggregate counts, dimensions, formats, quality, and byte sizes.
  • No filename, directory path, image pixel, object URL, or archive byte reaches analytics.

Questions about this tool

Will every image have exactly the same dimensions?

No. Each image keeps its proportions and fits inside the shared maximum width and height. Portrait and landscape sources can therefore finish at different dimensions.

Does the batch resizer enlarge small images?

Not by default. You can explicitly allow upscaling, but interpolated pixels cannot restore detail that is missing from the source.

What happens to transparent pixels?

PNG and WebP can retain transparency. JPEG cannot, so transparent areas are flattened onto white before encoding.

Are the images or ZIP uploaded?

No. The browser decodes and encodes one image at a time, then assembles the ZIP locally. Peelaway analytics receive only aggregate counts, dimensions, formats, and byte sizes.

Need to change what is in the image?

Test Peelaway's production workflow for supported object removal, background removal, and prompt-driven image changes.

Open the image editor