Dokumentacja

Troubleshooting

Diagnose common free GetWebP WordPress issues with browser-side optimization, credits, 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. Account connection — confirm the site is connected to a GetWebP account.
  2. Credits — confirm the GetWebP dashboard shows remaining credits.
  3. Browser support — use a current desktop Chrome, Edge, Firefox, or Safari.
  4. Secure admin page — load WordPress admin over HTTPS when possible.
  5. Uploads writable — confirm WordPress can write to wp-content/uploads.
  6. Same-site requests — security plugins should not block admin AJAX requests.
  7. Service status — security plugins or proxies should not block requests to https://api.getwebp.com/.

Account Connection Fails#

Check:

  1. Pop-ups or strict browser privacy settings are not blocking the sign-in return flow.
  2. WordPress admin AJAX requests are allowed by security plugins, WAF rules, and proxies.
  3. The WordPress admin page can reach https://api.getwebp.com/.
  4. The site URL in WordPress matches the site you are authorizing.
  5. The manual token flow works if automatic browser return is blocked.

After changing firewall or security settings, refresh the GetWebP dashboard and try connecting again.


Scan or Preview Is Disabled#

Scan and preview actions are disabled until the site is connected and service status allows optimization to continue.

Check:

  1. The dashboard shows a connected GetWebP account.
  2. Credits remain for the current monthly period.
  3. The service status refresh succeeds.
  4. The Media Library has eligible images.

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.


Credits Are Exhausted#

The free account includes 100 monthly optimization credits and up to 20 images per browser batch.

When credits are exhausted, saved generated files are kept and originals are untouched. Wait for the next monthly reset or use Pro to remove the monthly and batch limits.


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.