Image optimization plugins for WordPress promise faster page loads and better Core Web Vitals scores. Most now offer WebP conversion by default, and a growing number add AVIF support. But the two formats solve different problems, and choosing the wrong one can break images for a slice of your traffic or bloat your hosting bill.
Here’s how to pick the right format—and when to use both.
WebP: mature, compatible, predictable file sizes
WebP has been around since 2010. Browser support hit critical mass years ago: Chrome, Firefox, Safari, and Edge all support it natively. According to Can I Use data, WebP coverage sits above 97% of global users in 2026.
WebP handles both lossy and lossless compression. For most photography and blog post images, WebP lossy at 80–85 quality produces files 25–35% smaller than JPEG at equivalent visual quality. Lossless WebP beats PNG for screenshots and graphics with transparency, though the size advantage is smaller—usually 15–20%.
The format supports alpha-channel transparency, which makes it a direct PNG replacement. If your site uses transparent logos, icons, or overlays, WebP won’t break them.
Most WordPress image optimization plugins—ShortPixel, Imagify, Smush, EWWW Image Optimizer—convert to WebP automatically. The format is stable, well-tested, and won’t surprise you with edge cases.
AVIF: smaller files, slower encoding, spottier support
AVIF arrived later—Chrome added support in 2020, Safari in 2021. Browser coverage in 2026 hovers around 92%, which means 8% of visitors still can’t decode it. That gap includes older Android devices and some corporate-locked browsers.
AVIF’s advantage is file size. At equivalent quality settings, AVIF images run 20–30% smaller than WebP and 40–50% smaller than JPEG. For image-heavy sites—portfolios, e-commerce galleries, photo blogs—that difference compounds fast.
The tradeoff is encoding time. Generating AVIF files takes 3–5× longer than WebP on most hosting environments. If your plugin converts images on-upload or via cron job, AVIF processing can time out on shared hosting or budget VPS plans. Plugins like ShortPixel and Imagify offload conversion to their own servers, which sidesteps the timeout problem but adds API dependency.
AVIF also handles transparency, but browser support for alpha-channel AVIF lags slightly behind opaque AVIF. If you’re converting transparent PNGs to AVIF, test rendering in Safari and Firefox before deploying site-wide.
When to use WebP, AVIF, or both
If your hosting plan is shared or low-tier VPS, stick with WebP. AVIF encoding can spike CPU usage and trigger resource limits. WebP delivers most of the file-size benefit without the processing cost.
If you’re on managed WordPress hosting or a dedicated server with headroom, enable AVIF with WebP fallback. Most modern plugins support this: serve AVIF to browsers that accept it, WebP to the rest, and original JPEG/PNG as a last resort. The plugin detects support via the Accept HTTP header or generates a <picture> element with multiple <source> tags.
For e-commerce sites with hundreds of product images, AVIF’s size advantage matters. A 30% reduction in image payload can shave a full second off Largest Contentful Paint on mobile. That translates to measurable conversion lift. Just make sure your plugin queues conversions in the background—batch-converting 500 images at once will lock up most hosting environments.
For blogs with a few images per post, WebP is enough. The complexity of AVIF fallback chains and the 8% browser gap aren’t worth the incremental file-size win.
One plugin detail that trips people up
Most WordPress image optimization plugins store multiple formats of the same image—original JPEG, WebP, and AVIF—on disk. A single uploaded image can generate three or four files, depending on your settings. If you’re on a hosting plan with tight disk quotas, this adds up fast. A 2 GB media library can balloon to 5–6 GB after enabling both WebP and AVIF.
Check your plugin’s settings for an option to delete originals after conversion. Some plugins keep the source file for rollback purposes; others let you purge it once the optimized versions are live. If disk space is tight, delete originals—but keep a local backup of your media library first.
Want more tool breakdowns like this? Subscribe to One Two Three Send for weekly deep-dives on the platforms and plugins that run online businesses.