{"id":727,"date":"2024-05-07T11:42:16","date_gmt":"2024-05-07T11:42:16","guid":{"rendered":"https:\/\/kb.shortpixel.com\/docs\/how-to-deliver-the-webps-generated-with-shortpixel-with-the-litespeed-cache-plugin\/"},"modified":"2025-08-27T08:45:36","modified_gmt":"2025-08-27T08:45:36","password":"","slug":"how-to-deliver-the-webps-generated-with-shortpixel-with-the-litespeed-cache-plugin","status":"publish","type":"docs","link":"https:\/\/kb.shortpixel.com\/knowledge-base\/article\/how-to-deliver-the-webps-generated-with-shortpixel-with-the-litespeed-cache-plugin\/","title":{"rendered":"How to deliver the WebP generated by ShortPixel with LiteSpeed Cache"},"content":{"rendered":"\n
\n

If you previously followed the instructions on this page and discover that some or all of your WebP image files are missing, it is likely due to a change<\/a> the LiteSpeed team introduced in LiteSpeed Cache 5.4. To resolve this, please proceed with the following steps:<\/p>\n

    \n
  1. Upgrade to the latest version of ShortPixel Image Optimizer (at least 5.3.0).<\/li>\n
  2. Add this line to the functions.php file (or via the Code Snippets<\/a> plugin): add_filter('shortpixel\/image\/filecheck', function () { return true; });<\/code><\/li>\n
  3. Run again the ShortPixel bulk optimization<\/a> to generate the missing WebP files.<\/li>\n
  4. Remove the line from step #2.<\/li>\n<\/ol>\n<\/div>\n\n\n\n

    Instructions<\/h2>\n\n\n\n

    If you want to use LiteSpeed Cache instead of ShortPixel Image Optimizer (SPIO) to deliver the WebP files,\u00a0but still use SPIO to create them, you need to do the following:<\/p>\n\n\n\n

    1. Add this line to your wp-config.php<\/code> file. Please do this before <\/strong>you optimize your images.<\/p>\n\n\n\n

    define('SHORTPIXEL_USE_DOUBLE_WEBP_EXTENSION', true);<\/code><\/pre>\n\n\n\n
    This constant makes ShortPixel Image Optimizer to generate WebP files with a double extension (xxxxx.jpg.webp<\/code> or xxxxx.png.webp<\/code>), which is required by LiteSpeed Cache.<\/p>\n\n\n\n
    If you already optimized images with ShortPixel before adding the constant, you will need to bulk restore<\/a> your images, add the previous constant, and then run the bulk optimization again. Another solution in case you already have WebP files with a single extension is to rename your xxxxx.webp<\/code> files, as described in this other article<\/a>.<\/p>\n\n\n\n
    2. Go to the LiteSpeed Cache > Image Optimisation <\/strong>menu:<\/p>\n\n\n\n
    \"\"\/<\/figure>\n\n\n\n
    3. Click the “Image Optimization Settings<\/strong>” tab:<\/p>\n\n\n\n
    \"\"\/<\/figure>\n\n\n\n
    3. Enable “Image WebP Replacement<\/strong>” and “WebP For Extra srcset<\/strong>“:<\/p>\n\n\n\n
    \"\"\/<\/figure>\n\n\n\n
    4. Set the rest of LiteSpeed’s image optimization settings to OFF<\/strong>. They should be enabled only if you want to optimize your images with LiteSpeed instead of ShortPixel.<\/p>\n\n\n\n
    5. Go to Settings > ShortPixel > WebP\/AVIF & CDN and disable both “Deliver the next generation images using the ShortPixel CDN<\/strong><\/strong>” and “Serve WebP\/AVIF images from locally hosted files (without using a CDN)<\/strong>“. Remember that LiteSpeed is now responsible for delivering WebP, not ShortPixel.<\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    Alternatives<\/h2>\n\n\n\n
    If you cannot use this method, you should try an alternative solution for WebP image delivery:<\/p>\n\n\n\n