AVIF support and htaccess

Hello @tristanstgermain ,

Based on the screenshots, your images are being converted via the picture tag method rather than Rewrite rules. This explains why the frontend is successfully displaying AVIF images despite the Rewrite rules not being set up correctly. Additionally, the screenshots confirm that your Imagick PHP extension already supports both WebP and AVIF formats.

If you would rather use the Rewrite rules method, you can find instructions on how to configure them in these articles:

• Config Apache .htaccess | CompressX
• Config Nginx .htaccess | CompressX

Feel free to contact us if you need any further help.

Kind regards.

Hello @tristanstgermain

You’re welcome!

Both the <picture> tag method and the .htaccess (server rewrite) method are highly effective, but they have different trade-offs when it comes to performance, CDN caching, and layout compatibility.

The main advantage of the <picture> tag method is that it is completely unaffected by server-side caching or CDNs. Because the browser selects the image format directly from the HTML markup, it delivers highly predictable performance.

The downside is that because it alters the front-end HTML to insert the tag, it can occasionally conflict with some page builder modules or images loaded via CSS backgrounds. In contrast, the .htaccess rewrite method leaves the HTML entirely untouched, making it highly compatible with themes and builders, though it is much more difficult to configure alongside CDNs or Nginx server environments.

If you decide to go with the <picture> tag method and happen to notice any visual quirks or layout issues on your site, please feel free to reach out to us right away. Our development team is always actively working to expand support for edge cases, and we would be happy to jump in and investigate how to improve compatibility for your specific setup.

Kind regards,