Slim down hero images, blog graphics, and product shots for faster pages. Hit sensible size targets that keep Google's Core Web Vitals happy.
Drag & drop or click to upload
JPG, PNG, WebP up to 50MB
Target size: 512 KB per image — quality adjusts automatically.
Files are processed locally and never uploaded.
Drop your site images into the uploader above — processing stays in your browser.
Each image is automatically compressed toward ~0.5MB, a solid target for web use.
Download the results and replace the heavy originals on your site.
On a typical web page, images account for roughly half of all downloaded bytes — more than the HTML, CSS, and JavaScript combined. A single unoptimized 5MB hero photo can outweigh everything else on the page put together.
That weight is paid by every visitor: slower loads, higher bounce rates, and wasted mobile data. Compressing images is the highest-leverage performance fix on most sites, and it takes minutes.
Google's Core Web Vitals — the metrics that feed into search rankings — include Largest Contentful Paint (LCP), which measures how fast the page's main content appears. On most pages, the LCP element is an image: usually the hero.
This page targets around 0.5MB per image, a pragmatic ceiling for web slots. A hero compressed to half a megabyte paints dramatically faster than a 4MB original, and at typical display sizes visitors cannot tell the difference.
Different image slots deserve different sizes: a full-width hero might justify 0.5MB, a blog inline image rarely needs more than 200–300KB, and thumbnails can live under 100KB. One target doesn't fit all — but 0.5MB is a safe default ceiling before you fine-tune.
Dimensions matter as much as compression. Don't serve a 4000-pixel image in an 800-pixel slot; resize to the display size (or 2x for retina crispness) and use responsive srcset markup so phones download the small version. Compression and sizing multiply each other's gains.
Once your images are sensibly sized, the format is the next 25–35% of savings. WebP delivers JPEG-equivalent quality at roughly two-thirds the bytes, and every modern browser displays it natively.
Our WebP converter turns your compressed JPGs and PNGs into genuine .webp files in the browser. The practical workflow: compress here for size, convert there for format — or serve both with a picture-element fallback for maximum compatibility.
Two habits multiply what compression achieves. First, lazy-load below-the-fold images so they don't block the initial render. Second, always set explicit width and height attributes to prevent layout shift — another Core Web Vitals metric.
None of this requires a build pipeline or a paid CDN. Sensible sizes, modern formats, lazy loading, and stable dimensions cover the vast majority of image performance — everything else is diminishing returns.
Aim for under 500KB for heroes, 200–300KB for content images, and under 100KB for thumbnails. This page's 0.5MB target is a good default ceiling; fine-tune downward per slot from there.
The opposite: faster pages rank better. Google's Core Web Vitals explicitly reward fast-loading pages, and compressed images are the fastest route to a better Largest Contentful Paint score. Just keep descriptive filenames and alt text.
WebP is the safe default in 2026 — universal browser support and mature tooling. AVIF compresses slightly better but still has patchier support in editors and CMS pipelines. Compress to a sensible size first; the format choice is secondary.
Yes — drop in a batch and each image is compressed toward the 0.5MB target independently, downloadable individually or as a ZIP. For very large media libraries, repeat per folder; there's no daily cap.