Existing images, CDNs and caching
Why old Media Library images stay JPEG, how to replace them, and why a CDN, cache or theme can still show the old file.
Images uploaded before the plugin
WebP Auto Convert works on new uploads only. It never touches files already in the Media Library, so older posts keep their JPEG and PNG images. To convert an important image, download it, upload it again and replace it in the post or block. For a large back catalogue, a bulk optimisation tool is the better fit; this plugin is designed to keep new uploads light from now on.
I re-uploaded but the page still shows the JPEG
- The page still points at the old attachment. Replace the image in the block, widget or builder module, then update the page.
- A page cache is serving an old copy. Clear your caching plugin and any host cache.
- A CDN or image proxy is caching the old file. Purge it, or wait for it to expire.
- The image is set in the theme or a stylesheet (a background image, logo or header) with a hard-coded URL. Change it in the Customizer, Site Editor or builder setting where it is defined.
CDNs and offload plugins
Because the WebP is the real file, any CDN or offload plugin simply serves it like any other image — there is no special rewriting to configure. If a CDN also converts images on the fly, you do not need both; pick one.
Do browsers support WebP?
Every current browser shows WebP, including Safari on iPhone and Mac (since iOS 14 and macOS Big Sur). Very old browsers are the only ones that cannot, and the plugin does not keep a JPEG fallback for them.
Did this answer the question? No — open a support request