Drop images here or click to choose — JPG, PNG, WebP. Multiple files supported.
Free Image Compressor — Shrink JPG, PNG & WebP in Your Browser
Drop in any number of images and get them back dramatically smaller, usually with no visible loss of quality. Adjust the quality and width sliders and every image re-compresses automatically, showing exact before-and-after sizes. Nothing is uploaded — compression happens entirely in your browser.
Why image size is the fastest SEO win available
Images are usually the heaviest part of a page, and page weight drives load time directly. Google’s Core Web Vitals treat Largest Contentful Paint as a ranking signal, and on most pages the largest element is an image. Cutting a 4 MB photo to 300 KB can remove seconds from mobile load time — improving rankings and bounce rate without touching any code.
Choosing the right settings
- Quality 75–85% suits photographs. Most people cannot see the difference, but files shrink 60–80%.
- Quality 50–65% is fine for thumbnails and background images.
- Max width 1920px for hero images, 1200px for blog body images, 600px for thumbnails.
- Resize before compressing. Reducing dimensions saves far more than quality alone, which is why this tool does both in one pass.
A note on transparency
Output is JPEG, which has no transparency — transparent areas become white. That is the right trade for photos and screenshots. If you need to preserve a transparent background, keep the original PNG instead.
Also useful: our QR Code Generator and Word Counter, or read our tool reviews.
Resize first, compress second — the order matters
The largest saving available is almost never the compression setting. It is the dimensions. A 4000-pixel-wide photo displayed in an 800-pixel-wide column is carrying twenty-five times more pixel data than the screen can use, and no quality slider recovers that waste.
Work out the widest the image will ever actually display, double it for high-density screens, and resize to that before you compress. Going from 4000px to 1600px typically cuts the file by 80% or more on its own, and the visible result is identical because the extra pixels were never rendered.
Choosing the format
- JPEG — lossy, no transparency support. Still the right answer for photographs where transparency is not needed and maximum compatibility matters.
- PNG — lossless, supports full alpha transparency. Correct for logos, icons, diagrams, screenshots of text and anything with large flat areas of colour or hard edges. Wrong for photographs, where it produces enormous files for no visible benefit.
- WebP — supports both lossy and lossless modes and transparency, which makes it the only one of the three that covers every case. Google reports WebP lossless files as around 26% smaller than equivalent PNGs, and WebP lossy files as 25 to 34% smaller than comparable JPEGs at equivalent quality. Browser support is now effectively universal.
For most websites in 2026 the sensible default is WebP, with a JPEG fallback only if you must support genuinely ancient clients. The one place PNG still wins outright is an image that will be edited repeatedly, because lossless means no accumulated degradation.
Quality settings, and why re-compressing hurts
For JPEG and lossy WebP, quality between 75 and 85 is where almost all the useful trade sits. Below about 70, compression artefacts become visible in smooth gradients — skies, skin, out-of-focus backgrounds are where they show first. Above about 90 the file grows quickly for differences most people cannot see on a screen.
What is worth understanding is generation loss. Lossy compression discards information permanently. Compressing an already-compressed JPEG discards more, and the artefacts from the first pass become input to the second. Do this a few times and the image visibly degrades — the smearing you see in memes that have been screenshotted and re-shared repeatedly is exactly this effect.
The practical discipline: always keep an original, uncompressed or minimally compressed master, and compress from that master each time you need a new output. Never compress the compressed copy.
Metadata is a privacy problem, not just a file-size one
Photographs from phones and cameras carry EXIF metadata, and it frequently includes far more than people expect: precise GPS coordinates, the exact date and time, the device make and model, and sometimes serial numbers or the owner name set in the camera.
Publish an unstripped photo taken at home and you may have published your address to anyone who opens the file properties. Stripping metadata during compression removes that, and shrinks the file slightly as a bonus. This matters most for images of your home, your workplace, your children, or anything you would not want geotagged in public.
Why this is one of the highest-value performance fixes
Images are usually the largest asset on a page and very often the Largest Contentful Paint element — the specific thing Google measures to judge loading performance in Core Web Vitals. Compressing and correctly sizing images typically moves that metric more than any amount of script optimisation, and it takes minutes rather than days.
Two habits that compound the benefit: serve responsive sizes with srcset so phones do not download desktop-sized files, and add loading="lazy" to images below the fold so they do not compete with what the visitor sees first.
Frequently asked questions
Are my images uploaded to a server?
No. Compression happens entirely in your browser using the Canvas API. No image is transmitted, stored or logged, there is no upload limit, and you can load the page, disconnect from the internet and it still works. That makes it safe for client photographs, unpublished work and anything confidential.
What quality setting should I use?
Between 75 and 85 for JPEG and lossy WebP. Below 70 you start seeing artefacts in smooth gradients such as skies and skin; above 90 the file grows sharply for a difference most people cannot perceive on screen. Start at 80 and adjust only if you can actually see a problem.
Should I use WebP instead of JPEG or PNG?
For web use, usually yes. WebP handles both lossy and lossless compression and supports transparency, so it covers every case the other two do. Google reports WebP lossless as roughly 26% smaller than PNG and WebP lossy as 25 to 34% smaller than comparable JPEG. Browser support is now effectively universal.
Does compressing an image twice make it smaller?
Smaller, and visibly worse. Lossy compression permanently discards information, so a second pass discards more and compounds the artefacts from the first — this is generation loss. Always keep an uncompressed master and compress from that each time rather than re-compressing an output.
Does compression remove EXIF data from my photos?
Yes, and that is usually what you want. Phone and camera photographs commonly embed GPS coordinates, timestamps and device details, so publishing an unstripped image can expose your home or workplace location. Stripping the metadata removes that exposure and reduces the file size slightly at the same time.