It started, as most catastrophes do, with the words "you're so good with cameras, would you mind?" My college friend Priya was getting married. Her actual photographer had food poisoning. I had a mirrorless camera and a weekend free. What could go wrong? The answer, it turned out, was 47 gigabytes.
That number represents approximately 1,400 RAW files, exported to full-resolution JPEGs, then organized into folders with names like "ceremony-final-FINAL-v3-USE-THIS-ONE." By Sunday evening, I had a hard drive full of gorgeous memories and absolutely no way to share them with anyone. Priya's inbox couldn't take it. Google Drive kept throwing up its hands. And my laptop fan was making a noise usually associated with small aircraft.
This is a problem that roughly nobody warns you about. Photography tutorials spend enormous energy on composition and lighting. They spend almost no time on what happens after you've taken 1,400 photos of a human being's happiest day. Spoiler: what happens is a file size crisis.
Why Image Files Are Secretly Out of Control
Modern cameras are, in a word, ridiculous. A single uncompressed RAW file from a mid-range mirrorless can easily hit 25MB. Export those to high-quality JPEG and you're still looking at 8-12MB per image. Multiply that by any event of consequence and you've created a storage problem that would make a 2008 IT department weep.
But most of those pixels are doing absolutely nothing useful. A 6000x4000 pixel image displayed on a website, shared in a WhatsApp group, or emailed to a grandmother will be viewed at a fraction of that resolution. You're essentially shipping a truck to deliver a sandwich.
The solution isn't to take worse photos. It's to compress the right way, at the right quality settings, into the right format. And that last part matters more than most people realize.
JPEG vs PNG vs WebP: The Format War Nobody Asked For
Here's a quick primer, because format choice is where most people leave serious file savings on the table:
- JPEG is your old reliable. Great for photographs, lousy for graphics with text or hard edges. It compresses by discarding color detail your eye mostly won't miss - until you over-compress, at which point photos start looking like abstract impressionism.
- PNG is lossless, which sounds wonderful until you realize your 400KB product photo just became 3.4MB. Perfect for logos, screenshots, and anything with transparency. Genuinely terrible for most photographs.
- WebP is the format Google built to make everyone's web pages faster. It typically produces files 25-35% smaller than JPEG at equivalent quality. Browser support is now essentially universal. The only downside is that it sounds like a breakfast cereal.
Picking the wrong format for the job is like choosing your mode of transport based solely on what's parked closest to you. Sometimes that's fine. Sometimes you're taking a jet ski to a dentist appointment.
What "Quality" Actually Means in Compression
Every compression tool offers a quality slider, usually from 0 to 100. Most people assume higher is always better and set it to 90 or 95 and call it done. This is leaving enormous file savings untouched.
The practical reality: for web display, a quality setting of 75-82 is visually indistinguishable from 95 to almost any human eye. The file size difference, however, can be dramatic. A 4MB JPEG at quality 95 might compress to 800KB at quality 78 with no visible degradation whatsoever. That's an 80% reduction. For a gallery of 200 photos, that's the difference between 800MB and 160MB.
The key is to test on your actual images rather than guess. Some photos with complex gradients and lots of detail benefit from slightly higher settings. Flat backgrounds and simple compositions can go lower. It takes about three minutes of experimentation to find the sweet spot for a given batch.
How I Finally Fixed the 47GB Problem
After two days of Priya sending me increasingly creative versions of "so about those photos," I ran the entire gallery through COMBb2's image compression tool. The appeal was immediate: everything runs in the browser, so the photos never left my laptop. When you're dealing with someone else's wedding photos - featuring people's faces, locations, intimate moments - the last thing you want is files uploading to some unknown server to be "processed."
The workflow was genuinely simple. I dropped batches in, selected WebP as the output format, dialed quality to 80, and watched the file sizes collapse. What had been 8MB JPEGs became 1.1MB WebP files. Visually identical on any screen. Shareable via email, WhatsApp, any platform that had previously refused to cooperate.
The final gallery came in just under 6GB. Still substantial, but suddenly manageable. Priya got her photos. I got my laptop fan back to a normal frequency. Everyone was happy, particularly the best man who had been waiting to send his favorites to his mum in Edinburgh.
When Compression Actually Matters: Real Scenarios
The wedding situation was dramatic, but file size problems show up constantly in less obvious places:
- Email attachments: Most email providers have a 25MB limit. A single uncompressed photo from a modern iPhone can exceed this. Compress before you attach, or accept that the email will bounce and your recipient will assume you've vanished.
- Website speed: Google's PageSpeed Insights will cheerfully remind you that your 4MB hero image is catastrophic for mobile load times. Images account for the majority of page weight on most sites. This is a solvable problem.
- Cloud storage costs: If you're paying for storage, uncompressed photos are quietly charging you for pixels no one can see. A proper compression pass can halve your storage bill with no meaningful quality trade-off.
- Social media uploads: Instagram, Facebook, and TikTok all recompress your images on upload anyway - often badly. Sending them a carefully compressed file at the right size means you control the quality degradation, not an algorithm optimized for bandwidth costs.
It's also worth pairing compression with a proper resize step first. If you're uploading a 6000-pixel-wide photo to a website column that displays it at 800 pixels, you're sending six times more data than necessary even before compression enters the picture. Resize first, then compress. This is the correct order and I will not be accepting questions.
A Note on Quality You Can Actually Trust
One reason people avoid aggressive compression is fear. What if it looks terrible? What if I lose something I can't get back? These are reasonable instincts, but they're mostly mythology.
Modern compression algorithms - particularly WebP - are remarkably good at preserving perceptual quality while reducing file size dramatically. The artifacts that plagued JPEG in the 90s (the blocky, muddy disasters at low quality settings) are much less severe with current encoding. And if you're worried about a specific image, the compressor gives you a live quality preview before you commit to anything.
The other safety net: always compress a copy, not the original. Keep your master files. Compression is a delivery step, not an archival strategy.
Conclusion
The 47GB wedding gallery taught me something that no photography tutorial had bothered to mention: capturing great images is only half the job. Getting those images to actual human beings, in a format they can open, on a connection that doesn't time out, is the other half. Smart compression - choosing the right format, finding the right quality setting, working with a tool that doesn't require your photos to leave your device - turns an unshareable hard drive into memories people can actually see. Priya still sends me photos from that wedding. She says they look perfect. She's right, and they're 1.1MB each.
Try it yourself
Free, private, runs in your browser. No sign-up required.
