All our modules
Now showingWebP and AVIF Everywhere Settings Live demo

Multistore and permissions

In a multistore, the images and their copies are shared by every shop, so most settings apply to all shops. What depends on a shop’s address or pages is set per address or per shop.

What is shared, what is per shop

Applies toSettings and results
All shopsFormats and quality, Images to convert, Engine, Convert images, Automatic conversion (one cron address, built on the default shop), Clean up, Originals, the Cloudflare token, the download size saved and the disk space in Statistics. These sections say These settings apply to all shops., Copies are shared by all shops. or Originals are shared by all shops.
Each addressThe delivery mode in Delivery. Shops that share an address share its mode.
Each shopSpeed (with a value for a shop, a group or all shops, Per shop), the delivery test and PageSpeed, and the checks of the Overview that use them. Above their results, Shop tested: (in Delivery) and Shop measured: (in Statistics) list the shops: the one shown is in bold, a click on another shows its results.

The product page block is the same in every shop context. The module can be disabled in one shop with the Module Manager: the server rules then leave that shop’s addresses out, its images are no longer converted on upload there, and in that shop the header’s badge says Off in this shop.

Permissions of employees

The settings page belongs to the menu entry WebP and AVIF images (under Design). Its permissions are set per profile in Advanced Parameters › Team › Permissions:

PermissionWhat it allows
ViewOpening every section and reading its results. The page shows You can view these settings; changing them needs the Edit permission. The cron address is shown masked.
EditSaving settings, converting, testing, writing the server rules, and seeing the full cron address. The back-office conversion runs only while an employee with this permission has the back office open. The button of the product page block needs it too.
DeleteDeleting and moving copies in Clean up, and deleting backups in Originals.

Profiles that had access to the settings of version 2 keep it after the upgrade.

↑ Back to top

Upgrade from version 2

Version 3.0 is rebuilt from the ground up. It no longer needs PrestaShop’s Link override, sends the copies through server rules at the same image address, and has a new settings page. The upgrade keeps your conversion settings and your cron address, and cleans up after version 2.

Before you upgrade

  • Check the requirements: version 3.0 needs PrestaShop 1.7.8 or later (Requirements and compatibility).
  • Make a backup of the shop’s files and database, as before any module upgrade.
  • If you pasted version 2’s rules into your .htaccess or nginx configuration by hand, keep a note of where: they have to go (below).

Upgrade

  1. Download the 3.0 zip from your PrestaShop Addons account.
  2. Open Modules › Module Manager, click Upload a module and select the zip. PrestaShop recognises the newer version and runs the upgrade. If the module shows an Upgrade button instead, click it.
  3. Open Design › WebP and AVIF images. The settings page opens on the Overview.

On PrestaShop 1.7.8 the Module Manager can answer Module installed! without running the upgrade, and files copied by FTP never run it. The module then runs the upgrade itself the next time its settings page opens or the automatic conversion runs. Meanwhile the settings page says The module is finishing its update. Reload this page in a moment.; reload it after two minutes. If the upgrade fails, the page says The update of the module could not be finished: update it again from the Module Manager., with the details in Advanced Parameters › Logs.

What the upgrade does

  • The module keeps its place in the Module Manager under its new name, WebP and AVIF Everywhere (version 2 was called WebPGenerator); its technical name stays webpgenerator.
  • It takes the module’s part out of PrestaShop’s Link override; other modules’ code there stays.
  • It deletes the version 2 files and libraries the module no longer uses, and its old settings.
  • Your conversion settings (quality, AVIF, engine, EWWW key) are carried over.
  • The version 2 rules in .htaccess are replaced by the new ones, and the .htaccess backups version 2 left in the shop’s root folder move into the module’s data folder.
  • The menu entry moves to Design › WebP and AVIF images. Old menu entries and bookmarks of the version 2 pages open the matching section.
  • The version 2 cron address keeps working when its key carries over (the keys version 2 made do), and the settings page then shows the same key. If Automatic conversion still says Cron task: not called yet. a day after the upgrade, copy the Cron address of its card Cron task into your cron job. The console command of version 2 is gone: the cron address replaces it.
  • The module checks every image folder and the whole catalogue again. The copies version 2 made of catalogue images are kept, except those that do not save the share set in Formats and quality (5 % by default).

After the upgrade

  1. Open the Overview. The setup steps may open: they are worth following once (First setup in five steps). Afterwards the Overview opens on its answer: Everything works., or the things that need your attention, each with its fix.
  2. Look at Notes from the installation. Your .htaccess file still holds the WebP Generator lines you pasted by hand from version 2. means: remove the block of lines that holds the name the note gives; the module now writes its own rules. On nginx, replace version 2’s lines with the new configuration (nginx configuration).
  3. Check that the Overview does not list The address override of version 2 is still in PrestaShop (below). Under Show all checks, the check then reads The old address override is gone.
  4. In Delivery, click Test delivery now (Test delivery).
  5. In Clean up, look for the Copies made by version 2 and move the ticked ones aside (Copies made by version 2).
  6. Optional: run PageSpeed in Statistics. After an upgrade the first measurement is named Baseline (WebP delivery already active), as version 2 already sent WebP.

The address override of version 2 is still in PrestaShop

When the upgrade could not change override/classes/Link.php (the file is not writable), the Overview lists this check among the things that need your attention, and the old override keeps sending plain JPG addresses until it is removed:

  1. With your FTP program, open override/classes/Link.php in the shop folder.
  2. Remove the methods whose comment says module: webpgenerator. Keep everything else; if nothing else is left in the class, you may delete the file.
  3. Clear the cache in Advanced Parameters › Performance (Clear cache).
  4. Reload the Overview: the check no longer needs your attention, and Show all checks lists The old address override is gone.

Where version 2’s features went

Version 2Version 3.0
Image addresses rewritten by an overrideThe same addresses, served by the server rules or as sources in the page: Delivery
Regenerate pageConvert images and Automatic conversion
cwebp command and its optionsRemoved: GD, Imagick or EWWW, chosen in Engine
CDN and nginx settingsCDN and the nginx configuration of Delivery (the old values are not carried over)
Deleting the WebP images and the orphansClean up
Image comparisonCompare
Console commandThe cron address of Automatic conversion

↑ Back to top

PrestaShop 9.2’s AI assistant

On PrestaShop 9.2, the shop’s AI assistant can read how your images are doing: Ask AI in the back office, or ChatGPT, Claude and Cursor through the shop’s MCP address. WebP and AVIF Everywhere gives it five tools that only read; the AI cannot change anything and never sees a key, a token or a server folder.

What PrestaShop 9.2 offers

  • Ask AI: a chat panel on every back-office page. It needs a PrestaShop Account and your own key of an AI provider (such as OpenAI, Anthropic, Google Gemini or Mistral), set up in PrestaShop.
  • The shop’s MCP address (https://your-shop/mcp): AI programs such as ChatGPT, Claude or Cursor connect to it with an account you give them in PrestaShop, as an editor or as a viewer.

Both use “tools” that modules offer. The tools of WebP and AVIF Everywhere are ready as soon as the module is installed, enabled or upgraded through the Module Manager: there is nothing to set up in the module.

The five tools

Tool (the title the AI sees, in English in every language)What it answers
WebP and AVIF Everywhere statusThe formats and the engine, how many images have their copies per format and kind of image, the images waiting, the automatic runs, how each shop address and media server sends its images, the last delivery test, the speed settings and the checks in short.
WebP and AVIF Everywhere setup checksThe checks of the Overview, each with the menu path of its fix (for example “Design > WebP and AVIF images > Delivery”), and the notes from the installation.
WebP and AVIF Everywhere images without a copyThe images without a copy of one format: waiting, failed, kept as original or off, by kind of image, up to 100 at a time.
WebP and AVIF Everywhere savings and PageSpeedThe download size saved per format and kind of image, the last disk space count and what Clean up can remove, the optimised originals, and the first and latest PageSpeed scores and Largest Contentful Paint per page and device.
WebP and AVIF Everywhere images of one productThe images of one product with their sizes and copies, as the product page block counts them.

Questions you can ask

  • “How many of my product images have an AVIF copy?”
  • “Which checks of WebP and AVIF Everywhere need my attention, and how do I fix them?”
  • “List the images that failed to convert to WebP, and why.”
  • “How much download size do the WebP copies save? What were my PageSpeed scores at the first measurement, and now?”
  • “Does product 12 have WebP copies of all its images?”

The tools answer with figures and short English sentences; the assistant answers you in your language. Like any AI, it can misread a figure: check what matters on the Overview.

Read only, by design

  • The tools never convert, delete, test or change a setting: do that on the settings page. Because they only read, Ask AI runs them without asking for your approval, and an AI account with the viewer role may use them.
  • Their answers never contain the EWWW key, the cron token, the PageSpeed key, the Cloudflare token, a folder of your server or customer data.
  • In a multistore, the tools answer for the shop of the address the AI connects to, unless the question names another shop.

The assistant does not know the tools

  1. Check that the module is enabled, in Modules › Module Manager.
  2. Disable it and enable it again from the Module Manager, with All shops selected in a multistore: this registers its tools with PrestaShop again.

↑ Back to top

Loading...
Back to top