A friend of mine sells clothes on Facebook Marketplace. She takes decent photos with her phone but every listing has 8-10 images and uploading them takes forever on her connection. She asked me if there’s a way to make the photos smaller without making them look bad.
I checked one of her photos — 4.8MB for a single image. Her phone shoots at full resolution which is great for printing but way too much for a Facebook listing that people scroll past in 2 seconds.
I compressed it down to 380KB. Same photo. She couldn’t tell the difference. Her uploads went from 3 minutes to about 15 seconds.
Here’s exactly how to do it.
Step by step
1. Open the compressor
Go to convertkr.com/image-compress. No signup, no app to install.
2. Upload your image
Drag and drop your photo or click to browse. Works with PNG, JPG, WEBP, and most other formats.
3. Set the quality
You’ll see a quality slider. This is where the magic happens:
- 80-90% — almost no visible difference from the original. File size drops by 40-60%. This is what I use for most things.
- 60-70% — slight softness if you zoom in, but looks fine at normal viewing size. File size drops by 70-80%.
- 40-50% — noticeable quality loss. Only use this if you really need the smallest file possible and don’t care much about quality.
For my friend’s Facebook photos, I used 75%. Perfect balance.
4. Download
You’ll see the original size vs compressed size before downloading. That “before and after” comparison is actually useful — if the reduction isn’t enough, adjust the slider and try again.
Real numbers from images I’ve compressed
These are actual files I’ve dealt with:
- Phone photo (4.8MB JPG) → 75% quality → 380KB (92% smaller)
- Screenshot (1.2MB PNG) → 80% quality → 210KB (82% smaller)
- Product photo (3.1MB JPG) → 85% quality → 620KB (80% smaller)
- Scanned document (6.5MB PNG) → 70% quality → 440KB (93% smaller)
In every case, the compressed version looked identical at normal viewing size. You’d only notice the difference if you zoomed in to 300% and compared them side by side.
Where this matters most
Email attachments. Most email providers limit attachments to 25MB. If you’re sending 10 photos that’s 2.5MB each — you’re already at the limit. Compress them first and you can fit 30-40 photos in one email.
Website speed. A relative of mine has a small business website. The homepage had 6 photos totalling 18MB. The page took 8 seconds to load on mobile. I compressed all the images and the total dropped to 2MB. Load time went to under 2 seconds. Google actually ranks faster sites higher, so this matters for business.
WhatsApp and social media. These apps compress your photos anyway when you upload them. But they do it aggressively and you can’t control the quality. If you compress the photo yourself first at 80% quality, it looks better than what WhatsApp does automatically because you controlled the process.
Online forms. Job applications, university admissions, government portals — they all have file size limits. Usually 200KB or 500KB. A phone photo is always bigger than that. You need to compress it before uploading.
Cloud storage. If you’re backing up thousands of photos to Google Drive or Dropbox, compressing them saves real storage space. I helped a friend free up 4GB on his Google Drive just by compressing his photo collection from 80% quality. He couldn’t see any difference in the photos.
The “without losing quality” part
Let me be honest here — technically, any compression loses some data. But the human eye can’t tell the difference at 80-90% quality. When people say “compress without losing quality” they mean “compress without it looking worse.” And yes, that’s absolutely possible.
The trick is that photos contain way more detail than your screen can display. A 12MP phone photo has 4000×3000 pixels. Your phone screen is maybe 1080 pixels wide. There’s a lot of data in that photo that you literally cannot see. Compression removes that invisible data first.
At 80% quality, the compressor removes the stuff you can’t see. At 50% quality, it starts removing stuff you can see. That’s the line.
Resizing vs compressing
These are different things and people mix them up all the time.
Compressing keeps the image dimensions the same (say, 4000×3000 pixels) but reduces the file size by being smarter about how it stores the color data.
Resizing makes the image physically smaller — like changing 4000×3000 to 1920×1440. This also reduces file size because there are fewer pixels to store.
For maximum reduction, do both. Resize the image to the dimensions you actually need, then compress it. A 4000×3000 photo resized to 1200×900 and compressed at 80% quality might go from 4MB to 90KB. That’s a huge difference.
The ConvertKr compressor lets you set a max width too, so you can resize and compress in one step.
FAQ
Can I compress a PNG?
Yes, but PNG compression works differently — it’s lossless, so the file size reduction is smaller (usually 10-30%). For bigger savings, convert the PNG to JPG first using the image converter, then compress the JPG.
Will compression remove the image metadata?
The compression process may strip EXIF data (camera info, GPS location, date taken). For most people this doesn’t matter. If you need to keep metadata, make a backup of the original first.
Can I undo the compression?
No. Compression is one-way — you can’t uncompress a JPG back to the original quality. Always keep the original file if you might need the full quality later.
Is there a limit on file size?
No artificial limit. Since processing happens in your browser, your device’s memory is the only constraint. I’ve compressed 15MB photos without issues.
Need to compress an image? Open the image compressor — drop your file, set quality, download.