Image Compressor
A camera photo is often three or four megabytes. On a website it needs to be a few dozen kilobytes. Drop them here and they're resized and re-encoded on your own device — nothing is uploaded.
1600px covers almost any website use. Images are never enlarged.
75 is usually indistinguishable from the original on a screen.
Drop images here
Up to 20 at a time. They stay on your device.
Re-encoding is lossy, so keep your originals — this is for the copy that goes on the website, not your only copy. The browser also drops all metadata in the process: that removes GPS coordinates from phone photos, which is usually a good thing, but it also removes the colour profile and any copyright field.
Why it matters
Not a framework, not a tracking script — a product shot straight off a phone at full resolution, being downloaded in full and then displayed four hundred pixels wide.
The fix is unglamorous: make it the size it actually gets displayed at, and encode it properly. That is most of what image optimisation is, and it costs nothing.
If the website audit flagged your page weight, this is usually the first thing to try. If the page is still slow once the images are sensible, the problem is further in — hosting, database queries, or too much script — and that's development work.
Common questions
No. The compressing happens inside this page — your browser decodes, resizes and re-encodes the file, and nothing is sent. The only network request the page makes is the same anonymous page-view counter as every other page on this site, and it happens whether or not you add an image.
Because it was already well compressed, and re-encoding an optimised file usually costs more than it saves. When that happens the tool says so on the row and gives you the original back rather than a worse version of it.
Quality, a little, because re-encoding is always lossy — so keep your originals; this is for the copy that goes on the site. All metadata goes too: EXIF, camera settings, the colour profile, any copyright field, and GPS coordinates. Losing the location out of a phone photo before it goes public is usually a win. Losing a colour profile can shift a wide-gamut photo slightly.
WebP, unless something in your workflow refuses it. It's meaningfully smaller at the same visual quality and every current browser reads it. JPEG is there for older software and for anyone who needs maximum compatibility.
Still slow?
If the page still drags once the photos are sensible, something further in is the cause — and guessing at it is expensive.
Fixed price agreed before work starts. No hourly billing, no surprises.
