Image Compression for Photographers: Managing Large Photo Libraries | Bulk Image Compressor
A single wedding shoot can easily produce 30 to 40GB of files. A day of portrait sessions might generate 10 to 15GB. Multiply that across a year of work and you’re looking at terabytes of storage, most of which you’ll never deliver at full resolution.
The raw files from your camera matter for editing. But once you’ve finished processing, you need smaller versions for client delivery, web portfolios, social media, and email. That’s where compression fits into a photographer’s workflow.
The storage problem
Here’s what a typical photographer’s output looks like in terms of file sizes:
| File type | Typical size per image |
|---|---|
| RAW (Canon CR3, Nikon NEF, Sony ARW) | 25 to 60MB |
| Full-resolution JPEG export from Lightroom | 8 to 15MB |
| Web-ready JPEG (2000px wide, 80% quality) | 300 to 800KB |
| Social media JPEG (1200px wide, 80% quality) | 100 to 400KB |
A wedding gallery of 500 edited photos exported at full resolution comes out to about 5 to 7GB. That same gallery compressed for web delivery drops to around 200 to 400MB. The visual difference at screen viewing sizes is negligible, but the storage and transfer difference is massive.
If you’re paying for cloud storage (Google Drive, Dropbox, Amazon S3) to host client galleries, this adds up fast. Compressing your delivery files can cut your storage costs by 80% or more without any visible impact on what clients see on their screens.
When to compress (and when not to)
Not every file in your library needs compression. Here’s how to think about it:
Keep at full quality:
- Your edited RAW files or PSD/TIFF master files. These are your originals. Never compress these.
- Files destined for large-format printing (canvas prints, albums, billboards). Print needs every pixel you’ve got.
Compress for delivery:
- Client web galleries (Pixieset, ShootProof, SmugMug, or your own site). Clients are viewing on laptops and phones. They don’t need 15MB files.
- Portfolio images on your website. Visitors leave if your site is slow. A portfolio page with twenty 10MB images will take forever to load.
- Social media sharing. Instagram, Facebook, and Pinterest all re-compress your uploads anyway. Pre-compressing gives you more control over the final look.
- Email proofs and previews. Sending a dozen uncompressed photos over email is a recipe for bounced messages.
Quality settings that preserve what matters
Photographers care about specific things in an image: skin tones, color accuracy, detail in hair and fabric, smooth gradients in skies. The good news is that JPEG compression at reasonable quality levels preserves all of these well.
85 to 90% quality is the safe zone for client delivery. At this range, compression artifacts are invisible to the naked eye, even when pixel-peeping on a high-resolution monitor. File sizes drop by 40 to 60% compared to a full-quality export. This is what you should use for online galleries where clients might download and print images at home.
75 to 85% quality works perfectly for portfolio websites and blog posts. The images look clean at screen viewing sizes, and page load times stay fast. Your portfolio should load quickly because potential clients will bounce if they have to wait for each image. For a deeper look at finding the right quality threshold, read our guide on reducing file size without losing quality.
70 to 80% quality is fine for social media and email previews. These images are viewed on small screens and get re-compressed by platforms anyway. There’s no reason to send a 5MB file to Instagram when a 300KB file produces the same result after Instagram processes it.
Below 70% is where you’ll start noticing problems. Skin tones can get blotchy, gradients show banding, and fine details in hair or lace start to blur. Avoid going this low for anything client-facing.
Batch processing workflows
Processing hundreds of images one at a time isn’t realistic. Here’s how to handle compression in bulk.
Exporting from Lightroom or Capture One
Both Lightroom and Capture One let you set quality and resize during export. This is the simplest approach if you’re already exporting:
- Set your long edge to 2000 to 2500px for web galleries, or 1200px for social media.
- Set JPEG quality to 82 to 85%.
- Export the full batch in one go.
The downside is that Lightroom’s quality scale doesn’t map perfectly to standard JPEG quality. Lightroom quality 80 is roughly equivalent to standard JPEG quality 85 in some encoders. You may need to experiment to find your preferred setting.
Using Bulk Image Compressor for existing JPEGs
If you’ve already exported your JPEGs at full quality and need to create smaller versions, or if you have images from multiple sources that need consistent compression:
- Open Bulk Image Compressor in your browser.
- Drop in your batch of images. The tool handles hundreds of files at once.
- Set your quality level (80 to 85% for galleries, 75 to 80% for web).
- Download the compressed batch.
Everything processes locally in your browser, so your client photos never leave your computer. That matters when you’re working with private events like weddings, boudoir sessions, or corporate shoots.
Creating multiple versions
A practical approach is to maintain two or three compressed versions of each delivered set:
- Gallery version (2000 to 2500px, 85% quality): For client online galleries and downloads.
- Web version (1200 to 1600px, 80% quality): For your portfolio site and blog.
- Social version (1080 to 1200px, 80% quality): For Instagram, Facebook, and Pinterest.
This takes a few extra minutes per shoot but saves time later when you need to pull images for different purposes.
Archiving vs. web delivery
Your archive strategy and your delivery strategy should be separate. Here’s a simple framework:
For archiving: Keep your RAW files and full-resolution edited exports on local drives with a backup (external drive, NAS, or cloud backup). Don’t compress these. Storage is cheap compared to the cost of losing original files.
For active delivery: Keep compressed gallery versions on whatever platform you use for client access. These can be regenerated from your originals if needed, so they don’t need the same backup treatment.
For cold storage: After a project is delivered and the client has their files, you can move the full-resolution exports to cold storage (Amazon Glacier, Backblaze B2) and keep only the compressed web versions readily accessible. This keeps your fast storage costs manageable.
A note on file naming
When you create compressed versions, use a consistent naming convention so you can tell which version is which. Something like photo-001-web.jpg or photo-001-gallery.jpg works. Don’t overwrite your full-quality exports with compressed versions. It seems obvious, but it happens, especially during late-night editing sessions.
Compression isn’t about sacrificing quality. It’s about being intentional with file sizes for each use case. Your RAW files stay untouched. Your client gallery looks great at 85% quality. Your portfolio loads fast. And your storage bill doesn’t spiral out of control. A few minutes of batch compression per shoot keeps everything running smoothly.
Ready to compress your images?
Bulk compress JPEG, PNG, WebP, and AVIF images right in your browser. No uploads, no sign-ups.
Try Bulk Image Compressor