Are my images uploaded?

No. Decoding, resizing and re-encoding all happen in your browser using the Canvas API. Nothing is transmitted or stored.

What width should I use?

1600 pixels covers full-width images on most designs, including on high-density screens where the browser wants roughly double the CSS width. If your images sit in a narrow column, 1000 is plenty and will be noticeably lighter.

Does this hurt SEO or quality?

The opposite. Page speed is a ranking factor and images are usually the heaviest thing on a page. At 200 KB and 1600 pixels the difference is invisible on screen and substantial on load time.

Get your images ready for a website

Runs in your browser

Drop your photos in below. Each one is downscaled to a sensible display width, converted to WebP, compressed under 200 KB and packaged as a ZIP.

Drop images hereor click to choose — nothing is uploaded

Dimensions matter more than compression

A phone photo is typically 4000 pixels wide. A website rarely displays anything above 1600, and a blog column is often 800. Serving the original means the browser downloads several megabytes and then throws most of the detail away during scaling. Resizing first is the single biggest win available, and it costs nothing visually.

Why WebP

WebP produces files roughly 25–35% smaller than JPEG at equivalent visual quality, and every current browser supports it. AVIF is smaller again, but browsers cannot reliably encode it locally, so producing AVIF would mean uploading your images to a server — a trade we are not willing to make.

A privacy side effect

Because each image is decoded and re-encoded, EXIF metadata is discarded along the way. Camera model, timestamps and any GPS coordinates from the original photo do not survive into the optimised file. If you want to see what was in there first, use the EXIF viewer.

Serve the right size, not just a smaller one

Optimised files still need sensible markup around them. Set explicit width and height attributes so the browser reserves space and the page does not jump as images arrive — layout shift is both irritating and a measured ranking signal. Add loading="lazy" to anything below the fold so it does not compete with content the visitor can actually see. If your theme supports srcset, generating a second narrower version for phones is the next meaningful win after this one.

FAQ

Are my images uploaded?: No. Decoding, resizing and re-encoding all happen in your browser using the Canvas API. Nothing is transmitted or stored.
What width should I use?: 1600 pixels covers full-width images on most designs, including on high-density screens where the browser wants roughly double the CSS width. If your images sit in a narrow column, 1000 is plenty and will be noticeably lighter.
Does this hurt SEO or quality?: The opposite. Page speed is a ranking factor and images are usually the heaviest thing on a page. At 200 KB and 1600 pixels the difference is invisible on screen and substantial on load time.

The tools behind this

Doing this regularly? The Website Image Optimization recipe runs the whole job in one pass.