WebP for Photography Portfolios

Photographers face a direct tension: portfolios must look pristine, yet large images slow galleries to a crawl. WebP resolves most of it, delivering near-indistinguishable quality 25–34% smaller than JPG. This guide covers the quality settings that protect image fidelity, the double-lossy concern, metadata handling, and why you keep the originals.

For the format itself, see What is WebP?. To convert a gallery, use JPG to WebP.

Is WebP good enough for photography?

WebP is good enough for portfolio photography at quality 82 and above, where differences from the source are invisible without side-by-side pixel inspection. Its lossy mode preserves the smooth gradients and fine detail photographs depend on, while cutting file size by a quarter to a third versus JPG.

For display on the web — the use case for a portfolio — WebP at high quality is visually equivalent to the JPG it replaces. The fidelity scale is detailed in Lossy vs Lossless Compression.

What quality setting should photographers use?

Use lossy WebP at quality 82–88 for portfolio images, reserving the upper end for hero and full-screen views. Above quality 90 the file grows quickly with no visible gain. Below 80, attentive viewers may notice softening in fine texture.

Settings by display size:

Full-screen / hero images — q=85–88
Gallery grid images — q=82
Thumbnails — q=70–75

Should you worry about double-lossy compression?

Double-lossy compression is rarely a problem at quality 80 and above. Converting a JPG to WebP applies a second lossy pass, but at q≥80 the encoder has little left to discard from a good JPG, so the result looks identical. Below q=80, stacked artefacts can become visible.

If you want zero risk of cumulative loss, encode from the original RAW or TIFF export rather than from a JPG, or use near-lossless mode. See WebP Compression Settings.

Does WebP preserve photo metadata?

WebP can store EXIF and XMP metadata, but converters often strip it to save bytes. If copyright, camera data, or colour profiles matter, keep metadata on export; if page weight is the priority, strip it. Decide per use — portfolio display rarely needs embedded EXIF.

The metadata chunks are part of the file structure — see WebP File Structure: RIFF Container and Chunk Format.

Should you keep your original files?

Always keep the original RAW, TIFF, or full-quality JPG. WebP is a delivery format for the web, not an archival master. Keep the originals for reprints, future re-encoding, and any client deliverable, and serve WebP only to the website.

This mirrors the wider rule: archive the master, publish WebP. Convert your web-facing exports with JPG to WebP.

Where to go from here

For photography portfolios, WebP at q=82+ gives you pristine display quality at a quarter less weight. Keep your originals as masters and let WebP carry the gallery.