Set exact pixel dimensions, scale by percentage, or resize to fit. Lock aspect ratio. Batch resize your whole library. All in your browser.
Resizing an image means changing its pixel dimensions — the actual width and height of the grid of pixels that make up the picture. This is different from compression, which keeps the dimensions the same but reduces file size by simplifying pixel data. Resizing is what you need when an image is the wrong physical size for where it's going: too large for a web page layout, too small for a print job, or not matching a platform's required dimensions.
Most resizing needs fall into two categories. Exact pixel dimensions are needed when a specific platform or layout demands a precise size — a 1200×630px image for a social media share card, a 2000×2000px square for a product listing, or a 1920×1080px banner for a website hero section. Percentage scaling is better when you just want to shrink or enlarge an image proportionally without hitting a specific number — for example, reducing a batch of photos to 50% of their original size to save space while keeping their relative proportions identical.
Aspect ratio is the relationship between an image's width and height — a photo that's 4000×3000px has the same ratio as one that's 800×600px (4:3). If you resize only the width without adjusting the height to match, or vice versa, the image gets stretched or squashed, which is immediately noticeable to viewers. Locking the aspect ratio means that changing one dimension automatically recalculates the other to keep the proportions correct, so faces, logos, and straight lines don't end up distorted.
Different platforms expect different sizes. Website hero images typically work best around 1920×1080px or 2560×1440px for retina displays. Product photos for online stores are commonly resized to a square format like 1000×1000px or 1500×1500px. Profile pictures across most platforms are square as well, usually between 400×400px and 800×800px. Email newsletter images are often kept narrower, around 600px wide, to avoid being scaled down awkwardly by email clients.
If an image looks the right size on screen but the file itself is too large in megabytes, that's a job for compression, not resizing — shrinking the dimensions of an already correctly-sized image just makes it blurry or too small to use. If the image's physical dimensions don't fit where you need to place it — too wide for a sidebar, too small for a banner — that's when resizing is the right tool. Many workflows use both: resize first to the dimensions you need, then compress to bring the file size down further.
Usually, yes — making an image smaller in pixel dimensions also reduces its file size, since there's less pixel data to store. But for the most control over file size specifically, use the Image Compressor after resizing, or combine both settings as needed.
If you set a width and height that don't match the image's original proportions, the image will be stretched or squeezed to fit those exact dimensions, which usually looks distorted. Keep the lock on unless you specifically need a non-proportional crop.
Yes, the tool supports scaling up as well as down. Keep in mind that enlarging a low-resolution image beyond its original size can make it look soft or blurry, since the tool has to generate new pixel data rather than just removing it.
No. All resizing happens locally in your browser using the HTML5 Canvas API. Your files are never sent to a server.
Batch resizing applies the same target dimensions or percentage to all selected images at once. If you need different sizes for different images, run them through separately.