21 Nov 2026 · 7 min read · EN

Troubleshooting LSIO: LQIP failures, file-count bloat, and AVIF/WebP issues on cPanel WordPress

If LiteSpeed Image Optimization (LSIO) is failing to create LQIPs or you see a sudden surge in files (WebP/AVIF copies), check QUIC.cloud settings, queues, and requeue steps in the LiteSpeed Cache plugin before deleting anything.

By Tim Gocelerus

Troubleshooting LSIO: LQIP failures, file-count bloat, and AVIF/WebP issues on cPanel WordPress

Problem: LQIP generation can fail and image optimization can produce a large number of native WebP/AVIF files that blow up inode or file counts on cPanel WordPress hosts. Below are focused checks and actions to diagnose and recover without guessing at plugin internals.

Quick summary of how LSIO works (what matters for troubleshooting)

  • LiteSpeed Image Optimization (LSIO) runs as a QUIC.cloud service invoked by the LiteSpeed Cache for WordPress plugin (LSCWP). You must enable QUIC.cloud services in the plugin General settings before optimization requests are sent.
  • Image Optimization is managed in WordPress under LiteSpeed Cache > Image Optimization > Image Optimization Settings. The plugin uses two processing queues: Standard Queue (free, unlimited) and Advanced Queue (free monthly quota; AVIF requires Advanced Queue and may stop when that quota is exhausted). You choose Next-Gen Image Format in Image Optimization Settings (options such as WebP or AVIF).

Sources for these behaviors are the LiteSpeed docs and the plugin blog (see sources list).

Before you change files: gather diagnostics

  1. Confirm QUIC.cloud services are enabled in the plugin General settings. If QUIC.cloud is not enabled, no remote optimization requests will be sent.

  2. Check the Image Optimization UI:

    • In WordPress go to LiteSpeed Cache > Image Optimization > Image Optimization Summary.
    • Review any reported failures and the counts for processed, pending, and failed images.
  3. Check whether you chose AVIF as the Next-Gen Image Format:

    • In WordPress go to LiteSpeed Cache > Image Optimization > Image Optimization Settings and check Next-Gen Image Format. AVIF uses the Advanced Queue and is subject to its monthly quota; if the Advanced quota is exhausted AVIF requests can be paused.
  4. Check file and inode usage on the server (SSH). Useful quick commands:

# total files under uploads
find wp-content/uploads -type f | wc -l

# count WebP or AVIF files (case-insensitive)
find wp-content/uploads -type f -iname "*.webp" | wc -l
find wp-content/uploads -type f -iname "*.avif" | wc -l

# check inode usage on the filesystem containing uploads
df -i $(df wp-content/uploads -P | tail -1 | awk '{print $6}')

# disk usage for uploads folder
du -sh wp-content/uploads

These tell you if image conversions have multiplied files and whether inode exhaustion is plausible.

Typical causes and targeted fixes

1) LQIP generation failures (especially when originals are already WebP/AVIF)

Why it happens: LQIP (low-quality image placeholders) generation can fail when the optimization workflow encounters native next-gen images or unexpected source formats. There have been fixes in the plugin codebase addressing failure modes for native WebP/AVIF; plugin versions and QUIC.cloud behavior matter.

Fix steps:

  1. Ensure QUIC.cloud services are enabled in the plugin General settings (otherwise remote optimization won't run).
  2. If you enabled AVIF recently, consider switching Next-Gen Image Format back to WebP temporarily in LiteSpeed Cache > Image Optimization > Image Optimization Settings to see whether LQIP generation succeeds with the Standard Queue.
  3. In the Image Optimization area use Image Optimization > Image Optimization Summary and click "Soft Reset Optimization Counter" (under Optimization Tools) to clear counters for items that failed due to transient conditions.
  4. Use "Send Optimization Request" (from Image Optimization Summary) to requeue images for processing. If you have large numbers of files, use Auto Request Cron to let the plugin requeue gradually.
  5. If you prefer automation or need bulk requeueing outside the UI, consult the plugin's WordPress CLI documentation for requeue/optimization commands.

Note: If AVIF is required, be aware AVIF generation requires the Advanced Queue (quota-limited). If your Advanced quota is exhausted, AVIF requests will not run successfully until quota is available.

2) Inode or file-count bloat from generated image files

Why it happens: Each converted next-gen image, LQIP, or additional version may create extra files in uploads. Sites with many small images (icons, thumbnails, avatars) can suddenly hit inode limits.

How to diagnose:

  1. Use the file-count commands above to confirm the uploads directory file count and how many converted files exist by extension.
  2. If you see many converted files, identify whether they are coming from a recent bulk optimization run or from repeated requeues.

How to recover safely:

  1. Do not delete anything until you know which files are originals and which are generated by LSIO. Usually originals are the formats you uploaded (JPEG/PNG) while conversion-produced files will have .webp or .avif extensions; LQIP placeholders may be small images.
  2. If you need to free inodes quickly, you can remove conversion outputs while retaining originals. Example find command to preview converted files (do not run the delete command until you confirm):
# show counts per extension
find wp-content/uploads -type f -printf "%f\n" | sed -n 's/.*\.\([^.]*\)$/\1/p' | sort | uniq -c | sort -n
  1. Once you confirm which files are conversion outputs, remove them with targeted commands (take a backup first). After cleanup, use the plugin UI to requeue optimization with controlled settings (e.g., WebP + Standard Queue) so you avoid a repeat surge.

  2. Long term: if you need AVIF but have limited Advanced quota, either buy additional Advanced quota in your QUIC.cloud account or keep AVIF disabled until quota is scheduled. AVIF generation will be paused when Advanced quota is exhausted.

3) Failed optimizations that are quota- or queue-related

Checks and fixes:

  1. Confirm whether an image optimization attempt used the Advanced Queue by checking the Image Optimization Summary and your QUIC.cloud account usage (QUIC.cloud account is required for Advanced quota purchase).
  2. If AVIF generation is failing site-wide and you do not have Advanced quota, change Next-Gen Image Format to WebP in the plugin settings and requeue; WebP can be generated using the Standard Queue which is free and unlimited.
  3. Use "Soft Reset Optimization Counter" and then "Send Optimization Request" to restart processing for images that previously failed.

If you still see failures

  • Check for known bug fixes: the plugin repository has addressed LQIP generation failures for native WebP/AVIF in code updates. If your plugin is older than the release that introduced AVIF support or the fix, update the plugin per standard WordPress update procedures and retry.
  • Use the Image Optimization Summary to spot per-image failure messages and requeue only failed items where possible.
  • For automation or scripting, consult the plugin's WordPress CLI documentation for commands to requeue or inspect optimization state.

Checklist before you call host support

  • QUIC.cloud services enabled in LiteSpeed Cache General settings.
  • Check Next-Gen Image Format and decide AVIF vs WebP based on whether you have Advanced quota.
  • Soft Reset Optimization Counter and use Send Optimization Request (or Auto Request Cron) to requeue.
  • Count files and inodes using SSH so you can describe the scale of the problem.
  • If you plan deletions, take a backup first.

Closing note

Gocelerus is cPanel web hosting for Southeast Asia, serving Indonesia and Cambodia first; servers are in Singapore with NVMe storage, LiteSpeed web server, Imunify360 security, daily backups included, and free site migrations are provided by the team.

Sources

Manage your cPanel servers from one dashboard

Connect your WHM to Gocelerus and manage PHP, SSL, and WordPress across all your cPanel accounts from one place.