Q: When using Server Redirects, it doesn't seem to serve WebP images.

A: Using your browser dev tools, check the mime type via the Network tab. It should say webp. PageSpeed Insignts will recognize these as webp images even though they are labeled with the .jpg or .png extension.

Q: I do not see WebP images while logged in.

A: We do not serve the WebP images to editors who are logged in unless you are using the Server Redirects option.

Q: Do I need to use Server Redirects?

A: No, this is just an option that may increase the efficiency of the image delivery. We have seen that performance can be better without using Server Redirects. You can do your own testing to see which works best for you.

Q: Server Redirects are not working.

A: See Below:

This feature is experimental and does not work on all environments. If you are not a developer, please use only the General Settings. We will are not actively supporting this functionality due to environment differences.

1. Make sure the htaccess rules have been applied. If not, try enabling Pretty URLs first then apply then the htaccess rule back on.
2. You may need to edit the htaccess file on your server directly if no changes are seen to the file.
3. You will need to have an Apache server setup to utilize htaccess files for this feature.
4. If using Laragon for local development, restart Apache / Laragon after the htaccess file has been written.
5. If you have an Nginx server, you can view the example settings we have in System & Settings > Optimization > WebP Settings. Below are the htaccess rules in case you need to manually add them:

# -- webp handler start
<IfModule mod_setenvif.c>
    # Vary: Accept for all the requests to jpeg and png
    SetEnvIf Request_URI "\.(jpe?g|png)$" REQUEST_image
</IfModule>
<ifModule mod_rewrite.c>
	RewriteEngine On

	# If the Browser supports WebP images, and the .webp file exists, use it.
	RewriteCond %{HTTP_ACCEPT} image/webp
	RewriteCond %{REQUEST_URI} ^/?application/.*\.(jpe?g|png)
	RewriteCond %{REQUEST_FILENAME}.webp -f
	RewriteRule ^/?(.*)$ $1.webp [NC,T=image/webp,END]

	# If the Browser supports WebP images, and the .webp file does not exist, generate it.
	RewriteCond %{HTTP_ACCEPT} image/webp
	RewriteCond %{REQUEST_URI} ^/?application/.*\.(jpe?g|png)
	RewriteCond %{REQUEST_FILENAME}\.webp !-f
	RewriteRule ^/?(.*)$ index.php/webp-process-image [NC,END]
</ifModule>
<IfModule mod_headers.c>
	Header append Vary Accept env=REQUEST_image
</IfModule>
<IfModule mod_mime.c>
	AddType image/webp .webp
</IfModule>
# -- webp handler end

Q: Any Reason to use Dynamic URLs?

A: Its not our recommendation to use this feature, but some may want to enable it for debugging or using the image conversion in a different manner.

Q: WebP Image Quality setting doesn't seem to change the image size.

A: We've seen that this setting can have little effect on small images or on servers without certain extensions. Servers with ImageMagick or GraphicsMagick extensions installed will probably see better results here.

Q: Not all of my images are being converted.

A: We've limted the conversions to images found in the application directory and img tags on the page. Background images and theme images will not be converted. We didn't want to overstep when those can be converted manually and uploaded outside of the file manager.