Compress Image for Website
Shrink your image to around 200KB for faster page loads and better Core Web Vitals.
Drag & drop your image here, or
Reduces width and height so the image stays sharp at the target file size.
Why 200KB for web images?
Images are usually the heaviest thing on a web page and the most common cause of a poor Largest Contentful Paint score. Around 200KB is a practical target for a full-width content image: light enough to paint quickly on mobile data, detailed enough to look sharp on a laptop screen. Thumbnails should be far smaller — 30–80KB is plenty. Think in terms of a total page budget rather than a per-image rule: one 200KB hero plus six 50KB thumbnails is a healthy page, whereas ten 200KB images is not.
What to expect at 200KB
Sensible targets by role on the page:
| Starting file | Typical result |
|---|---|
| Full-width hero image | 1600 × 900 px at around 200KB |
| Blog inline image | 1200 × 800 px, often under 150KB |
| Thumbnail or card image | 400 × 300 px, well under 50KB |
Always set explicit width and height attributes on your image tags. Compression fixes file size; only dimensions stop the layout jumping as images load.
How it works
- Select your file using the box above — it stays on your device.
- We compress it in your browser, adjusting quality and dimensions until it fits under 200KB.
- Download the result — your original file never leaves your device.
What to do next
- Resize to the right pixel dimensions first — it saves more than any quality setting. Compress JPG to 100KB →
Frequently asked questions
Should I use WEBP or AVIF instead of JPG?
WEBP is typically 25–35% smaller than JPG at the same visible quality and is supported everywhere that matters. Compress here, then convert the result. AVIF is smaller again but slower to encode and less consistent in older browsers.
Does compressing images improve Core Web Vitals?
It improves Largest Contentful Paint directly, since the LCP element is usually the hero image. It does not affect Cumulative Layout Shift — that needs width and height attributes — and it does not affect Interaction to Next Paint, which is a JavaScript problem rather than an image one.
What pixel width should the image actually be?
No wider than the largest space it will occupy, times two for high-density screens. A 700px content column needs a 1400px image, not a 4000px one. Resizing before compressing produces a far better result than compressing alone.
Should I compress images if my CMS already optimises them?
Check first — WordPress, Shopify and most modern platforms generate resized variants automatically. Compressing before upload is still worthwhile, because it lowers the starting size of every variant they generate.