Performance6 min read·Updated

Cut CDN and Hosting Bandwidth with WebP

If images are 60–80% of transfer, a 30% WebP saving is a 20%+ bill saving. Convert the hottest paths first (home, PLP, blog index), then the long tail.

Egress is just bytes × requests

A category page with 24 × 400 KB images is 9.6 MB per visitor. At 24 × 80 KB WebP it is 1.9 MB. Same photos, same CDN, different encode.

Why it matters

  • Cloudflare, Fastly, and origin bandwidth are metered at scale.
  • Bots hit listing pages too.
  • You can measure this in the analytics you already have.

How to do it

  1. Find top landing pages by traffic.
  2. Convert their image sets.
  3. Watch transfer size in DevTools Network (Img filter) before/after.

Settings that work

Be aggressive on thumbnails (70–75%). Keep heroes at 75–80%.

Convert a batch in your browser. Nothing is uploaded.
Open the converter

Put it into practice

Convert your images to WebP right now, free and privately in your browser.

Open the converter

Frequently asked questions

Yes. You are replacing the object. Purge the old URLs or use new filenames.

They help leftovers. A good original still wins. See Cloudflare Polish vs local WebP.

Keep reading

Performance6 min read

Polish vs local WebP

Polish can serve WebP at the edge. Local conversion still wins for originals, offline work and hosts without Polish.

Read more
Performance6 min read

Why images are huge

The usual reasons images are huge — phone photos, PNG screenshots, 2× exports — and the WebP batch that fixes them.

Read more
Performance6 min read

Hosting and image weight

Media libraries eat disk. Convert the heaviest uploads to WebP and delete unused originals to reclaim gigabytes.

Read more