Skip to content
webp for TYPO3 CMS processed files
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
Classes [BUGFIX] Remove unnecessary call-by-reference for object argument Mar 19, 2019
Documentation [FEATURE] Add external adapter (custom binary) possibility Mar 19, 2019
.gitignore Convert all images in every local and writable storage Jan 28, 2019
LICENSE Initial commit Mar 13, 2018 [TASK] Update README on requirement verification Mar 19, 2019
composer.json Merge branch 'reST' Mar 19, 2019
ext_conf_template.txt [FOLLOWUP] Update label Mar 19, 2019

WebP for TYPO3 CMS LTS 8 and 9

Adds an automagically created WebP copy for every processed jpg/jpeg/png image in the format


What is WebP and why do I want it?

WebP is a modern image format that provides superior lossless and lossy compression for images on the web. Using WebP, webmasters and web developers can create smaller, richer images that make the web faster.

WebP lossless images are 26% smaller in size compared to PNGs. WebP lossy images are 25-34% smaller than comparable JPEG images at equivalent SSIM quality index.

Lossless WebP supports transparency (also known as alpha channel) at a cost of just 22% additional bytes. For cases when lossy RGB compression is acceptable, lossy WebP also supports transparency, typically providing 3× smaller file sizes compared to PNG.

— source:


Add via composer:

composer require "plan2net/webp"
  • Install and activate the extension in the Extension manager
  • Flush TYPO3 and PHP Cache
  • Clear the processed files in the Install Tool or Maintenance module


Your version of ImageMagick or GraphicsMagick on the server needs to support WebP (obviously).

You can test the support of GraphicsMagick with e.g.:

gm version | grep WebP

(should return yes)

or using ImageMagick with e.g.:

convert version | grep webp

(should return a list of supported formats including webp)

These are examples, check your system documentation for further information on how to verify webp support on your platform.

Extension manager configuration

You can set parameters for the conversion in the extension configuration.


# cat=basic; type=string; label=Webp conversion parameters (for internal or external adapter)
parameters = -quality 95 -define webp:lossless=false

You find a list of possible options here:

or here:

Default value is:

-quality 95 -define webp:lossless=false

which has (in our experience) a minor to no impact on visual difference to the original image.


Try to set a higher value for quality first if the image does not fit your expectations, before trying to use webp:lossless=true, as this could even lead to a higher filesize than the original!


# cat=basic; type=boolean; label=Convert all images in local and writable storage and save a copy as Webp; disable to convert images in the _processed_ folder only
convert_all = 1

Since version 1.1.0 all images in every local and writable storage will be converted to Webp by default (instead of just images modified by TYPO3 in the storage's processed folder). If you want to revert to the previous behaviour, set this flag to false (disable the checkbox).

Webserver example configuration

Please adapt the following to your specific needs, this is only an example configuration.


Add a map directive in your global nginx configuration:

map $http_accept $webp_suffix {
    default   "";
    "~*webp"  ".webp";

and add these rules to your server configuration:

location ~* ^/fileadmin/.+\.(png|jpg|jpeg)$ {
        add_header Vary Accept;
        try_files $uri$webp_suffix $uri =404;
location ~* ^/other-storage/.+\.(png|jpg|jpeg)$ {
        add_header Vary Accept;
        try_files $uri$webp_suffix $uri =404;

Make sure that there are no other rules that already apply to the specified image formats and prevent further execution!

Apache (.htaccess example)

<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteCond %{HTTP_ACCEPT} image/webp
    RewriteCond %{DOCUMENT_ROOT}/$1.$2.webp -f
    RewriteRule ^(fileadmin/.+)\.(png|jpg|jpeg)$ $1.$2.webp [T=image/webp,E=accept:1]
    RewriteRule ^(other-storage/.+)\.(png|jpg|jpeg)$ $1.$2.webp [T=image/webp,E=accept:1]

<IfModule mod_headers.c>
    Header append Vary Accept env=REDIRECT_accept

AddType image/webp .webp

Make sure that there are no other rules that already apply to the specified image formats and prevent further execution!

Removing processed files

You can remove the created .webp files at any time within the TYPO3 CMS backend.


  • Go to System > Install > Clean up
  • Click the Clear processed files button


  • Go to Admin Tools > Remove Temporary Assets
  • Click the Scan temporary files button
  • In the modal click the button with the path of the storage

Although the button names only the path of the _processed_ folder, all processed files of the storage are actually deleted!


You can get an equal result with using the Apache mod_pagespeed or nginx ngx_pagespeed modules from Google with a configuration like:

pagespeed EnableFilters convert_jpeg_to_webp;
pagespeed EnableFilters convert_to_webp_lossless;

but that requires more knowledge to set up.

Drawbacks to keep in mind

Note that this extension produces an additional load on your server (each processed image is reprocessed) and possibly creates a lot of additional files that consume disk space (size varies depending on your ImageMagick/GraphicsMagick configuration).


This extension was inspired by Angela Dudtkowski's cs_webp extension that has some flaws and got no update since early 2017. Thanks Angela :-)


Release Changes
1.1.0 Convert all images in every local and writable storage
Fix fallback options for conversion
You can’t perform that action at this time.