Skip to main content
Free Image Tool

Image Resizer

Resize a JPEG, PNG, or WebP image to exact dimensions or scale to fit a max width while preserving aspect ratio.

  • Free · no sign-up
  • Instant results
  • Privacy-friendly

Choose an image, set target dimensions, and click Resize. Output downloads in the same format as the input.

Other Image Tools

How to resize without distorting the image

Give a width, a height, or both, up to 8000 pixels on either side. With aspect ratio preserved — the default, and the setting you almost always want — supplying one dimension lets the other follow automatically, so the image scales cleanly with nothing stretched.

Turning that off lets you force exact dimensions, which will squash or stretch the picture if the target shape does not match the original. That is occasionally what you need for a strict template slot, but if the goal is filling a fixed frame without distortion, cropping is the correct tool rather than an unlocked resize.

Downscaling is safe, upscaling is not

Making an image smaller discards pixels and looks good, because the detail being removed was more than the new size can show. Making it larger cannot invent detail that was never captured. A conventional upscale spreads existing pixels across a bigger canvas, producing a soft, slightly mushy result that gets worse the further you push it.

The practical rule is to work from the largest original you have and scale down to each size you need, rather than scaling one small copy up. If you genuinely must enlarge, keep it modest — beyond about 150 percent the softness becomes obvious to anyone looking.

What size do you actually need?

The most common mistake is publishing images at camera resolution. A phone photo is often 4000 pixels wide; a blog column displays maybe 800. Those extra pixels cannot be seen, but every visitor downloads them.

Useful starting points:

  • Blog and article images — 1200 to 1600 pixels wide covers full-width layouts and still looks sharp on high-density screens.
  • Product photography — 1000 to 2000 pixels square, larger only if you offer zoom.
  • Full-width hero images — 1920 pixels wide is ample; 2560 only if you specifically target large desktop displays.
  • Thumbnails and avatars — 400 pixels or less. Serving a 2000-pixel image into a 150-pixel circle is pure waste.
  • Open Graph and social previews — 1200 by 630 pixels, the standard both Facebook and X expect.

Retina screens and the 2× rule

High-density displays pack roughly twice the physical pixels into the same space, so an image displayed 800 pixels wide can look soft unless the file is around 1600 pixels wide. The usual compromise is to export at twice the display size and compress a little harder — the extra resolution hides compression artefacts well, so the combination often costs no more bytes than a larger, gently compressed file.

For a proper solution, serve several sizes and let the browser choose with the srcset attribute. That way a phone downloads a phone-sized image instead of a desktop one, which is one of the most effective page-weight improvements available.

Resize first, then compress

Order matters. Compressing a 4000-pixel image and then resizing it wastes the compression work and re-introduces artefacts at the new size. Resize to the dimensions you will actually display, then compress once. That sequence produces the smallest file at the best quality, and it is the single biggest lever on Largest Contentful Paint, which Google uses as a ranking signal.

Frequently asked questions

Will resizing make my image blurry? #
Making it smaller will not — that discards detail the new size could not show anyway. Making it larger will, because the missing detail cannot be invented. Always scale down from the largest original you have rather than scaling a small copy up.
How do I resize without stretching the image? #
Keep the preserve aspect ratio option on and set just one dimension; the other follows automatically. Distortion only happens when you force both width and height to a shape the original does not have.
What size should images on my website be? #
Roughly the size they display at, doubled for high-density screens. For most blogs that means 1200 to 1600 pixels wide. Serving a 4000-pixel photo into an 800-pixel column makes every visitor download about twenty-five times more data than they can see.
Should I resize or compress first? #
Resize first, then compress. Compressing before resizing throws away the compression work and reintroduces artefacts at the new size. Resizing is also the larger saving of the two by a wide margin.
Why does my image look soft on a MacBook or modern phone? #
High-density screens pack about twice the physical pixels into the same area, so an image displayed at 800 pixels wants roughly 1600 actual pixels. Export at twice the display size and compress slightly harder to offset the file size.
What is the difference between resizing and cropping? #
Resizing scales the whole image to new dimensions. Cropping cuts away part of it, changing the composition. To fit a fixed frame whose shape differs from your image, crop — an unlocked resize would distort it.
Is my uploaded image kept? #
No. It is held only long enough to produce the resized file you download, then discarded. Nothing is stored or indexed.