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 converted on your own device, to the format and file size you need. Nothing is uploaded.
75 is usually indistinguishable from the original on a screen.
For upload forms with a limit. We lower the quality step by step, then the size, and tell you if a file still won't fit.
Drop images here
JPEG, PNG, WebP, AVIF, GIF, BMP, and HEIC or TIFF where this browser can open them. Up to 30 at a time. They stay on your device.
Re-encoding is lossy (except plain PNG), 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.
For photos on a website, WebP: meaningfully smaller than JPEG at the same visual quality, and every current browser reads it. AVIF is smaller again but not every app opens it yet, and not every browser can make it, so it only appears where yours can. JPEG is for email and older software. For logos, icons and screenshots, use Smaller PNG: it cuts the image to 256 colours or fewer, keeps transparency, and is often a fraction of the size.
Yes. Tick "Aim for a file size" and type the limit. The tool lowers the quality step by step, then the dimensions, until each image fits, and says so plainly when one still won't without being wrecked.
iPhones save HEIC by default, and only Safari can open HEIC in a web page. Open this page in Safari and it works there, or switch the iPhone to Settings, Camera, Formats, Most Compatible so it saves JPEG.
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.
