Summary
The free image compressor re-encodes your JPEG, PNG and WebP files in your browser, tries the lighter format for each one (WebP when it wins) and keeps whichever file is smallest. Nothing is uploaded. Start at the default quality of 80%, compare the result at full size, then resize your images to their display width before publishing, because the tool keeps the original dimensions.
Want to go further? Ask
An image compressor makes the heaviest part of most pages lighter. On the median homepage, images weigh 1,054 KB on desktop and 900 KB on mobile, out of a total page weight of 2,652 KB and 2,311 KB (HTTP Archive, Web Almanac 2024, Page Weight). Google's own image guidelines say the same thing: images "are often the largest contributor to overall page size", which makes pages slow and expensive to load (Google Search Central, image SEO best practices).

How does the free image compressor work?
Drop one or several images on the tool, set the quality, and download the lighter files. Everything happens on your device: the browser reads each file, redraws it and encodes it again, so your images never travel to a server.
- Add your files: JPEG, PNG or WebP, up to 10 MB each. You can select several at once.
- Set the quality with the slider, from 10% (maximum compression) to 100% (maximum quality). The default is 80%.
- Read the report: the total saved, then one line per image with its final size, its dimensions and its output format.
- Download each file, or all of them in one click. Each name starts with "compressed-" so you never overwrite an original by mistake.
Move the slider after a first run and the tool compresses the same files again, which makes it quick to compare two settings.
Which format does the tool choose for each image?
It tests the candidates and keeps the smallest file. If no candidate beats your original, it keeps the original and says the image is already optimised.
| You upload | Formats tested | What you usually get |
|---|---|---|
| JPEG photo | JPEG and WebP at your quality setting | WebP in most cases, JPEG when it is smaller |
| PNG (logo, screenshot, transparency) | WebP at your quality setting and PNG re-encoded | WebP, which keeps transparency |
| WebP | WebP at your quality setting | A lighter WebP, or your original if it was already lean |
WebP wins often for a documented reason: Google measures WebP lossless files as 26% smaller than PNGs, and lossy WebP files as 25 to 34% smaller than comparable JPEGs at equivalent quality, with transparency supported in both modes (Google for Developers, WebP). Google Search indexes images in BMP, GIF, JPEG, PNG, WebP, SVG and AVIF, so a WebP file is safe for image search too.
What quality setting should you use?
Use 80% for photos and go lower only after checking the result at full size. The slider passes a quality value between 0 and 1 to the browser's encoder, the standard way browsers export lossy images (MDN, HTMLCanvasElement.toBlob()). Lower values remove more detail; the right level depends on what the image shows.
| Quality | Best for | What to check |
|---|---|---|
| 90 to 100% | Product close-ups, portfolio work, images users zoom into | Savings can be small; keep the original if the gain is marginal |
| 75 to 85% | Most photos: blog covers, hero images, team pictures | Faces and skin tones at full size |
| 60 to 70% | Background images, thumbnails, decorative visuals | Banding in skies and gradients |
| Below 60% | Very small previews only | Blur and blocky edges around text or logos |
Screenshots and images that contain text deserve a higher setting than photos: compression artefacts show first around sharp letters.
Why does image weight matter for SEO?
Because the main image of a page is often what Google times. The Largest Contentful Paint (LCP) measures when the largest visible element appears, and a good score is 2.5 seconds or less at the 75th percentile of page loads (web.dev, Largest Contentful Paint). On mobile, the LCP element includes an image on 68% of pages (Web Almanac 2024, Media).
Google recommends good Core Web Vitals "for success with Search", and says they align with what its core ranking systems seek to reward (Google, Core Web Vitals and Search). A lighter hero image is one of the most direct ways to improve your LCP.
Compression is not the whole story, though. Google's LCP guide explains that a smaller file shortens the download, but if the browser discovers or renders the image late, the time saved simply moves to another step (web.dev, Optimize LCP). Compress the file, then make sure the main image is in the HTML from the start and is not lazy-loaded.

How do you prepare images before compressing them?
Resize first, then compress. The compressor keeps the pixel dimensions of your file, so a 4,000 pixel photo displayed at 800 pixels still carries 25 times more pixels than the screen shows.
- Resize to the display size: about twice the width at which the image is shown is enough for sharp screens. A full-width blog cover rarely needs more than 1,600 to 2,000 pixels.
- Crop what does not help: empty margins cost bytes and attention.
- Compress at 80%, compare, adjust.
- Rename the file with a few descriptive words, such as "red-trail-running-shoes.webp", since Google says a short, descriptive file name gives it light clues about the image subject.
- Write the alt text when you insert it: see our glossary entry on alt text.
Re-encoding through the browser also leaves out the camera metadata stored in the original file, which removes a few more kilobytes from photos taken with a phone or a camera.
How heavy should an image be?
There is no official limit, but practical budgets keep pages fast. Use these targets as a starting point and measure the whole page with the page size checker.
- Hero or cover image: under 150 to 200 KB, since it often decides the LCP.
- Images inside an article: under 100 KB each.
- Thumbnails and logos: a few dozen KB at most.
- The whole page: compare it with the median above. Mobile inner pages carry 348 KB of images at the median, which shows how much lighter a well-built article can be.
Which mistakes cancel the benefit of compression?
Most of them happen after the compression step, when the image is placed on the page.
- Lazy-loading the main image. Nearly one in ten LCP images on mobile is lazy-loaded, an anti-pattern that makes pages much slower (Web Almanac 2024, Media). Keep
loading="lazy"for images below the fold. - No width and height attributes. Without them, the page jumps when the image arrives, which hurts layout stability.
- One large file for every screen. Serve smaller versions to phones with
srcset. - Compressing the same JPEG again and again. Each lossy pass loses detail. Keep a high-quality master and compress from it.
- Forgetting the CMS. Some platforms generate their own versions of every upload; check the file actually served, not the one you uploaded.
How do you keep every page light over time?
Make compression part of publishing, then audit regularly. Run the on-page SEO audit on your key pages to catch heavy images and missing alt text, and read our guide to image optimization for the full checklist.
If you publish often, automate the routine. The Sorank blog article generator writes and publishes illustrated articles on your site, and the GEO and SEO dashboard follows the Google traffic and AI visibility those pages earn.
Resize, compress at 80%, check at full size: that routine removes most of the weight from your pages. Drop your images in the compressor above, then see the Sorank plans to publish optimised content on autopilot.
































































































