GetWebP - Local Image Converter Logo
문서

Standard Delivery

Understand the free plugin's standard WordPress WebP delivery path. GetWebP does not write Apache .htaccess or Nginx rewrite rules.

Standard Delivery

The free plugin does not write server rewrite rules. It does not edit .htaccess, does not generate Nginx snippets, and does not serve AVIF through server-level content negotiation.

This page keeps the old /docs/wordpress/server-rewrite URL available, but the current free delivery path is standard WordPress WebP delivery.

Table of Contents#

What Standard Delivery Does#

When generated WebP files exist, GetWebP uses WordPress filters to replace eligible attachment image URLs with the generated WebP sibling.

The free plugin covers common WordPress image paths:

  • attachment image attributes
  • calculated srcset values
  • content images with wp-image-* classes
  • featured image HTML

Original files remain in place for fallback and for any image path GetWebP does not rewrite.

What It Does Not Do#

Standard delivery does not:

  • write .htaccess rules
  • create Nginx rewrite rules
  • rewrite external CSS files
  • guarantee replacement for images that are not WordPress Media Library attachments
  • automatically serve AVIF on the frontend

GetWebP can create AVIF files for compatible workflows, but free frontend delivery serves generated WebP files.

Where It Works#

Standard delivery works best with images inserted through the WordPress Media Library, featured images, and normal wp_get_attachment_image() output.

If a page builder, theme, CDN, or offload plugin bypasses WordPress attachment markup, delivery depends on whether the final HTML still contains attachment IDs or generated WebP URLs.

Verify Delivery#

  1. Run a manual optimization batch.
  2. Open a public page with optimized images.
  3. Open browser DevTools and filter the Network tab by images.
  4. Look for generated .webp image URLs.

If you still see original JPEG or PNG URLs, clear page caches and confirm those attachments show optimized status in the Media Library.

Caching and CDNs#

After a large run, purge:

  • WordPress page cache
  • optimization/minification plugin cache
  • CDN cache
  • object-storage/offload sync if your site uses one

Generated files are written to local uploads first. CDN or object-storage delivery depends on your offload plugin's sync behavior.