Resize Image

Because two boxes look simpler and work worse. People arrive already knowing which constraint they care about: "no wider than 1920", "exactly 300 across", "half size". A bare width/height pair makes you compute the other number yourself, and a small error there breaks the aspect ratio. Naming the constraint makes the answer exact the first time.

Because enlarging cannot add detail — it stretches the pixels you already have, and the result is soft. But it is not forbidden: sometimes you genuinely need "exactly 1000px wide" for a template or a marketplace, and a tool that quietly hands back 600px has ignored your request rather than protected you. So upscaling is a visible checkbox you turn on yourself, and we tell you when your current numbers would need it.

With the lock, the whole image is fitted inside the box you specified without cropping anything, so it may end up smaller than one of your two numbers. Without it, both numbers are obeyed literally and the image is stretched. Cropping to fill the box exactly is the Crop tool's job — doing it silently here would mean eating part of your image without telling you.

Because the arithmetic runs on numbers rather than pixels, so there is no reason to make you press a button to find out whether you asked the right question. The final dimensions are shown live as you change anything — including the case people are most often surprised by: "this will not change anything".

Yes, by default. A PNG stays a PNG, because otherwise its transparency would be lost to a decision you did not ask us to make. You can change the format from the list if you want, and formats a browser cannot write (GIF, BMP) come out as PNG when they have transparency and JPEG when they do not.

Orientation is applied to the pixels before processing, so phone photos do not come back lying on their side the way they do on many other sites. The rest of the metadata — GPS, camera model — is removed by the re-encode.

No. Everything happens inside your browser — the image never leaves your device, and there is no daily usage limit.

Yes. Choose any number of images (up to 20, and up to 200 MB combined) and the same constraint applies to every one of them — each image reaches that same limit (longest edge, exact width, percentage...) based on its own real dimensions. The results come back as a single ZIP archive.

Because images in one folder are rarely all the same source size, so one number claiming to answer for all of them would be a guess dressed up as a fact. The live figure represents the first image as a reference; each image gets its own real calculation when the batch actually runs, shown in its own result row.

Each image is decoded on its own, so decode memory never grows with the batch — but every result accumulates in memory before the archive is built. 20 images and 200 MB combined keeps the tool running smoothly on any device.