Image optimizer
Compress and convert photos in your browser. Batch upload or scan a website URL and fix the heavy images. JPG, WebP, AVIF.
Drag photos here or click to choose
JPG, PNG, WEBP · multiple files at once · photos stay on your device
Why you want lighter photos
A fast site is a better site. For your visitors, for Google, and for your own mobile data when posting on the go. The biggest gains live in your images, almost always.
Why WebP, and when JPG still wins
At the same visual quality WebP is about 25 to 35 percent smaller than JPG. Every modern browser supports it, and unlike JPG it has a lossless variant and transparency. For most photo sites WebP has become the standard.
When is JPG still the answer? When your photo needs to reach old mail clients, when your legacy CMS does not serve WebP, or when exporting to print. AVIF goes a step further in compression but takes longer to encode and only became practical on Safari relatively recently.
What quality numbers really do
A JPG or WebP at quality 80 is practically indistinguishable to the eye from the same photo at 95, while the file is often half the size. The difference is how much subtle detail compression discards, especially in smooth areas (sky, skin). At 60 you start to see it, at 50 it gets distracting.
Rule of thumb: 80 for web, 90 for portfolio or print master, 70 if you really want to squeeze for mobile. Always keep a high-quality master.
Pixels first, then compression
A 6000px photo displayed at only 800px on your site is waste. Before compression, scale your photo down to the size you actually need. That often saves more than compression itself. For most sites 1920px on the longest side is plenty.
EXIF, privacy, and orientation
Every photo your phone takes stores metadata. Camera make and model, lens, date, and on default settings also GPS coordinates. For public photos you usually want that gone. This tool strips it by default.
One thing we do carefully: the rotation flag in EXIF is read before stripping, and the photo is physically rotated. Otherwise a vertical iPhone photo would suddenly appear horizontal after stripping. A classic pitfall in naive tools.
The scan feature
Have a site and no idea which photos are too heavy? Paste the URL in the second tab. We fetch the homepage, parse the images out of the HTML (img, picture/srcset, lazy-load, og:image, and CSS background images), and check their file size. Anything over the 200KB threshold shows up in a list.
One click and the tool downloads those images through our server (bytes streamed, not stored), compresses them client-side in your browser, and hands you a ZIP with the optimized versions. No account, no upload from you, no logging of what we fetched for you beyond a counter for the daily limit.
Read further on this site
- Website checker: measures speed, image weight, and SEO basics.
- Aspect & crop: work out exactly how many pixels you need for a print size.
- Watermark generator: add your name or logo before exporting.
Image Optimiser: how it works
The Image Optimizer compresses and converts photos directly in your browser, with no server uploads involved. You can process individual files or enter a website URL to scan for oversized images. It comes in handy when your portfolio or client site feels sluggish and you want to find out exactly what is slowing things down.
Why image file size matters for web performance
A 4 MB photo works fine for printing, but on a webpage it forces the browser to download every one of those bytes before the page fully renders. Google factors loading speed into search rankings, and visitors on mobile connections feel it immediately. Portfolio homepages are a common culprit: a handful of unoptimized full-width images can add several seconds to load time.
The general guideline most web developers follow is to keep images below 200 KB, or below 500 KB for full-screen backgrounds. That sounds tight, but with the right compression settings the visual difference is minimal. If you want a broader picture of your site's technical health, the Photography Website Checker covers other performance factors as well.
Choosing the right export format
JPEG remains the default for web photos, but WebP typically produces files that are 25 to 35 percent smaller at comparable quality. Browser support for WebP is solid across all modern browsers. PNG is worth using when you need transparency, but not as a standard export format for photographs.
Because the tool runs entirely in the browser, your files stay local. That matters when you are working with client images you would rather not route through external servers. Set the quality level, pick the output format, and download the result directly.
Frequently asked questions
How much can I compress a JPEG before the quality loss becomes visible?
For most web use, 70 to 80 percent quality is a safe range. Images with flat color areas handle heavier compression better than shots with fine texture, noise, or sharp detail.
What is the difference between resizing and compressing an image?
Resizing changes the pixel dimensions, for example from 4000 to 1200 pixels wide. Compression reduces file size without touching the dimensions, by encoding the data more efficiently. For the web, you typically do both: scale down the dimensions and apply compression on top.
How do I find out which images on my website are too large?
Enter your website URL in the Image Optimizer and the tool scans the page to list all images along with their file sizes. You get a clear overview of which ones need attention without having to check each file manually.