Resize Image
Change image dimensions. Everything runs locally, nothing is uploaded.
Pixels, not inches
Resizing changes the pixel grid; it does not change physical size. A 3000-pixel-wide photo is 10 inches at 300 pixels per inch and 30 inches at 100, and both files are identical. Print workflows care about pixels per inch; screens care only about pixels. Deciding which one you are serving first avoids the common mistake of upscaling a web image to "300 dpi" and gaining nothing but file size.
Downscaling is safe, upscaling is invention
Removing pixels is a well-defined averaging problem: each output pixel summarises a block of input pixels, and the result looks clean. Adding pixels is not — the software has to guess what was between the samples. A 2× upscale looks acceptable at a glance and soft at full size; beyond that, edges turn to mush. If the source is too small, re-shoot or re-export rather than upscale.
Keep the aspect ratio locked unless you intend to distort. Cropping and resizing are different operations, and forcing dimensions that do not match the ratio stretches faces in a way that is immediately obvious.
Questions that come up
Is the image uploaded anywhere? No. The resize happens on a canvas in the browser and the file never leaves the device.
Which format should I save? JPEG for photographs, PNG for anything with text or transparency, WebP when file size matters more than compatibility.
Why did my PNG get larger? Re-encoding a lossless format at a different size creates new data; the compression gains do not survive resampling.
Does resizing keep the photo's metadata? The canvas re-encodes the image, so EXIF data — camera model, GPS coordinates, capture time — is dropped. That is usually desirable for anything published, and worth knowing if you needed the timestamp preserved.