AVIF is not generated
The active WordPress image editor must support AVIF. Confirm server codec support and the editor reported by Status.
TROUBLESHOOT OMEGA IMAGE ENGINE · WordPress Plugin 2.0.0
Troubleshooting guidance for Omega Image Engine WordPress Plugin 2.0.0, based on its audited architecture and technical boundaries.
Start with the least destructive correction. Restore/revert a high-impact change before experimenting further on a production site.
The active WordPress image editor must support AVIF. Confirm server codec support and the editor reported by Status.
Use the authenticated run/resume batch controls and review per-attachment status for failures or unsupported items.
Themes, builders, custom markup and caching/CDN layers can alter final markup. Test representative content and clear relevant caches.
Registered attachment originals, WordPress sizes and Omega variants are intentionally protected. Only unregistered orphan duplicates are deletion candidates.
This is deliberate so cached/external references are not broken. Settings/metadata cleanup is separate from generated-file preservation.
AVIF/WebP output depends on the host and active WordPress image editor. Themes, page builders, custom markup and caching/CDN layers can affect final frontend picture/srcset delivery. Image optimization cannot by itself guarantee a specific page-speed or Core Web Vitals score.
Review the complete public-facing capability specification, pricing and licence information for Omega Image Engine.