Image Resize

No — it stays in your browser. Resizing runs on a local HTMLCanvasElement and the download is generated from a Blob in memory.

Use PNG for screenshots and graphics with sharp edges, JPEG for photos, and WebP when you want the smallest file size and modern browser support.

Browsers use bilinear/trilinear sampling for canvas scaling. For very large downscales, resize in two or three steps for sharper results.

Browsers cap canvas size, and the limit differs by browser and device; iOS Safari's, at roughly 4096×4096, is among the lowest. Very large images may fail silently or look truncated.

You can, but nothing is gained. Enlarging invents intermediate pixels by interpolating between the ones that exist, so the result is a softer version of the same detail at a bigger size, not a sharper picture. If you need genuine detail at a larger size, it has to come from a higher-resolution original.

Resizing keeps the whole picture and changes how many pixels describe it. Cropping keeps the pixel density and throws away the parts of the frame outside your selection. If the subject is too small in the frame, cropping is what you want; if the file is simply too big, resizing is.

Almost always the output format. Saving a photograph as PNG stores it losslessly, which for photographic content produces a file several times larger than the JPEG or WebP it came from, even at reduced dimensions. Choose JPEG or WebP for photos and keep PNG for screenshots, flat colour and transparency.