Preparing a folder of photos for a website or a social feed usually means three separate jobs. Here you resize, change format and compress in a single pass, see exactly how much space you saved and take everything home in one ZIP file.
Processing locally on your device
Overview
Each image goes through the same three-stage pipeline. First it is resized, using exact pixel dimensions with an aspect-ratio lock, a percentage from 5% to 400%, or a preset such as Instagram square (1080×1080), Instagram Story (1080×1920), YouTube thumbnail (1280×720), Full HD or 4K. The “don’t enlarge” option leaves images that are already smaller than the target untouched, which avoids blurry upscaling. If you only want to convert or compress, resizing can be switched off entirely.
Next the image is encoded in the output format you choose: keep the original format, or convert to JPG, PNG, WebP or AVIF (AVIF appears only when your browser can encode it). JPG has no transparency, so you choose a background color for any transparent areas. Finally, lossy formats are compressed with a quality slider. As a general rule, a quality of 75–85 gives a large size reduction with differences that are hard to spot, while PNG output is lossless and ignores the slider.
All of this happens on a canvas inside your browser, so files are never uploaded. Results update automatically whenever you change a setting, and the list shows each file’s original and new size along with the total saved across the batch. A before/after comparison lets you check quality on a real image before you commit, and you can download files one by one or as a single ZIP. Resizing is usually the biggest win: halving both dimensions cuts the pixel count by 75%, and a 4000×3000 phone photo resized to 1920 pixels wide and saved as WebP at quality 80 often drops from several megabytes to a few hundred kilobytes.
| Preset | Dimensions | Aspect ratio | Typical use |
|---|---|---|---|
| Instagram square | 1080 × 1080 | 1:1 | Feed posts |
| Instagram Story | 1080 × 1920 | 9:16 | Stories, Reels covers |
| YouTube thumbnail | 1280 × 720 | 16:9 | Video thumbnails |
| Full HD | 1920 × 1080 | 16:9 | Website hero images, slides |
| 4K UHD | 3840 × 2160 | 16:9 | Large displays, wallpapers |
Add images by dropping them onto the page or choosing files.
Set the resize mode (pixels, percent or a preset), or switch resizing off.
Choose an output format and, for JPG, a background color for transparent areas.
Adjust the quality slider and check the before/after comparison and size savings.
Download individual files or all of them as a ZIP.
Use cases
Resize a shoot of 50 product images to a consistent 2048-pixel square, convert to WebP and compress, so product pages load quickly without visible loss of detail.
Turn a set of camera photos into 1080×1080 Instagram posts or 1080×1920 Stories in one go, ready to schedule.
Shrink images to 1600 pixels wide and WebP before uploading, keeping your media library small and your Core Web Vitals scores healthy.
Scale a holiday album down to 50% and save as JPG at quality 80 so dozens of photos fit under a typical 25 MB attachment limit.
Pro tips
Answers to common questions about the batch image processor.
Always resize first, then convert to the chosen format, then compress with the quality setting. You can switch resizing off if you only need conversion and compression.
AVIF appears only when your browser can encode it on a canvas. If your browser cannot, use WebP, which is supported for encoding in all modern browsers and is still much smaller than JPG.
PNG is lossless, so the quality slider has no effect, and re-encoding a heavily optimized PNG can produce a slightly larger file. Resize it, or convert to WebP, for real savings.
Images smaller than the target are kept at their original size instead of being scaled up. Larger images are still reduced to fit the preset.
Presets define the target size; with pixel mode you can lock the aspect ratio so only one dimension needs to be entered. Check the before/after view to confirm the framing is what you want.
No. ToolEnhancer processes files on your own device inside the browser. They are never sent to, stored on or seen by our servers.
Yes. The batch image processor is free to use with no sign-up, no watermarks and no daily limits.