GetWebP - Local Image Converter Logo
文档

Troubleshooting

Diagnose common free GetWebP WordPress issues with browser-side optimization, writable uploads, delivery, and caching.

Troubleshooting

This page covers the current free WordPress plugin. It does not assume automatic upload optimization, a background queue, server rewrite rules, or server-side encoding.

Table of Contents#

Optimization Does Not Start#

Check:

  1. Browser support — use a current desktop Chrome, Edge, Firefox, or Safari.
  2. Secure admin page — load WordPress admin over HTTPS when possible.
  3. Uploads writable — confirm WordPress can write to wp-content/uploads.
  4. Same-site requests — security plugins should not block authenticated admin AJAX or source-image requests.
  5. Eligible inputs — use JPEG, PNG, or BMP attachments; animated PNG, GIF, HEIC, and HEIF are not processed by the Free package.

Scan or Preview Is Disabled#

Check:

  1. The Media Library has eligible JPEG, PNG, or BMP images.
  2. No scan, batch, or settings save is already running.
  3. The current user has permission to manage the plugin and edit the target attachments.
  4. WordPress admin AJAX requests are not blocked by a security plugin or proxy.

Quality preview samples up to five eligible unoptimized JPEG, PNG, or BMP attachments and writes no generated files.

A Batch Stops#

If you clicked Stop, use the continue action shown in GetWebP. The plugin rescans the same run target before continuing.

If the browser tab closed or crashed:

  1. Reopen GetWebP.
  2. Scan again.
  3. Start a smaller batch if the images are very large.

The free plugin processes in the administrator's browser, so the tab must stay open while a batch runs.

Generated WebP Is Not Showing on the Frontend#

Check:

  1. The attachment shows optimized status in the Media Library.
  2. The public page uses normal WordPress attachment image markup.
  3. Page cache and CDN cache have been purged.
  4. The generated .webp file exists in uploads.

The free plugin uses standard WordPress WebP delivery. It does not write .htaccess or Nginx rewrite rules and does not automatically serve AVIF on the frontend.

Some Images Fail#

Common causes:

  • the original file is missing from uploads
  • the image is too large for the browser to decode reliably
  • the file is corrupt or unsupported
  • a security plugin blocks admin file requests
  • the uploads directory cannot be written

Retry the failed image, or optimize a smaller selection.

CDN or Offload Issues#

Generated files are written to local uploads first. If you use a CDN or object-storage offload plugin, make sure generated WebP files are synced or cached by that system.

After large runs, purge CDN and page caches.