Compress an Image
Shrink a JPEG, PNG or WebP until the file size makes sense, watching a live preview while you drag the quality slider. The encoder is the one built into your browser, so compression finishes in seconds and the photo itself never travels to a server. Free, with no account and no watermark.
Loading the tool…
How it works
- Drag your image onto the drop zone, or click to browse for it.
- Move the quality slider and watch the size readout and preview update.
- Optionally switch the output format to WebP for extra savings.
- Compare before and after at 100% zoom if you want to check details.
- Hit Download to save the compressed copy alongside your original.
Worth knowing
Lossy compression works by throwing away detail your eye is least likely to miss: fine texture in busy areas, subtle color variations, and high-frequency noise. A quality setting of 80 to 85 is the sweet spot for photographs - most people cannot tell it apart from the original at normal viewing size, yet the file often lands at a quarter of its starting weight. Below about 60, block artifacts start creeping into smooth gradients like skies and skin.
This tool uses the encoders your browser already ships with, driven through the Canvas API. That has two practical consequences. First, there is nothing to install and no queue to wait in - encoding a 12-megapixel photo takes well under a second on a typical laptop. Second, results can differ by a few percent between Chrome, Firefox and Safari, because each vendor tunes its JPEG and WebP encoders differently.
Format choice matters as much as the quality slider. At comparable visual quality, WebP files come out roughly 25 to 34 percent smaller than JPEG, and every current browser can display them. If your image has large flat areas, sharp text or transparency, PNG or WebP will treat it far better than JPEG, which smears hard edges with ringing artifacts.
When the slider alone will not get you small enough, reduce the pixel dimensions before compressing. A 4000-pixel-wide photo destined for a web page that renders it at 800 pixels carries 25 times more pixel data than needed; downscaling first shrinks the file more than any quality setting can, and it removes the sensor noise that makes JPEGs hard to compress in the first place.
Dropping JPEG quality from 95 to 85 typically halves the file size while changing pixels so little that most viewers fail a blind A/B test - the size curve is steepest exactly where your eye is least sensitive.
What this tool will not do
- It will not shrink an already heavily compressed JPEG by much - recompressing a quality-60 file mostly adds artifacts, not savings.
- It will not compress animated GIFs or video files; single still images only.
- It will not enlarge or repair a blurry photo - compression only removes data, never adds it.
Questions people ask
Why is my image still big after compressing?
Usually the pixel dimensions are the real problem. A 6000x4000 photo has 24 million pixels, and no quality setting can hide that. Resize it to the size it will actually be displayed at, then compress - the combination routinely achieves savings above 90 percent.
What quality setting should I use for photos on a website?
Start at 80. For hero images that get close scrutiny, try 85; for thumbnails, 70 is usually fine. Check skies and skin tones at 100% zoom - those show artifacts first.
Does compressing an image reduce its quality every time?
Each lossy re-encode discards a little more information, so avoid compressing a compressed file repeatedly. Keep your original and always work from that master copy instead of from a previous output.
Should I pick WebP or JPEG as the output?
WebP if the destination accepts it - it saves roughly a quarter to a third of the bytes at the same visual quality and supports transparency. JPEG remains the safe choice for email attachments and older systems that reject anything else.
Is there a limit on how many images or how large they can be?
There is no count limit. The practical ceiling per image is your device memory: a decoded photo needs 4 bytes per pixel, so a 50-megapixel file wants around 200 MB of RAM while being processed.
Why does the same photo compress to different sizes in different browsers?
Each browser bundles its own encoder build with its own tuning. Differences of 2 to 8 percent between Chrome, Safari and Firefox are normal, and neither result is wrong.
Usually the next step
More in Compress & Optimize
This page processed nothing on any server — there is no server. The technical explanation.