WebP and AVIF can reduce image transfer size while preserving useful quality, but test the complete upload, processing and delivery path on your actual WordPress installation. Support depends on the version, processing method, plugins and hosting environment.
IN THIS ARTICLE
01 Check the active processing path
Review Site Health media information and the installed WordPress version. Server-side processing commonly relies on image-library support. Newer WordPress releases can process supported uploads in the browser, so a missing server format capability does not describe every possible upload path.
Keep original source files and test with a small representative collection before converting an entire library. Include photographs, transparent graphics and images containing fine text.
02 Run a controlled format test
- Export a web copy in the intended format using a trusted image tool.
- Upload it to a draft or staging site and confirm that WordPress creates the sizes your layout needs.
- Insert it into the relevant block or product image field.
- Open the public test page on representative browsers and inspect quality, transparency and the delivered file size.
- Check any CDN or image-optimisation service for additional conversion rules.
03 Plan conversion of existing media
Uploading new formats does not automatically replace every older image already embedded in content. A conversion plugin or deployment process must handle metadata, generated sizes and URL references deliberately.
Use one coordinated optimisation workflow rather than several plugins independently generating competing variants. Review storage use because retaining originals, old thumbnails and new-format copies can increase disk consumption even while visitor downloads become smaller.
What should I do if WebP or AVIF processing fails?
If a format fails, retain a compatible source and record the exact upload or processing error. Do not rename a JPEG extension to AVIF or delete originals before checking the converted files.
For a bulk conversion, back up files and the database, test a limited set and verify rollback. Measure actual page delivery rather than assuming the new format is always smaller at the quality you need. If a browser or integration cannot use the chosen format, provide a supported fallback through a documented image-delivery approach.