How to Compress Photos for the Web Without Ruining Them
Photographers are trained to protect image quality above almost everything else, which makes the idea of compressing files for the web feel like a compromise to resist. But image optimization for a photography website isn't actually a tradeoff between quality and speed in the way it's often framed. Done correctly, a properly optimized image looks identical to the human eye while loading in a fraction of the time of an unoptimized one. The real tradeoff only appears when compression is done carelessly, either too aggressively, ruining visible quality, or not at all, wrecking site speed.
Table of contents
Why raw exports are the wrong file for the web
Resolution: matching the file to its actual display size
Format and compression settings that actually matter
A practical export workflow for galleries
Tools and automation worth using
FAQ
1. Why raw exports are the wrong file for the web
A photographer exporting from Lightroom or Capture One at maximum quality, full resolution, minimal compression, is producing a file optimized for print or archival purposes, not for a browser rendering it at 1200 pixels wide on a phone screen. That mismatch is the root cause of nearly every slow photography gallery: the browser is downloading far more data than it will ever actually display, purely because the export settings were never adjusted for the web use case specifically.
This matters more for photographers than almost any other type of website, because the volume of images is so much higher than a typical business site. A twenty-image gallery of unoptimized full-resolution exports can easily total 100-200MB, an amount that would take even a reasonably fast mobile connection many seconds, sometimes tens of seconds, to fully load. The same gallery, properly optimized, often comes in under 10MB with no visible quality difference on screen.
2. Resolution: matching the file to its actual display size
The single biggest lever in image optimization is resolution, not compression quality. An image displayed at a maximum of 2000 pixels wide on a large desktop hero doesn't need to be exported at 6000 pixels, the camera's native resolution, since the browser will simply be downloading and then downscaling four times more data than it will ever display. Export images at the actual maximum size they'll appear on your website, not the maximum size your camera can produce.
This requires knowing your website's actual display dimensions, which vary by placement: a full-width hero might need up to 2400px on the long edge, while a grid gallery thumbnail might only need 800-1000px. Most website platforms will generate multiple sizes automatically for responsive display if the images are uploaded at a reasonable master size, but uploading unnecessarily massive originals (8000px+ camera-native files) still forces the platform to process and often serve more data than needed, even with responsive handling in place.
3. Format and compression settings that actually matter
For most photography use cases, a well-compressed JPEG at 70-85% quality remains a reliable choice, striking a strong balance between file size and visible quality, since JPEG compression at this range is rarely distinguishable from an uncompressed original at normal viewing distances and screen sizes. Going below 60% quality starts to introduce visible artifacts, particularly in areas of smooth gradient like skies or skin tones, common subjects in photography portfolios, so it's worth testing your specific export settings against your actual typical images rather than applying a blanket setting blindly.
WebP, a newer image format, offers meaningfully better compression than JPEG at equivalent visual quality and is now widely supported by browsers and increasingly handled automatically by website platforms during upload. If your platform supports automatic WebP conversion, you often don't need to manage this manually, but it's worth confirming that your platform is actually serving WebP to supporting browsers rather than defaulting to larger JPEGs across the board.
4. A practical export workflow for galleries
Build compression into your existing editing workflow rather than treating it as a separate final step. After finishing your edit in Lightroom or Capture One, use an export preset specifically configured for web: resize to your website's actual maximum display dimension (commonly 2000-2400px on the long edge), export as JPEG at 75-80% quality, and strip unnecessary metadata that adds file weight without any visual benefit. Save this as a dedicated "web export" preset so it becomes a one-click step rather than a manual decision made inconsistently gallery to gallery.
For photographers delivering large galleries regularly, batch exporting with a consistent preset is far more reliable than optimizing images one at a time, both for consistency and for the sheer time savings. If you're currently uploading straight from a "client delivery" export (often full resolution for print ordering) directly to your website, that's very likely the single biggest fix available: create a separate, smaller web-specific export and use that instead.
5. Tools and automation worth using
Beyond your editing software's export settings, dedicated compression tools can catch additional savings, particularly for images already exported without optimal web settings. Tools like Squoosh (a free, browser-based compressor) let you visually compare compression levels against file size in real time, which is useful for calibrating your own eye to what compression level is actually acceptable for your specific photography style before you commit to a preset.
Many website platforms, including Squarespace, also apply some automatic optimization and responsive image serving on upload, but this shouldn't be relied on as a substitute for reasonable export settings on your end. Platform-level optimization works best as a safety net on top of already-reasonable source files, not as a fix for wildly oversized, unoptimized originals. Getting your export workflow right upstream remains the highest-leverage single change most photographers can make to their site's actual performance.
The bottom line
Image optimization for a photography website isn't a quality sacrifice, it's a matter of matching your export settings to how the image will actually be displayed and viewed. Export at the resolution your site actually needs, compress at a quality level that's visually indistinguishable from the original, and build this into your editing workflow as a standard preset rather than an inconsistent afterthought. The payoff is a site that loads fast without a single visible compromise to the photography itself.
FAQ
What's the ideal JPEG quality setting for web export?
Generally 70-85%, which offers strong compression with no visible quality loss for most photography subjects at normal viewing sizes.
Should I export images at my camera's full resolution for the website?
No. Export at the actual maximum display size your website uses, typically 2000-2400px on the long edge for hero images, since anything larger just adds unnecessary file weight.
Is WebP better than JPEG for photography websites?
Generally yes, offering better compression at equivalent visual quality, and most modern browsers and website platforms now support it, often automatically.
Will compression make my images look noticeably different?
Not at the recommended quality range (70-85% JPEG or equivalent WebP settings). Visible differences typically only appear at much more aggressive compression levels.
Can my website platform handle image optimization automatically?
Many platforms apply some level of automatic optimization, but it works best as a supplement to reasonably sized, compressed source files, not as a substitute for a proper export workflow.
More insights for photographers
