How to reduce image file size without visible quality loss
Updated
A phone photo is usually 3–8 MB. A web page wants images under 300 KB, an email attachment under a megabyte or two, and many upload forms reject anything above a fixed limit. Getting from one to the other without making the picture look bad is mostly a matter of knowing which of three levers to pull first.
The three levers, in order of effect
1. Dimensions
File size grows with the number of pixels, and the number of pixels grows with the square of the width. A 4000 × 3000 photo has twelve million pixels; scaled to 1600 × 1200 it has under two million. That is an 84% reduction before any compression setting is touched.
Ask where the image will be seen:
| Use | Sensible maximum width |
|---|---|
| Full-width website banner | 1920–2400 px |
| Image inside an article or product page | 1200–1600 px |
| Email, chat, documents | 1200–1600 px |
| Thumbnail or avatar | 300–600 px |
Sending more pixels than the screen can show costs bytes and gives nothing back. The exception is print, where you want every pixel you have.
2. Format
Choosing the right format can change the size several times over:
- Photos saved as PNG are enormous. Save them as JPG or WebP.
- Screenshots and graphics with text look best as PNG; lossless or high-quality WebP is usually smaller still.
- For anything going on a website, WebP is typically 25–35% smaller than JPG at similar quality.
3. Quality
For lossy formats (JPG and WebP), the quality setting decides how much detail is discarded. The relationship is not linear: dropping from 100 to 85 often halves the file with no visible change, while dropping from 60 to 45 saves little and starts to look bad.
| Quality | What to expect |
|---|---|
| 90–100 | Visually identical to the original; large files |
| 75–85 | The sweet spot for most photos |
| 60–75 | Fine for thumbnails and backgrounds; look closely at faces and gradients |
| Below 60 | Visible blocks and banding |
A workflow that works
- Keep the original. Compression is one-way. Work on copies.
- Resize first. Set a maximum width that matches where the image will be used.
- Pick the format. JPG or WebP for photos, PNG or WebP for graphics.
- Start at quality 75–80 and look at the result at 100% zoom. Check skin, sky and any text — those show problems first.
- Adjust once. If it looks perfect, try 70. If you can see artifacts, go up to 85.
Hitting a specific size limit
Upload forms often say something like “maximum 200 KB”. The fastest way there:
- Reduce the width first. Halving the width cuts the size to roughly a quarter.
- Then lower quality in steps of 5–10.
- If the image is a PNG and transparency is not needed, switch to JPG or WebP — this alone often solves it.
Why did my file barely shrink, or get bigger?
- It was already compressed. A JPG that has been through a messaging app or a website has already been squeezed hard. Re-compressing at the same quality saves almost nothing.
- It is a PNG. PNG is lossless, so a quality slider has little to work with. Change the output format.
- You raised the quality. Re-saving a quality-60 JPG at quality 90 produces a bigger file that looks no better; the lost detail does not come back.
The image compressor on this site handles the last case for you: when the result would be larger than what you started with, it keeps your original instead.
What compression does not change
Resizing and compressing an image through a browser-based tool re-encodes the pixels. Be aware of two side effects:
- Metadata is usually dropped. Camera settings, GPS location and other EXIF data are not carried into the new file. For photos you share publicly that is often a privacy benefit; for an archive you may want to keep the originals.
- Animated images become still. An animated GIF or WebP is reduced to its first frame.
You can try all of the above in the image compressor. It runs in your browser, so nothing is uploaded, and it lets you set quality, maximum width and output format for a whole batch of images at once.