Photographer's Guide to WebP, AVIF, and Modern Image Formats
You've spent hours editing the perfect shot. The colours are exactly right, the sharpness is dialled in, every pixel tells a story. Now you need to put it on your portfolio website, and the question is: do you keep using JPG like you've done for years, or switch to one of these newer formats that promise smaller files with the same quality?
The Real Impact on Portfolio Load Speed
Let's talk numbers. A typical portfolio page displays 15-25 images. At quality-90 JPG, each image at 1920px wide is roughly 400-600 KB. That's 6-15 MB of images per page. The same images in WebP at equivalent quality are 280-420 KB (30% smaller). In AVIF, they're 180-300 KB (50% smaller).
For a portfolio website, this difference is massive. Your page goes from 10 MB to 5 MB. On mobile, that's the difference between a 3-second load and a 6-second load. Art directors reviewing portfolios on their phones during a commute don't wait for slow pages — they move to the next photographer.
WebP: The Practical Choice Right Now
WebP has 96%+ browser support as of 2026. Every browser your potential clients use can display WebP. The quality-to-file-size ratio is noticeably better than JPG, especially in the 70-85% quality range where most web images live. For a photographer's portfolio, WebP is the sweet spot: meaningful file size savings, near-universal compatibility, and excellent quality.
One concern photographers have: does WebP handle colour accurately? Yes, with a caveat. WebP supports sRGB colour space perfectly. If your workflow involves wider colour spaces (Adobe RGB or ProPhoto RGB), convert to sRGB before converting to WebP. Most web browsers display sRGB anyway, so this shouldn't change your web delivery workflow.
AVIF: Maximum Compression, Some Trade-offs
AVIF offers genuinely impressive compression — roughly 50% smaller than JPG at the same perceived quality. For large portfolio galleries, this saves significant bandwidth. It also supports 10-bit and 12-bit colour depth, HDR, and wide colour gamut, which matters if you're delivering to HDR-capable displays.
The trade-offs: encoding is slow (noticeably slower than WebP or JPG), which matters if you're converting hundreds of images. Browser support is good but not quite universal — older versions of Safari and some mobile browsers may not display AVIF. And some photographers report that AVIF can produce slight colour shifts in certain tonal ranges. Test with your actual images before committing your entire portfolio.
My Recommended Workflow
Edit in your normal format (RAW → TIFF/PSD for editing). Export web-sized versions as high-quality JPG (your master web copies). Then convert those JPGs to WebP for your website. Keep the JPGs as fallbacks and for platforms that don't accept WebP.
If your portfolio website builder supports it, serve AVIF to browsers that support it, WebP as fallback, and JPG as the final fallback. WordPress, Squarespace, and most modern platforms handle this automatically through their image optimization features. If you're on a custom site, your developer can set up format negotiation.
Archival vs Display Copies
Never convert your master files to WebP or AVIF for archival purposes. These formats are designed for web delivery, not long-term storage. Your archive should remain in TIFF, PSD, or high-quality JPG. WebP and AVIF are display formats — they are what you generate from your archive when you need to publish images online. If a format falls out of favour or a better one emerges, you re-export from your archive rather than converting from one lossy web format to another.
A practical archival workflow: edit in your RAW processor, export a full-resolution TIFF or PSD as your master file, then generate web-sized WebP copies for your portfolio site. If you need to update your portfolio, re-export from the masters. This approach ensures your originals always remain at the highest possible quality, regardless of which web format is popular at the time.
What About Client Deliveries?
For client file delivery, stick with JPG. Clients don't care about format efficiency — they care about being able to open and use their photos. JPG opens on every device, every operating system, every program. Sending a client WebP files will generate confused emails. JPG for delivery, WebP/AVIF for your website. Keep those workflows separate.
