JPG vs WebP for Photography: A Real-World Comparison
Photographers face a practical question when optimizing images for the web: is WebP actually better than JPG for photos, or is the hype overblown? The theoretical benchmarks are clear (WebP is 25-34% smaller), but real-world results depend on image content, quality settings, and the specific visual characteristics that matter for photography.
This comparison focuses specifically on photographic content: portraits, landscapes, product shots, and event photography. Not screenshots, not icons, not graphics. Real photos.
JPG vs WebP for Photography
| Aspect | JPG | WebP |
|---|---|---|
| Portrait photo (2MB JPG q85) | 2.0MB | 1.3-1.5MB (same quality) |
| Landscape photo (1.5MB JPG q85) | 1.5MB | 1.0-1.1MB (same quality) |
| Product photo (800KB JPG q85) | 800KB | 520-600KB (same quality) |
| Gradient handling | Banding at lower quality | Smoother transitions |
| Detail preservation | Strong at quality 85+ | Strong, slightly softer |
| Skin tone accuracy | Excellent | Excellent, minor differences |
| Color accuracy | sRGB only | sRGB only (8-bit mode) |
| Progressive loading | Yes (progressive JPEG) | No native progressive mode |
| Camera raw compatibility | Universal export target | Growing support |
File Size Tests on Real Photos
Across hundreds of test photographs at matched visual quality (SSIM 0.95+), WebP consistently produces files 25-35% smaller than JPG. The savings are remarkably consistent across different subject matter: portraits, landscapes, still life, street photography, and architecture all show similar percentage reductions.
The absolute savings matter more than the percentage. A portfolio page with 20 photographs might total 15MB as JPG and 10MB as WebP. That 5MB difference translates to noticeably faster page loads, especially on mobile connections.
Visual Quality: The Subtle Differences
At matched file sizes, WebP typically looks slightly sharper in areas with fine detail (hair, fabric texture, foliage) because its prediction-based compression preserves edges better than JPG's block-based DCT. Conversely, some photographers note a slight softening in WebP's handling of very subtle tonal gradations.
At matched quality settings (where each format's quality slider produces its best visual output), the differences are imperceptible to most viewers. Side-by-side comparisons at 100% zoom may reveal minor differences, but at normal viewing distances on a web page, both formats look identical.
The Photographer's Workflow Consideration
Most photographic workflows start with RAW files processed in Lightroom, Capture One, or similar software. The export step is where the JPG-vs-WebP decision happens. Major photography software now supports WebP export, but JPG export has decades of optimization and offers more granular control.
A practical approach: export from your RAW processor as high-quality JPG (quality 95), then batch-convert to WebP for web delivery. This gives you JPG masters for maximum compatibility and WebP versions for web performance. Never convert directly from JPG to WebP for web use: the lossy-to-lossy conversion compounds quality loss.
Client Delivery and Social Media
For client deliverables (gallery proofs, download packages), JPG remains the standard. Clients expect JPG files that open on any device. For web-based galleries viewed in browsers, WebP provides a better experience through faster loading.
Social media platforms (Instagram, Facebook, Twitter) convert uploaded images to their own formats regardless of what you upload. The upload format matters less than the resolution and quality you provide. JPG at quality 95 is still the safest upload format for maximum quality after platform re-compression.
Print Considerations
For print output, neither JPG nor WebP is ideal. Professional printing workflows prefer TIFF or high-quality JPG. WebP is not accepted by most print services. If your photos need to serve both web and print, maintain high-quality source files (RAW or TIFF) and export separately for each delivery channel.
Home printing from a web browser handles both JPG and WebP. For casual prints, the format makes no meaningful difference.
Frequently Asked Questions
Will switching from JPG to WebP make my photos look worse?
No. At equivalent quality settings, WebP produces visually identical results to JPG in smaller files. The quality concern is only relevant when converting existing JPGs to WebP (lossy-to-lossy). Always export from your original source files to WebP for best results.
What WebP quality setting matches JPG quality 85?
WebP and JPG quality values are not directly comparable. WebP quality 75-80 typically produces files of similar visual quality to JPG quality 85, but at a smaller file size. Test with your specific images to find the right balance.
Should I offer both JPG and WebP downloads on my portfolio site?
For browser display, serve WebP via the picture element with JPG fallback. For downloads, offer JPG since clients expect it and it works everywhere. There is no need to offer both formats for download unless specifically requested.