free tool, no sign-up

Website Image Compressor

Enter your website and this tool finds every image on it, shrinks each one right in your browser, and shows you exactly how much lighter your site could be. Then download them all as a zip.

Settings(2000px max · quality 80 · WebP)
Compression settings

Never upscales smaller images.

80 is a good balance.

Other formats become WebP.

Why image size matters

Images are usually the heaviest thing on a small business website. A single photo straight from a phone or camera can be 4 to 10 MB, and a page with a dozen of them can take several seconds to load on mobile data.

That matters because visitors leave slow pages, and Google measures how long your biggest visible element takes to appear (Largest Contentful Paint, one of its Core Web Vitals). On most sites, that element is an image.

Resizing images to the size they're actually shown at and saving them as WebP often cuts their weight by 70 to 90 percent with no difference you can see.

How it works

  1. 1

    Enter your site

    The tool reads your homepage and sitemap (up to 25 pages) and finds every image: photos, backgrounds, social share images and icons.

  2. 2

    Compress in your browser

    Each image is resized to 2,000px wide at most and saved as WebP at quality 80. It all runs on your device, so nothing is uploaded or stored.

  3. 3

    Download and replace

    Grab a zip of the smaller files, then swap them in on your site. The guides below show where to do that on each platform.

How to replace images on your platform

The tool detects which platform your site is built with and grabs the original upload, not the resized copies the platform makes. Here's where to swap in the smaller files.

Replacing images on Squarespace

Squarespace makes its own resized copies of whatever you upload, but they're all made from your original, so a heavy original means heavier pages everywhere.

  1. Open the page in the editor and click the image block.
  2. Click the pencil (edit) icon, then hover over the image and choose Replace.
  3. Upload the compressed file and save. Background images live under the section's Edit Section → Background.

Replacing images on Wix

Wix serves images through its own CDN and converts them on the fly, but very large uploads still slow down the first load and the mobile site.

  1. In the Wix Editor, click the image and choose Change Image.
  2. Click Upload Media and add the compressed file.
  3. Select it, click Choose Image, then Publish. Strip and section backgrounds are under Change Strip Background.

Replacing images on WordPress

WordPress (5.8 and newer) supports WebP. It creates smaller sizes for themes, but many themes still load the full-size original in places like hero sections.

  1. Go to Media → Add New and upload the compressed files.
  2. In the block editor, select an image block and click Replace, then pick the new file from the Media Library.
  3. To swap files without editing every page, a plugin like Enable Media Replace keeps the same URL.

Replacing images on Webflow

Webflow generates responsive variants (the -p-500, -p-800 files) from your upload. This tool fetches the original, since that's the file every variant comes from.

  1. Open the Assets panel and upload the compressed files.
  2. Select an image on the canvas, open its settings and choose Replace Image.
  3. For CMS images, open the collection item and upload the new file in the image field, then publish.

Replacing images on Framer

Framer resizes images for each breakpoint, but it still starts from your upload, and large originals add up across a whole site.

  1. Select the image layer (or the frame with an image fill).
  2. In the right panel, click the image under Fill and upload the compressed file.
  3. For CMS collections, replace the image in each item, then Publish.

Replacing images on Showit

Showit serves resized copies of your uploads, but large originals still slow things down, and its separate desktop and mobile layouts can each use different images.

  1. In the Showit app, open the page and click the image on the canvas.
  2. In the right panel, click the image to open the Media Library, upload the compressed file, and select it.
  3. Switch to the mobile view and check the same spot, since it can use a different image. Then Publish.

Replacing images on Next.js

next/image optimizes images on request, but huge source files cost more optimization time and usage, and the first visitor waits for it.

  1. Replace the files in your public/ folder (or wherever your images live) with the compressed versions.
  2. If the extension changed to .webp, update the src paths in your components.
  3. Commit and deploy. For images from a CMS, re-upload them there.

Platform won't accept WebP? Open Settings in the tool, choose Keep original, and run it again to get compressed JPEGs and PNGs.

Questions

Something else on your mind? Text me and I'll get back to you.

Is this image compressor really free?

Yes. There's no sign-up and no limit beyond a few scans a minute. It's free because the heavy lifting happens in your own browser.

Are my images uploaded to a server?

No. Our server only reads your pages to find image addresses. Your browser downloads, resizes and compresses each image itself. If a site blocks direct downloads, the image passes through a small relay that streams it to you without saving it.

Why WebP?

WebP files are usually 25 to 35 percent smaller than JPEGs at the same visual quality, and every modern browser supports them. If your platform won't accept WebP, open Settings and choose Keep original to get compressed JPEGs and PNGs instead.

Will compression make my photos look worse?

At quality 80 and 2,000 pixels wide, most people can't tell the difference on a website. That's wider than almost any layout displays an image. You can raise the quality in Settings if you want to be extra careful.

Why didn't it find some of my images?

The tool reads your pages and your site's own code, so it also finds images hidden behind buttons like "See more". It can miss images your site loads from somewhere else while someone browses (some booking widgets, Instagram feeds and pop-ups), images set in separate CSS files, pages beyond the first 25, and anything behind a login or bot protection.

What does "already optimized" mean?

Compressing that image would have made it bigger, so the tool leaves it alone. It isn't included in the zip because there's nothing to replace.

Why are SVGs and animated GIFs skipped?

SVGs are vector graphics and are usually tiny already. Animated GIFs would lose their animation if converted this way, so they're listed but left untouched. For big animated GIFs, a short MP4 or WebM video is usually much smaller.

Want your whole site sped up?

Images are one piece. I can swap them in for you, fix the rest of what's slowing your site down, or build you a faster one. Get in touch.