Reduce page weight and storage: convert HEIC to WebP at the edge

Many high-quality user photos now arrive as HEIC from modern phones, but HEIC is not universally supported in browsers and origin stores, so websites end up serving heavy fallbacks, storing duplicates, and incurring avoidable bandwidth and storage costs. This problem is particularly acute for image-heavy sites—social networks, marketplaces, publishers and e-commerce—across roughly 200 million websites and underpins an estimated $8.0B annual image-optimization market (200M sites × $40/yr). You could build an edge-first conversion service that auto-detects HEIC uploads or requests and transcodes to WebP (and optionally AVIF) on the CDN/edge with smart caching, origin offload, a bulk migration tool for stored assets, and developer APIs for control. Doing conversion at the edge reduces origin requests and storage duplication and typically shrinks delivered image bytes by about 20–40% versus fallback JPGs, directly lowering bandwidth and storage bills. The timing is favorable: phone-generated HEIC traffic is increasing, WebP/AVIF browser support has matured, and edge compute at major CDNs makes real-time conversion both feasible and latency-friendly. To stand out you’ll need deep CDN integrations, performant edge workers, high-quality encoding controls, transparent analytics, and competitive pricing so you can displace mid-tier incumbents on HEIC-specific workflows. Be honest about the challenges: HEIC decoding and AVIF encoding are CPU-intensive (raising edge compute costs), there are codec and licensing edge cases to manage, and go-to-market will require CDN partnerships and solid migration tooling to overcome incumbent inertia.