Batch Image Resize

Practical limit is around 200 images per batch on a typical desktop browser. Memory and download throughput become the bottleneck above that. For thousands of images, batch in groups or use a desktop tool like ImageMagick or Sharp (Node.js) which run command-line and have no browser memory limits.

The image is scaled so its longest dimension equals the target value, with aspect ratio preserved. Setting longest side = 1200 means a 4000×3000 image becomes 1200×900 (landscape) or 900×1200 (portrait). Useful when you want a consistent maximum size regardless of orientation.

No — resizing produces new files; the originals on your computer are untouched. Each resized image downloads with its original name (or with a configurable suffix like '-1200' to avoid overwriting).

<strong>Fixed dimension</strong> for consistent output (e.g., 'all images max 1200px wide for the web'). <strong>Percentage</strong> for proportional scaling regardless of input size (e.g., '50% all sizes for thumbnails'). Pick whichever matches your goal — both are common.

Useful for size optimization: converting a folder of PNG photos to JPEG often saves 50–70% of bytes with no visible quality loss. Converting to WebP saves even more. Useful for compatibility: ensuring all output images are the same format makes downstream processing simpler.

No. Resizing happens entirely in your browser using HTML5 canvas. Even large batches of high-resolution images stay local. Memory grows with the largest image being processed; multi-MP images are fine on any modern device.