Title: WebberZone Image Optimizer
Author: Ajay
Published: August 24, 2026
Last modified: August 27, 2026
---
Search plugins
# WebberZone Image Optimizer
By [Ajay](https://profiles.wordpress.org/ajay/)
[Download](https://downloads.wordpress.org/plugin/webberzone-image-optimizer.1.0.2.zip)
* [Details](https://wordpress.org/plugins/webberzone-image-optimizer/#description)
* [Reviews](https://wordpress.org/plugins/webberzone-image-optimizer/#reviews)
* [Installation](https://wordpress.org/plugins/webberzone-image-optimizer/#installation)
* [Development](https://wordpress.org/plugins/webberzone-image-optimizer/#developers)
[Support](https://wordpress.org/support/plugin/webberzone-image-optimizer/)
## Description
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.
#### Your originals are never modified
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. Either way, nothing overwrites, replaces
or re-saves your original file. Deactivating the plugin returns your site to serving
the originals immediately, and no URL ever breaks.
#### Delivery that survives caching
Images are wrapped in a `` 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 `` element has
no such failure mode.
Responsive images are handled properly. Every candidate in an image’s `srcset` is
mapped to its optimized copy, with the width descriptors preserved exactly. If even
one size in the set is missing, the whole image falls back to the original rather
than letting the browser request a file that does not exist.
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
* An optimized copy that comes out no smaller than its source is discarded, per
file
* Metadata stripped from the copies while the colour profile is kept, so colours
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
* Multisite aware: per-site queues, tables created for new sites automatically
* WP-CLI: `wp wzio status`, `convert`, `queue`, `run`, `clean`
* Filters throughout for developers
## Screenshots
[⌊Bulk Optimize screen with live progress⌉⌊Bulk Optimize screen with live progress⌉[
Bulk Optimize screen with live progress
[⌊Per-image savings and actions in the Edit Media screen⌉⌊Per-image savings and
actions in the Edit Media screen⌉[
Per-image savings and actions in the Edit Media screen
## Installation
1. Upload the `webberzone-image-optimizer` folder to `/wp-content/plugins/`.
2. Activate the plugin through the Plugins menu.
3. Visit **Media Image Optimizer** to choose your formats.
4. Visit **Media Bulk Optimize** and press Start.
## FAQ
### Will this touch my original images?
No. Originals are never modified, moved or deleted. Every optimized file is a separate
file written next to the original.
### What happens if I deactivate the plugin?
Your site immediately goes back to serving the original images. The generated files
stay on disk, so reactivating restores the optimization instantly without converting
anything again.
### Do I need to change my server configuration?
No. The `` rewrite needs nothing beyond activating the plugin. Server rules
are only needed for images referenced from CSS, and they are optional.
### Should I enable AVIF?
AVIF produces noticeably smaller files than WebP and is understood by every current
browser, but it takes longer to encode and a small number of older browsers do not
support it. Generating both is the safest choice: each visitor gets the smallest
file their browser can read, and anyone else gets the original. Start with WebP
if your library is very large.
### My server cannot encode WebP or AVIF
The settings screen marks any format your server cannot produce. Ask your host to
enable the Imagick extension, which is the better backend, or GD compiled with WebP
support.
### One of my images is still being served as a JPEG or PNG
There are three common reasons, and the Media library column tells you which one
applies.
**The image is not hosted on your site.** Only files inside your own uploads directory
can be optimized. Posts imported from another site often keep image URLs pointing
back at the original domain, and those are left alone.
**One size in the set could not be made smaller.** An optimized copy that comes
out no smaller than the source is discarded rather than kept, and a responsive image
is all-or-nothing: if any single size in its `srcset` has no optimized copy, the
whole image falls back to the original. This is deliberate — offering the browser
a set with a gap in it would let it request a file that does not exist. It happens
most often on large photographs that were already heavily compressed, where the
full-size version loses to the original even though every smaller size wins.
**Your server cannot produce that format.** Check the settings screen, which marks
any format your server cannot encode.
### Does this work with a CDN or a caching plugin?
Yes. Because the format choice happens in the browser rather than on the server,
every visitor receives identical HTML and the page cache stays correct. If you also
add the optional server rules for CSS backgrounds, keep the `Vary: Accept` header
they include.
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“WebberZone Image Optimizer” is open source software. The following people have
contributed to this plugin.
Contributors
* [ Ajay ](https://profiles.wordpress.org/ajay/)
* [ WebberZone ](https://profiles.wordpress.org/webberzone/)
[Translate “WebberZone Image Optimizer” into your language.](https://translate.wordpress.org/projects/wp-plugins/webberzone-image-optimizer)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/webberzone-image-optimizer/),
check out the [SVN repository](https://plugins.svn.wordpress.org/webberzone-image-optimizer/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/webberzone-image-optimizer/)
by [RSS](https://plugins.trac.wordpress.org/log/webberzone-image-optimizer/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 1.0.2
Release date: 27 August 2026
* Enhancements:
- The Bulk Optimize scan runs in time-bounded passes and resumes where it left
off, so building the queue can no longer time out on a very large media library.
- The library-wide counts on the Bulk Optimize screen are cached, so a bulk
run no longer re-counts the entire media library after every batch.
- The naming detection scan primes its post and meta caches, replacing roughly
two hundred queries with two.
#### 1.0.1
Release date: 26 August 2026
* Features:
- Optimized copies left by another plugin are detected, with a one-click switch
to match their file naming so they start being served.
- An optimized copy that already exists is adopted rather than re-encoded, so
moving from another plugin does not repeat work it has already done.
* Bug fixes:
- An optimized copy that is not small enough is now rejected before it replaces
anything, so a rejected conversion can no longer delete a usable copy from
an earlier run.
- An optimized copy inherited from another plugin is kept only when it is no
older than its source, so a stale copy is never served.
#### 1.0.0
Release date: 25 August 2026
* Initial release.
## Meta
* Version **1.0.2**
* Last updated **5 hours ago**
* Active installations **Fewer than 10**
* WordPress version ** 6.6 or higher **
* Tested up to **7.1**
* PHP version ** 7.4 or higher **
* Tags
* [AVIF](https://wordpress.org/plugins/tags/avif/)[convert](https://wordpress.org/plugins/tags/convert/)
[image optimization](https://wordpress.org/plugins/tags/image-optimization/)[performance](https://wordpress.org/plugins/tags/performance/)
[webp](https://wordpress.org/plugins/tags/webp/)
* [Advanced View](https://wordpress.org/plugins/webberzone-image-optimizer/advanced/)
## Ratings
No reviews have been submitted yet.
[Your review](https://wordpress.org/support/plugin/webberzone-image-optimizer/reviews/#new-post)
[See all reviews](https://wordpress.org/support/plugin/webberzone-image-optimizer/reviews/)
## Contributors
* [ Ajay ](https://profiles.wordpress.org/ajay/)
* [ WebberZone ](https://profiles.wordpress.org/webberzone/)
## Support
Got something to say? Need help?
[View support forum](https://wordpress.org/support/plugin/webberzone-image-optimizer/)
## Donate
Would you like to support the advancement of this plugin?
[ Donate to this plugin ](https://wzn.io/donate-wz)