Image resizer: the right size for the page, not the camera.

The mistake is almost always the dimensions, not the compression

People reach for a compressor when a page is slow, and the compressor helps. But the larger saving usually comes before compression, in the pixel dimensions. A photo straight from a phone is often several thousand pixels wide. If the page displays it at 800, most of those pixels are downloaded, decoded and then thrown away by the browser.

Resize first, to about twice the width it displays at, and compress second. The order matters because compression settings that look fine on a huge image can look soft once it is scaled down, and the reverse.

What this tool does with your file

It opens the image in the browser, draws it onto a canvas at the size you choose, and asks the browser to encode it in the format you pick. Large reductions are done in halving steps rather than one jump, which keeps edges cleaner than a single resample. Transparent areas become white in JPEG because the format has no transparency. If your browser cannot encode a format, the tool says so rather than silently handing you something else.

Before you upload it

A resized file is only half of the image work on a page. The other half is the markup: a descriptive file name, alt text that says what the image shows for anyone who cannot see it, and explicit width and height attributes so the layout does not jump while it loads. Those, and the rest of the page-level basics, are on the SEO checklist.

If you manage images across many client sites, the same reasoning applies at scale: find the templates that serve full-size uploads into small slots, and fix the template once rather than every image.