AttiaWebP helps site owners convert JPEG and PNG media library images into WebP (and optionally AVIF) using the image tools available on their own WordPress server.
The default mode is conservative: it creates WebP copies next to the original files and keeps the original JPEG/PNG files untouched. Optional server-level delivery can serve matching WebP/AVIF sidecar files without rewriting front-end HTML, WooCommerce product markup, widgets, or content.
Advanced replacement tools are included for site owners who want a one-image WebP media library. These tools are disabled by default and require explicit confirmation before deleting original JPEG/PNG files or generated image sizes.
Main features:
.htaccess rules block on Apache/LiteSpeed servers, plus a copy-paste Nginx example.Important: Always create a full backup before using permanent replacement tools. Replacement mode deletes original JPEG/PNG files and generated image sizes after successful WebP conversion.
WP-CLI commands:
wp attiawebp status – Shows support details, pending counts, and background state.wp attiawebp convert [--limit=<n>] [--force] – Creates WebP/AVIF sidecars for pending attachments.wp attiawebp replace --confirm=DELETE-ORIGINALS [--limit=<n>] – Runs the permanent replacement flow.wp attiawebp reset-markers [--which=sidecar|replace] – Clears conversion or skip markers.Filters:
aawo_conversion_quality( int $quality, string $mime, string $file ) – Adjusts quality per file or format.aawo_should_convert_file( bool $convert, string $file, int $attachment_id ) – Skips or allows specific files.aawo_delivery_rules( string $rules, bool $avif_enabled ) – Modifies the managed .htaccess rules block.aawo_batch_time_budget( int $seconds ) – Changes the per-batch time budget for bulk processing.AttiaWebP does not send images, site data, or usage data to external services. All conversion work happens locally on the WordPress server.