IMAGE WORKFLOW

Batch resize photos: padding, quality, formats and ZIP download

DataWork Tools · November 6, 2026

Preparing product photos should not stretch the product or require uploading a private folder. This tool keeps the original aspect ratio, fits photos inside a box or adds padding to a fixed canvas, and bundles successful outputs into a ZIP. It does not remove backgrounds, retouch products or use generative AI.

Open the batch image resizer →

Example: put an 800×600 photo on a 1200×1200 canvas

  1. Load the demo images, or select your own JPG, PNG or WebP files.
  2. Set width and height to 1200, choose “Pad to exact size” and a white background. Leave upscaling off.
  3. The 800×600 photo stays at its original size, centered on a 1200×1200 canvas. Padding is 200 pixels on each side and 300 pixels at the top and bottom.
  4. Review dimensions, appearance and bytes. Download individual images or a ZIP of successful outputs.

Fit inside versus pad to exact size

Mode, 1200×1200 limit, upscaling off800×600 input
Pad to exact size1200×1200 output with an 800×600 image centered inside
Fit inside800×600 output without extra padding

Enable upscaling and the same image becomes 1200×900. Padding mode adds 150 pixels above and below; fit mode exports a 1200×900 image. Upscaling cannot restore missing detail. Neither mode crops or stretches your image.

Choose JPG, PNG or WebP

JPG is useful for photos but cannot store transparency. Choose a white background, or switch to PNG/WebP. The tool reports an error instead of silently flattening a requested transparent JPG.

PNG supports transparency. Its encoder does not use the lossy quality control, and a resized PNG can be larger than its source. WebP supports quality control and transparency when the browser can encode it. If an unsupported encoder falls back to PNG, the tool reports an error rather than giving a mislabeled file.

A quality setting of 85% is an encoder parameter, not a promised similarity score or an 85% reduction in bytes. There is no guaranteed target KB. Compare actual before/after file sizes. ZIP bundles the already encoded images; it does not promise further image compression.

Errors, cancellation and filenames

Unsupported or damaged images receive individual error messages while other files continue. The ZIP contains successful images only. A numbered prefix prevents duplicate source names from overwriting one another. Source files are never modified. Changing files or options, resetting or cancelling clears previous outputs so old downloads cannot be mistaken for a new run.

Limits and unsupported formats

Process 1–20 files, at most 10MB each and 40MB combined input. Each source must be at most 24 megapixels; each output side must be between 1 and 4096 pixels. Combined output is limited to 20MB. Exceeding that output limit clears the batch results: reduce dimensions, quality or file count and run again. On memory-limited phones, use smaller batches.

SVG, GIF, HEIC and RAW are not supported. Animated PNG/WebP are exported as the still frame decoded by the browser; animation is not retained. Original EXIF, GPS, camera settings and color profiles are not guaranteed to survive canvas re-encoding. Orientation follows the browser decoder, so inspect portrait photos and colors before publishing. Files and filenames are processed locally and are not sent to a server.

Review before uploading to a marketplace

  1. Check that the product is fully visible and its proportions are correct.
  2. Verify dimensions, background and actual bytes for each result.
  3. Compare success/failure counts, unzip the archive and inspect the outputs.
  4. Check your marketplace’s current image requirements separately. This tool does not guarantee marketplace approval.

Try the batch resizer → · Preparing a product catalog too? Use the CSV column editor or duplicate row remover.