Image Tools

Compress, resize, or convert?

These three get confused constantly and solve different problems. Resizing changes the pixel dimensions and is what you want when an image is physically larger than the space it will ever occupy — a 4000px photo in a 800px column is wasted bandwidth no matter how well it compresses. Compressing keeps the dimensions and lowers quality to save bytes, which is the right move when the size is correct but the file is heavy. Converting changes the format: WebP and AVIF are dramatically smaller than JPEG or PNG at similar quality. For a photo that is too big in every sense, resize first, then convert, then compress — in that order, because each step shrinks the work the next one has to do. The Image Cropper changes composition rather than size, and the Color Picker from Image pulls exact hex values out of a screenshot or photograph.

Choosing a format

Use JPEG for photographs when compatibility matters most and WebP when it does not — WebP is typically 25–35% smaller at visually equivalent quality and is supported by every current browser. Use PNG only when you need lossless detail or genuine transparency, such as a logo or a UI screenshot; a photograph saved as PNG is usually several times larger than it needs to be. Remember that every lossy save is permanent, so keep an original and re-export from it rather than repeatedly compressing the same file.

Your photos never leave the device

These tools use the browser's own canvas and image APIs, so the file is read from disk into memory and processed there. Nothing is uploaded, which is the practical difference when the image is a passport scan, a medical document, a screenshot of an internal dashboard or a photograph of your children. It also means there is no file-size ceiling imposed by an upload limit — you are bounded only by your own device.