Troubleshooting
LiteSpeed Cache Image Optimization Not Working: Causes and How to Fix It

Short answer
LiteSpeed Cache image optimization usually stops because the site is not linked to QUIC.cloud, the quota has run out, cron is not pulling finished images, or a firewall blocks QUIC.cloud's callbacks. Reconnect the service, check quota, fix cron and allowlist QUIC.cloud's IP addresses.
Key takeaways
- Images are optimized on QUIC.cloud, not your server.
- A broken QUIC.cloud connection stops every request.
- Automatic pulls depend on a working cron.
- Firewalls must let QUIC.cloud reach your REST API.
- Turn on next-gen image replacement and purge cache.
Why is LiteSpeed Cache image optimization not working?
LiteSpeed Cache image optimization usually fails because the site is not linked to QUIC.cloud, images are stuck waiting to be pulled back, a firewall blocks QUIC.cloud's callbacks, or your quota has run out.
Image optimization in the LiteSpeed Cache plugin does not happen on your own server. The plugin sends your images to QUIC.cloud, which compresses them and creates WebP or AVIF copies. Your site then pulls the optimized files back.
That round trip has several steps, and a break at any point leaves images unoptimized. The checks below follow the same order as the process.
If you want a refresher on the plugin first, read our guide to what LiteSpeed Cache does.
How does the image optimization process work?
The plugin sends an optimization request, QUIC.cloud processes the images, notifies your site, and your site pulls the optimized versions back, either automatically by cron or when you click to pull.
Each image moves through a series of statuses. Knowing them tells you where things are stuck.
| Stage | What happens | If it stalls |
|---|---|---|
| Requested | Your site sends images to QUIC.cloud | Check the QUIC.cloud connection and quota |
| Notified | QUIC.cloud tells your site images are ready | Check firewall and REST API access |
| Pulled | Your site downloads the optimized files | Check cron, file permissions and outbound connections |
| Failed | Something went wrong for that image | Check the image file and error details |
You can see the counts for each status on the Image Optimization summary screen in LiteSpeed Cache. LiteSpeed's own image optimization documentation explains each field.
Is your site connected to QUIC.cloud?
Image optimization needs a working connection between your WordPress site and a QUIC.cloud account, so a missing, expired or broken link stops every request.
In LiteSpeed Cache, check the general settings for the QUIC.cloud connection status. Recent versions guide you through linking the site to a QUIC.cloud account from the dashboard.
If the connection shows an error, try reconnecting. This often fixes problems after a domain change, a migration or a restore from backup, because the old connection details no longer match the site.
Our walkthrough on setting up LiteSpeed Cache with QUIC.cloud covers the linking steps in detail.
Have you run out of image optimization quota?
QUIC.cloud gives each account a limited image optimization quota, and once it runs out, new requests wait or fail until the quota renews or you add credit.
Log in to your QUIC.cloud dashboard and check the image optimization usage for your domain. Free allowances and paid credit amounts change over time, so check the current figures on the QUIC.cloud image optimization page.
Large media libraries use quota fast, because every thumbnail size counts as an image. If you have many registered image sizes, each upload creates several files to optimize.
You may also see a message about too many requested images. That means you have hit a short-term request limit. Wait a few minutes and send the next batch.
Are images stuck waiting to be pulled?
If many images show as notified but not pulled, your site has not downloaded the finished files yet, usually because automatic pulling relies on cron or the pull request is failing.
LiteSpeed Cache has an option to pull images automatically using a cron job. If WP-Cron does not run, the pull never happens.
Check whether WP-Cron works. Look for DISABLE_WP_CRON in wp-config.php. If it is set to true, a real server cron must call wp-cron.php. Our guide to fixing WP-Cron not running covers both cases.
You can also start a manual pull from the Image Optimization summary screen. If manual pulling works but automatic does not, cron is the problem.
Is a firewall blocking QUIC.cloud?
Security plugins, host firewalls or Cloudflare rules that block QUIC.cloud's servers stop them from notifying your site, so images never move past the requested stage.
QUIC.cloud needs to reach your site's REST API to tell it images are ready. If that request is blocked or challenged, your site never hears back.
Check these areas:
- Security plugins that block or rate-limit REST API calls.
- Host firewalls such as ModSecurity rules.
- Cloudflare bot protection or WAF rules.
- Plugins that disable the WordPress REST API entirely.
QUIC.cloud publishes the IP addresses its servers use. Allowlist them in your firewall and security plugin. The QUIC.cloud image optimization troubleshooting guide lists the most common blocks.
Can your server download the optimized images?
Your server must be able to make outbound HTTPS requests and write files to the uploads folder, otherwise pulls fail even when QUIC.cloud has finished.
Two server-level problems show up here:
- Outbound requests blocked. Some hosts limit outgoing connections. Ask your host whether outbound HTTPS to QUIC.cloud is allowed.
- Folder permissions. WordPress must be able to write to wp-content/uploads. Folders are usually set to 755 and files to 644.
The WordPress Site Health screen under Tools flags many of these issues, including REST API and loopback request failures.
Why are WebP or AVIF images not showing?
Optimized next-gen images only appear when the replacement setting is on and the browser supports the format, and caching can hide the change until you purge.
LiteSpeed Cache can create WebP or AVIF copies and swap them in for supported browsers. These modern image formats are usually much smaller than JPEG or PNG. If the replacement option is off, visitors still get the original JPEG or PNG files even though the optimized copies exist.
After you turn replacement on, purge the LiteSpeed cache so pages are rebuilt. Our guide on how to purge LiteSpeed Cache shows each method.
To check what a visitor gets, open your browser's developer tools, go to the Network tab and click an image. The type column shows whether it is WebP, AVIF or the original format. For help choosing a format, see our comparison of WebP vs AVIF for WordPress.
Why do some images fail?
Individual images fail when the original file is missing, corrupt, too large, an unsupported format, or already well compressed.
Images often fail after a migration that did not copy every file, or when a plugin deleted originals. If the file is not on disk, QUIC.cloud has nothing to work with.
Very large images or unusual formats may also be skipped. The LiteSpeed Cache media troubleshooting guide describes how to inspect a single image's status in the Media Library.
Some images save almost nothing when compressed again. That is normal for files that were already optimized before upload.
How do you reset image optimization and start again?
LiteSpeed Cache includes tools to clean up unfinished optimization data and, if needed, remove all optimization data so you can start fresh.
Use these tools carefully, in this order:
- Try a manual pull first, in case images are simply waiting.
- Use the clean up option for unfinished data to clear stuck requests.
- Send a new optimization request and wait.
- Only as a last resort, destroy all optimization data and restore originals.
Take a full backup before the last step, including the uploads folder. Removing optimization data deletes the optimized copies and can take time on large libraries.
When should you contact support?
Contact LiteSpeed or QUIC.cloud support when the connection is working, quota is available, cron runs, and firewalls are allowlisted, but images still do not move.
Include your domain, a screenshot of the summary screen, and any error messages. Support can see the request logs on the QUIC.cloud side.
You can also post in the plugin's WordPress.org support forum, where the developers reply to many questions. If image optimization keeps causing trouble, a separate image plugin is a valid alternative, and our guide to optimizing images for WordPress covers the options.
Frequently asked questions
Why are my LiteSpeed images stuck on requested?
QUIC.cloud has received the images but has not been able to tell your site they are ready, or is still processing them. Check that your firewall and security plugins allow QUIC.cloud's servers and that the REST API is not disabled, then wait and check again.
Does LiteSpeed Cache image optimization work on any host?
The plugin runs on any host, and image optimization uses QUIC.cloud rather than the LiteSpeed web server. Page caching features need a LiteSpeed server, but image optimization only needs a working QUIC.cloud connection and outbound access.
Is LiteSpeed image optimization free?
QUIC.cloud offers a limited free allowance, with paid credit for more. The limits change over time, so check the current QUIC.cloud pricing before optimizing a large media library.
Will optimizing images replace my originals?
LiteSpeed Cache keeps backups of the original images by default, so you can revert. Keep that option on unless disk space is very tight, and always take a full backup before removing optimization data.
Why do I still see JPEG images after optimization?
Next-gen image replacement may be off, your browser may not support the format, or the page is still served from an old cache. Turn on the replacement setting, purge all caches, and check the image type in your browser's network panel.
Sources
- Image optimization LiteSpeed Documentation
- Media troubleshooting LiteSpeed Documentation
- Image optimization service QUIC.cloud
- Image optimization troubleshooting QUIC.cloud
- Site Health screen WordPress.org
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


