How do I keep the image from stretching?

Leave "Lock aspect ratio" ticked — when you change the width, the height updates automatically (and vice versa) so the image never distorts. Untick it to set an exact custom width and height.

What format does it output?

A PNG, which preserves quality and any transparency. You can then compress it with the Image Compressor if you need a smaller file.

Yes — resizing happens in your browser with a canvas; nothing is uploaded.

How do I resize an image in inches?

Images are stored in pixels, so inches depend on DPI: pixels = inches × DPI. For print at 300 DPI, a 2×2 inch photo is 600×600 px; for screens at 96 DPI it is 192×192 px. Work out the pixel size and enter it as the width and height above.

What is a 2 inch photo size in pixels?

At 300 DPI (print quality) a 2×2 inch photo is 600×600 pixels, and a 2×2.5 inch photo is 600×750. At 96 DPI (screen) it is 192×192. Enter the matching pixel dimensions above to resize to a 2-inch photo size.

What is the difference between resizing and compressing — does resizing change the file size?

Resizing changes the dimensions (width × height in pixels), which usually shrinks the file too. Compressing keeps the dimensions but lowers the file size by reducing quality. For the smallest file, resize first here, then run it through the Image Compressor.

Free Tool

Image Resizer

Resize any image to exact pixel dimensions in your browser — lock the aspect ratio or set custom width and height, then download. Nothing is uploaded.

Exact pixel sizes
Runs in your browser
Nothing uploaded

Drop an image here, or click to upload

JPG, PNG or WEBP · max ~20MB

Page speed

Send the pixels you actually display

Oversized images are a common cause of a slow page. A 4000px image shown in an 800px slot still downloads all 4,000 pixels — the browser scales it visually, and the visitor still waits for the full file.

This brings them down to the size you really display them at, in your browser, before they ever reach a page.

The rule that matters

Resize to the size it will be displayed at, then compress. Getting those two the wrong way round is a common mistake, and it wastes most of the benefit.

Compressing first only shrinks pixels you were going to throw away.
A 4000px wide photo in an 800px column carries 25 times the pixels it needs — five times the width, five times the height.
The visitor waits for every one of them before seeing anything.

The same photo, two ways

As supplied

Pixels4000 x 3000

Displayed at800px

Wasted25x the pixels

3.8MB

Resized first

Pixels800 x 600

Displayed at800px

WastedNone

210KB

The visitor waits for every pixel in the left column, then sees the same thing. Resizing closes that gap.

Common sizes worth knowing

You rarely need to guess. Most slots on a site fall into a handful of widths, and matching them is usually enough.

Measure the slot in your browser’s inspector rather than guessing — it takes ten seconds and settles the argument.
Double the width only if you are specifically serving retina screens, and accept the file size that comes with it.
Anything wider than your page container is wasted, always.

Typical display widths

Full-width hero

1920px

Content column

800px

Card thumbnail

400px

Avatar

150px

Measure the slot, match the width. Anything beyond your container width is downloaded and then discarded.

Resize, compress, confirm

Three steps, and the third is the one people skip. It is easy to optimise a file that was never the bottleneck and conclude the work did not help.

Set the width it will actually be shown at, then download.
Shrink the file further with the Image Compressor with little visible drop in quality.
Re-run the page and check the speed actually moved.

In this order, every time

1Resize to the display sizeThe step that removes the most bytes.
2Then compress what is leftQuality setting of your choosing.
3Confirm on the real pageRe-run it and check the number moved.

Pixels removed, 4000px to 800px96%

Your photos never leave your browser

The resizing happens on your own device. No upload, no queue, no sign-up, and no server-imposed file size limit.

Your images are not sent anywhere while you use it.
Client work and unreleased product shots can go in without going anywhere.
Nothing to delete afterwards, because nothing was uploaded.

Where your image goes

parix.ai/free-ai-tools/image-resizer/

Your photo stays here

nothing sent

Parix.ai serverNever contacted while you resize.

The short version

Four numbers worth keeping

25x

The pixels wasted by a 4000px photo in an 800px slot.

800

px suits most content columns, which is narrower than people expect.

Steps, in order: resize, then compress. Never the reverse.

101

Free tools on Parix.ai, none of them behind a sign-up.

Free, and staying free

Why Parix.ai gives this away

We build fast sites for a living, and oversized images are the first thing we fix on almost every site we inherit. These tools are the same checks we run for clients, put on a public page — which is why there is no paywall and no sign-up.

Resize an image

Who uses it

Anyone fixing a slow page, and anyone handed a folder of camera-resolution photographs that need to go on a site this afternoon.

Do it in order

Resize here, compress with the Image Compressor, then confirm with the Free SEO Audit.

When images are not the problem

If the page is still slow once the images are right, the audit will say what is actually holding it up, and our web development team fixes the rest.