Image Compressor

Related tools

A single photo from a modern phone can weigh 8–15 MB — fine for your camera roll, a nightmare for an email attachment, a slow website, or a form that caps uploads at 2 MB. This guide explains what image compression actually does, when you need it, and how to get a smaller file without a visibly worse photo.

How image compression actually works

Most photos use lossy compression: the format throws away detail the human eye barely notices — subtle color gradients, fine texture — to shrink the file dramatically. JPG does this by splitting the image into small blocks and simplifying the color information in each one; push the quality slider down and it simplifies more aggressively. WebP uses a newer, more efficient version of the same idea, which is why it typically produces a smaller file than JPG at the same visual quality.

PNG works differently: it's lossless, meaning every pixel is preserved exactly. That's why PNGs of photos are so much larger than JPGs of the same photo — there's a ceiling to how much a lossless format can shrink a busy, colorful image, no matter the settings.

When you actually need a smaller file

• Email attachment limits. Gmail and Outlook cap attachments around 25 MB total — three or four uncompressed phone photos can hit that ceiling fast.
• Website speed. Oversized images are the single biggest cause of slow-loading pages, which hurts both visitor experience and search ranking (Google's Core Web Vitals directly measure how long images take to load).
• Upload limits on forms. Job application portals, government sites, and insurance claim forms often cap uploads at 2–5 MB per file.
• Storage. If your phone or cloud plan is full of full-resolution photos you just want to share, not print, compression buys back space without deleting anything.

Choosing JPG, WebP, or PNG

For ordinary photos, JPG is the safe universal choice — every device, app, and website accepts it. WebP usually produces the smallest file for the same visual quality, and virtually every modern browser supports it, but a handful of older apps still don't — check before you rely on it. Only reach for PNG when you specifically need transparency (a logo, an icon) or pixel-perfect accuracy (a screenshot with small text); for regular photos it's the wrong tool, since it can't compress them nearly as much.

Getting the best result

1. Start from the original file, not a copy you've already compressed. Compressing a JPG that's already been compressed stacks quality loss on quality loss.
2. Resize before you compress if the photo is much bigger than you'll ever display it (see our Image Resizer) — fewer pixels to encode means a smaller file at the same quality setting.
3. Try WebP first if you just need the smallest possible file and don't know of a compatibility requirement forcing JPG.
4. Compare at 100% zoom, not thumbnail size — compression artifacts that are invisible in a small preview can show up once someone views the full image.

Frequently asked questions