Image Resizer

Type the width you need and, with the lock on, the height follows automatically at the original aspect ratio. That is what you want almost always — it is how you avoid the squashed look of an image forced into the wrong shape.

Unlock the ratio when you genuinely need a fixed frame and are willing to distort the picture, or when you are resizing something like a texture where proportions do not matter.

The preset buttons cover the widths that come up most: 1920 for full-width hero images, 1280 for in-article images, 800 for blog bodies, 400 for thumbnails.

Shrinking is safe. Throwing pixels away is a well-defined operation and the browser does it with high-quality smoothing, so a downsized image looks clean.

Enlarging is not. There is no extra detail to recover, so scaling a 400px image up to 1600px gives you a soft, blurry version of the same picture at four times the file size. If you need a bigger image, go back to the original source rather than upscaling.

The one exception is when you need exact dimensions for an upload that rejects anything smaller. In that case upscaling is a formality, not an improvement.

JPG for photographs — smallest files, no transparency. PNG for logos, screenshots and anything with sharp edges or transparency. WebP when the image is for a website, since it is typically 25 to 35 per cent smaller than JPG at the same visual quality.

The resizer re-encodes at high quality, so a resized JPG will not visibly degrade in a single pass. Repeatedly resizing and re-saving the same JPG will accumulate artefacts, so work from the original each time where you can.

No. The resize happens through the Canvas API inside your browser. There is no server, no queue and no account, and the image data never leaves the tab.

It also keeps working offline once the page has loaded.