Drop your images
Drag in one or many — they are resized on your device, never uploaded.
Resize
Batch-scale by pixel size or percentage with the aspect ratio locked — free, unlimited, and nothing is ever uploaded.
Drop images to resize
PNG · JPG · WEBP · AVIF — batch supported, nothing uploaded
How it works
Drag in one or many — they are resized on your device, never uploaded.
Fit the longest side to a pixel width, or scale by a percentage. Aspect ratio is kept.
Grab each image or the whole batch as a zip — optionally converted to a modern format.
What it is good for
Shrink camera photos to a sensible width so pages load fast.
Meet size limits without fiddly external tools.
Batch-scale a folder of images to a consistent size in one pass.
"Resize" and "lose quality" get tangled together, but they are not the same thing. Shrinking a photo — going from a 4000-pixel camera original down to something a web page can use — keeps almost all of its sharpness when it is done well. The quality loss people worry about usually comes from the wrong tool, the wrong direction, or a second compression step further down the line. Here is how to get a clean result every time.
Making an image smaller throws away pixels you did not need, and a good downscaling filter blends the remaining ones so edges stay crisp. This tool uses a high-quality Lanczos filter for exactly that reason. Making an image larger is the opposite problem: there is no extra detail to add, so a plain resizer just stretches what is there and the result looks soft. That is why enlarging is switched off by default. If you genuinely need more pixels — a tiny logo, an old thumbnail — reach for an AI upscaler, which reconstructs edges and texture instead of stretching them.
You can fit the longest side to an exact pixel width, or scale everything by a percentage. Use a pixel width when you have a specific target in mind:
Reach for percentage scaling when you have a batch of mixed sizes and just want everything uniformly smaller — say, every image at 50% — without picking a number for each one.
Resizing and format are two separate choices, and the format often matters more for file size. WebP is the best default for photos — typically 25–35% smaller than JPG at the same visible quality. Keep PNG for graphics with sharp edges or transparency, and fall back to JPG only when an older tool needs it. Our PNG to WebP guide walks through when each one wins.
Resizing changes the dimensions; it does not re-compress the image. A photo scaled to 1600px is already far smaller, but if it still needs to be lighter, run it through a compressor as a second step — that is where you trade a sliver of quality for a large drop in bytes. The two tools stack cleanly: resize for the right dimensions, compress for the right weight. The guide to reducing file size covers the full workflow.
Every resize here runs locally in your browser with WebAssembly. Your images are never uploaded, there is no account, and there is no limit on how many you process — drop a whole folder and download the batch as a zip. For the full walkthrough with worked examples, read Resize an image without losing quality.
Every resize runs locally with WebAssembly. No servers, no uploads, no accounts — your images stay private by design.
Downscaling uses a high-quality Lanczos filter, so results stay crisp. Enlarging is off by default to avoid blur.
For most blog and article images, fit the longest side to 1600px — sharp on high-resolution screens without wasting bytes. Full-width hero images can go to 2000px; inline thumbnails are fine at 400–800px.
A resizer cannot invent detail, so blowing a small image up just makes it soft. If you need more pixels, use an AI upscaler instead — it reconstructs edges and texture rather than stretching them.
WebP is the best default: 25–35% smaller than JPG at the same quality. Keep PNG only for graphics with sharp edges or transparency, and use JPG when you need maximum compatibility with older tools.
Resizing changes the pixel dimensions, not the compression. A 4000px photo scaled to 1600px is much smaller, but if it is still heavy, run it through a compressor to trade a little quality for a big size drop.
Yes — drop a whole batch. Every image is scaled with the same rule and zipped together in one pass.
Always. You set the longest side or a percentage, and width and height scale together — no stretching or squashing.
No. Resizing runs entirely in your browser with WebAssembly — nothing leaves your device.