Step 1
Open [Bulk Image Resizer](/tools/bulk-image-resizer).
Loading workspace...
Preparing your tools
Guide
Learn how to bulk resize JPG, PNG and WebP images online, preserve aspect ratio, choose dimensions, and process an image batch consistently.
Resizing one image is easy. Resizing a folder of product photos, screenshots, headshots, or website assets one by one is where the work becomes repetitive. A bulk image resizer applies one resize rule to a whole batch so the output stays consistent.
CodeStorms Bulk Image Resizer accepts JPG, PNG, and WebP images and lets you set a maximum width, height, or both. When you provide only one dimension, the tool preserves the original aspect ratio automatically.
Open [Bulk Image Resizer](/tools/bulk-image-resizer).
Add the JPG, PNG, or WebP images you want to process.
Set the target width, height, or both.
Review the selected files and dimensions.
Run the resize job.
Check the results and download each resized image individually when processing finishes.
If the images also need consistent framing, crop them before resizing. The image cropping guide explains how to choose the area and aspect ratio to keep; then use Crop Image before applying one resize rule to the full batch.
Batch resizing is a good fit when you need to:
If you only have one file, use Resize Image. For a folder or batch, open Bulk Image Resizer.
On the Free plan you can resize up to 3 images per run, with a 10 MB limit per input image. Pro supports up to 20 images per run, with the same tool-specific 10 MB per-file limit. Upload JPG, PNG or WebP files; GIF input is not supported. After processing, download individual resized images, or use the automatically generated ZIP when several output images are produced.
For most website work, setting only a maximum width is the safest option. For example, if a 4000 × 3000 photo only needs to display at 1200 pixels wide, set the width to 1200 and let the height scale proportionally.
Setting both width and height is useful when your destination expects a fixed bounding box. Review the result if source images have different aspect ratios because forcing two dimensions can change how the final image fits the layout.
Resizing changes pixel dimensions. Compression reduces file size. They solve different problems.
A practical web workflow is:
Use Image Compressor after resizing when page weight matters.
Batch resizing scales images so they fit within a maximum width and height; it does not force every image into a square crop or invent extra pixels. If you need identical subject framing for product listings or team headshots, crop the originals before applying a shared resize limit. If you have an animated GIF, this workflow does not accept it. JPG, PNG and WebP images are supported, and resized outputs retain their input formats.
For website speed, resize oversized images first, then compare file size and appearance before deciding whether to use an additional compressor. A larger image file is not automatically a higher-quality visual.
Continue your workflow with these matching tools.
Related, practical walkthroughs for the tools used in this guide.
Compress web images with source-aware settings, compare visual quality and output bytes, and check transparency and real Core Web Vitals.
Read the guide →
Compress JPG, PNG and WebP images for faster websites. See a real before-and-after test, understand quality, and learn when to resize first.
Read the guide →
Learn how to preview an image online, check dimensions, file type and metadata, and inspect image files without converting or editing them.
Read the guide →
Upload your file and apply these settings in under a minute.
Yes. The Bulk Image Resizer processes a batch of supported images with the same resize settings in one run.
When you set only one dimension, the other dimension is calculated proportionally so the original aspect ratio is preserved.
The current bulk workflow accepts JPG, PNG, and WebP images.