Kit — image resize

Image resize

Set a long edge, a width, a height or a percentage and resize a batch of images at once. The aspect ratio is always kept, the reduction happens in steps so edges stay clean, and phone photos come out the right way up.

Choose imagesClick to choose, or drag and drop. JPEG, PNG, WebP, GIF and more

Whichever edge is longer becomes this value, portrait or landscape. Common choices: 1920 (full HD), 1600, 1200, 800.

Stretching a small image adds no detail — it only softens the edges. On by default.

"Keep original" preserves JPEG, PNG and WebP. Formats a browser cannot write (HEIC and friends) become PNG if they might carry transparency, JPEG otherwise.

Add images and their original dimensions will appear here.

This runs entirely in your browser. Nothing is uploaded.

Related tools

QR code generatorImage metadata removerWord & character countJSON formatter & validatorAll tools

What this one does differently

Steps down instead of jumping

A single canvas draw from full size to a quarter or less loses thin lines and text and leaves diagonal edges crawling. This reduces by no more than half per pass, so every source pixel reaches the result.

Photos stay upright

Phone cameras store landscape pixels plus an EXIF rotation flag. Decoding without that flag produces sideways output from a file that previews correctly everywhere else. The flag is applied first.

Nothing is uploaded

Reading, resizing and encoding all happen in the page. Photos of people, unreleased artwork, internal documents — none of it needs a decision about where it is being sent.

Choosing the settings

How is resizing different from compressing?Resizing changes the pixel count. Compressing keeps the pixel count and encodes it more coarsely. For a requirement stated in pixels — "no wider than 1200px" — use this. For one stated in bytes — "under 1MB" — /compress (Compact) is the better fit.
JPEG or WebP?WebP is smaller than JPEG at a comparable look and it keeps transparency. JPEG opens absolutely anywhere. Pick WebP for the web, JPEG when you do not control what will open the file or when a printer asked for it.
How many pixels do I actually need?It depends on where the image will be seen. For a web page or an email attachment, a long edge of 1200–1920px is usually plenty. Print is specified by density rather than dimensions, and around 300dpi at final size is the usual expectation — an A4 page at that density is roughly 3500px on its long edge.
What does 50% actually remove?Each edge is halved, so a quarter of the pixels remain. The file shrinks roughly in step with the pixel count, though the exact figure depends on the format and the picture.

Questions

How many images at once?

There is no fixed limit. They are processed one at a time with a running count. Very large images in large numbers will use a lot of memory on a modest device, so the page may feel slower.

Are my images stored?

No. Everything happens in the browser and nothing is sent to a server. Closing the page discards whatever was loaded.

Will a transparent PNG turn black as a JPEG?

No. JPEG cannot hold transparency, so transparent areas are filled with white before encoding. If you need a different background or want to keep the alpha channel, choose PNG or WebP instead.

Can it enlarge?

Turn off "Never enlarge" and it will scale up to whatever you ask for, but detail that was not captured cannot be invented — the result is simply softer. The option is on by default.

Does it handle HEIC from an iPhone?

It works wherever the browser can decode HEIC, which Safari can. Other browsers often cannot, and in that case the row says so and the remaining files still run.