Frontend Delivery
Understand GetWebP's standard WordPress WebP delivery path and its boundaries in the free plugin.
Frontend Delivery
The free plugin uses standard WordPress delivery for generated WebP files. It does not write server rewrite rules and does not automatically serve AVIF on the frontend.
Generated AVIF files can still be useful for compatible workflows, but the built-in free delivery path focuses on WebP.
Table of Contents#
- How Standard Delivery Works
- Covered Image Paths
- AVIF Boundary
- WooCommerce and Page Builders
- Caching
- Disabling Delivery
How Standard Delivery Works#
When generated WebP files exist, GetWebP uses WordPress filters to replace eligible attachment image URLs with generated WebP sibling URLs.
This happens in WordPress output paths, not at the web server rewrite layer. Originals stay in place, so unsupported or unreplaced image paths can still use the original JPEG or PNG file.
Covered Image Paths#
The free plugin covers common WordPress Media Library paths:
| Path | Behavior |
|---|---|
| Attachment image attributes | Replaces src when a generated WebP exists |
WordPress srcset | Replaces matching size URLs with generated WebP URLs |
| Post content images | Rewrites wp-image-* image tags where attachment status is known |
| Featured images | Rewrites featured image HTML where possible |
Images outside the Media Library, external URLs, CSS files, and custom markup may not be rewritten.
AVIF Boundary#
The free plugin can generate AVIF files when AVIF output is enabled, but standard frontend delivery serves generated WebP files. Use AVIF files in workflows where your theme, CDN, or custom templates explicitly reference them.
WooCommerce and Page Builders#
WooCommerce product images that use standard WordPress attachments can be optimized and may be delivered as WebP through the same WordPress paths.
Some builders and lazy-load plugins generate custom markup. If delivery does not appear on a specific template, inspect the final HTML and confirm the image still maps to a WordPress attachment.
Caching#
After a large optimization run, clear:
- WordPress page cache
- minification/cache plugin output
- CDN cache
- object-storage/offload sync, if used
Generated files are written locally first. CDN delivery depends on whether your CDN or offload plugin syncs those generated sibling files.
Disabling Delivery#
To stop standard WebP delivery while keeping generated files:
- Go to GetWebP -> Settings.
- Keep or remove generated files from Maintenance depending on your goal.
- Deactivate the plugin if you want WordPress to serve originals only.
Original images remain untouched.