WebberZone Image Optimizer

WebberZone Image Optimizer converts the images already in your media library to WebP and AVIF, and serves each visitor the smallest file their browser can read. Images are typically 40–60% smaller with no visible difference. Everything happens on your own server. Your images are never uploaded anywhere. The plugin makes no outbound network requests of any kind — there is no external service, no API key, no monthly image quota, no account to create and nothing that can stop working because a company shut down or changed its pricing. What your server needs Almost certainly nothing you do not already have. WordPress cannot crop or resize an uploaded image without either the Imagick or the GD extension, so every working WordPress install already has one of them, and both have been able to write WebP for years.

• WebP works on virtually any current host. GD has supported it since PHP 5.5, Imagick since well before that.
• AVIF is newer and less universal. It needs either PHP 8.1+ with GD built against libavif, or Imagick with an AVIF delegate. Plenty of hosts have it; plenty do not yet.

You do not have to guess. The plugin tests your server by actually encoding a small image with each backend at activation, rather than trusting what the extension claims to support, and the settings screen shows you exactly which formats came back working. If AVIF is unavailable the option is simply marked as such and WebP carries on normally. Optional original compression with backups By default, each optimized copy is written alongside the original with the new extension appended, so photo.jpg gains photo.jpg.webp. The File naming setting can switch this to replacing the extension instead (photo.webp) — see the settings screen for the trade-off before turning it on. Sidecar generation leaves the source unchanged. Optional original compression recompresses served JPEG/PNG files with mandatory backups; optional resizing uses the maximum dimension. Use Restore originals to reverse these changes. Deactivation stops optimized delivery but does not restore compressed originals. Delivery that survives caching Images are wrapped in a <picture> element, so the browser chooses the format. That matters more than it sounds: the common alternative is to vary the response on the Accept header, which returns different bytes for a single URL. Any cache in front of that — a page cache plugin, a CDN — which ignores Vary will happily hand a WebP file to a browser that cannot display it. A <picture> element has no such failure mode. Responsive images are handled properly. Each format's <source> lists only the optimized srcset candidates that exist, with their descriptors preserved exactly. Missing intermediate copies are omitted, while a missing smallest, widest or highest-density copy withholds that format so the optimized set always covers the same range as the original set. The original <img> remains as the fallback. For images referenced from a stylesheet, where the browser is never offered a choice, the Delivery tab generates ready-to-paste Apache and nginx rules, complete with the Vary: Accept header those rules require. Bulk conversion that finishes The bulk screen works through a database-backed queue one batch at a time. Close the tab and nothing is lost; a background worker carries on, and reopening the screen resumes exactly where it stopped. Failures are retried a few times and then listed with the reason. Features

• WebP and AVIF, generated together or separately (AVIF where the server supports it)
• Bulk conversion of an existing media library, resumable and interruptible
• Automatic conversion of new uploads
• Lazy conversion: an image seen on the front end but not yet converted is queued, never encoded during the page render
• Per-format quality, encoder effort, and lossless mode for PNG sources
• A lossy optimized copy that misses the minimum saving is retried once at a lower quality before being discarded, per file
• Metadata stripped from the copies while the color profile is kept, so colors do not shift
• Animated GIFs keep their animation when ImageMagick is available
• Memory guard that skips an image rather than crashing a batch
• Per-image status and actions in the Media library, with a filter for optimized, not-yet-optimized, skipped and failed images
• Bulk Optimize warns when images are queued but the background worker has stopped running, and gives the commands that recover it
• Multisite aware: per-site queues, tables created for new sites automatically
• WP-CLI: wp wzio status, convert, queue, run, clean
• Filters throughout for developers

1.2.0 Release date: 7 October 2026 Release post: https://webberzone.com/announcements/image-optimizer-v1-2/ Added

• Optional original JPEG compression with configurable quality and PNG compression through local oxipng or pngquant tools, with verified backups and wp wzio compress support.
• Restore originals actions in the Media Library and Edit Media screen, bulk restoration and wp wzio restore-originals to recover files and dimensions; backups and restore records are retained on uninstall by default.
• Compression from verified backups when settings change, plus backup integration with WordPress's GD and Imagick image editors to avoid regenerating thumbnails from compressed main files.
• Maximum image dimension and Disable upload scaling settings for new uploads.
• Resize existing originals option and wp wzio compress --resize to shrink served main files with restorable dimensions; existing thumbnail files are retained, with oversized candidates omitted from WordPress-generated srcset.
• Original compression results and resized dimensions in the Media Library, plus original savings, backup usage, resized-image counts and optimized-copy disk usage by format on Bulk Optimize and in wp wzio status.
• Regenerate only images made with older settings option on Bulk Optimize and --outdated on wp wzio convert and wp wzio queue; copies made before settings tracking are left alone.

Fixed

• Bandwidth savings on Bulk Optimize and wp wzio status omitted images converted outside the queue and could be lost when queue records were cleared.
• Image conversion could fail in background or command-line requests when wp_tempnam() was unavailable.
• Optimized copies could remain on disk when an image was deleted during conversion.

Earlier versions For the changelog of earlier versions, please refer to the releases page on GitHub.