The two ways an image gets smaller
There are exactly two ways to reduce an image's file size, and the difference matters:
- Compression — encode the same image data more efficiently. JPEG and WebP can throw away information your eye won't notice, producing significantly smaller files at visually identical quality.
- Resampling — reduce the number of pixels (e.g. from 4000×3000 down to 1200×900). This is genuine quality loss, but if the displayed size is smaller than the source, you'll never see the difference.
Used carefully, both can shrink an image without visible quality loss. Used poorly, both can ruin a photo.
The decision tree
Step 1: Is your image larger than its displayed dimensions?
If your 4000×3000 photo will only ever be displayed at 1200×900, you're carrying ~10× more pixels than you need. Resampling to 1200×900 will reduce the file size dramatically with zero visible loss. Always resample to displayed dimensions before compressing.
Step 2: Is your image a photo or graphics?
This determines format choice:
- Photos: JPG. (Or WebP if your platform supports it — typically 25-35% smaller than JPG at the same quality.)
- Graphics, logos, screenshots with text: PNG. JPG will produce ugly artifacts around sharp edges and text.
- Mixed (photo with text overlay): usually PNG, but test both.
Step 3: Apply compression intelligently
For JPG: quality 85% is the sweet spot. Above that, file size grows fast without visible improvement. Below 70%, artifacts become noticeable. CompressTo uses a binary search to find the highest quality that fits under your target — usually well above the visible-loss threshold.
Realistic expectations
| Source | Target | Visible quality loss? |
|---|---|---|
| 4 MB phone photo | 1 MB | None. |
| 4 MB phone photo | 500 KB | None at typical viewing sizes. |
| 4 MB phone photo | 200 KB | None at small sizes; slight softness if blown up. |
| 4 MB phone photo | 100 KB | Slight, mostly invisible. |
| 4 MB phone photo | 50 KB | Visible. Acceptable for ID photos; not for portfolios. |
| 4 MB phone photo | 20 KB | Significant. Recognisable but pixelated. |
Pre-compression checklist
- Strip metadata you don't need. EXIF data (camera model, GPS, etc.) can add tens of KB to small files. CompressTo strips this automatically.
- Crop tightly. Empty background pixels eat space. A tight crop preserves the important detail at smaller file sizes.
- Resize to displayed dimensions. See above. This is the single biggest no-quality-loss saving.
- Choose the right format. JPG for photos, PNG for graphics, WebP if supported.
- Don't double-compress. Each JPG re-encode degrades quality. Always go from original to final target in one step.
What CompressTo does automatically
You don't have to think about most of the above. Drop your image into the tool, set a target, and CompressTo:
- Runs a binary search on JPEG quality to find the highest quality that fits your target.
- Automatically reduces dimensions if quality alone can't get you under target.
- Strips metadata to claw back every available byte.
- Runs entirely in your browser — your image is never uploaded.
Start with the homepage compressor, or pick a target size: 100 KB, 200 KB, 500 KB, 1 MB.
The honest summary
"Reduce file size without losing quality" is partly possible: by resampling to the size you actually use, choosing the right format, and using modern compression, you can shrink most files by 60–80% with no visible loss. Below that, you're trading something — but for most everyday uses, the trade is invisible.