Title: IndexLane Safe WebP & AVIF Queue
Author: IndexLane
Published: September 2, 2026
Last modified: October 12, 2026
---
Search plugins
# IndexLane Safe WebP & AVIF Queue
By [IndexLane](https://profiles.wordpress.org/wpfixpath/)
[Download](https://downloads.wordpress.org/plugin/indexlane-safe-webp-queue.1.2.1.zip)
* [Details](https://kea.wordpress.org/plugins/indexlane-safe-webp-queue/#description)
* [Reviews](https://kea.wordpress.org/plugins/indexlane-safe-webp-queue/#reviews)
* [Installation](https://kea.wordpress.org/plugins/indexlane-safe-webp-queue/#installation)
* [Development](https://kea.wordpress.org/plugins/indexlane-safe-webp-queue/#developers)
[Support](https://wordpress.org/support/plugin/indexlane-safe-webp-queue/)
## Description
**AVIF and WebP in one free plugin. Smaller image downloads, no credits, no API
key, and your originals stay safe.**
Turn your Media Library’s JPEGs, PNGs, thumbnails, and other WordPress image sizes
into WebP or **AVIF** copies. AVIF can produce smaller files than WebP; results
depend on your images and quality settings. Check the actual savings, then choose
when your site starts serving them to visitors.
Safe WebP & AVIF Queue works with your hosting’s image tools, a bundled browser
encoder, or an optional built-in PHP encoder. Even if your host can display WebP
or AVIF but cannot create them, you still have a way to convert. Your original JPEGs
and PNGs stay where they are.
No subscription, conversion credits, API key, or external conversion service. Everything
needed for conversion is included in the plugin.
* **Keep control:** scan first, convert a few images, and review the results before
serving the generated copies.
* **Work at your pace:** use resumable background jobs or selected browser conversions.
* **See what you saved:** inspect file sizes and savings, search the report, or
export it as CSV.
* **Keep your originals:** remove this plugin’s generated copies whenever you need
to.
* **Go smaller:** choose AVIF in the browser converter and compare the results,
with WebP or the original image as the fallback.
The plugin supports **PHP 7.4 and newer**. The optional picowebp backend is detected
automatically and stays unavailable on PHP 7.4 or 8.0; the rest of the plugin continues
to work.
#### Convert in your browser
Enable **Convert images in the browser**, scan your Media Library, select a few
images, and click **Convert Selected in Browser**.
The bundled encoder uses WebAssembly to run on your computer. There’s no desktop
app or browser extension to install. Keep the plugin page open while it processes
each file, including existing thumbnails and other WordPress sizes. You’ll see progress
and a result for each one.
You can stop a run and return later. Completed copies stay saved; a new scan shows
what remains.
Choose **WebP** or **AVIF** under **Browser conversion format**. AVIF can produce
smaller files than WebP, and the browser encoder is included either way. Set **AVIF
quality** to taste; 60 is a good starting point. AVIF encoding is slower than WebP,
so allow more time for large images.
The panel checks browser support before enabling conversion. You need HTTPS and
enough memory on your computer. Browser conversion works with images served from
the same origin as your admin; the FAQ explains file limits and restrictions for
separately hosted media.
#### Or let your hosting work in the background
When WordPress has GD or Imagick with WebP support, use **Convert Selected** or **
Convert Entire Library**. Jobs run in small batches, save progress, and let you
pause, resume, cancel pending work, or retry failures.
You can close the browser during a server job. Background progress uses WP-Cron,
so it depends on site visits or a configured cron runner. Automatic conversion for
future uploads is also available on supported hosts.
Browser conversion remains available if you prefer it. Whole-library background
jobs and automatic uploads also work with the optional PHP encoder when it is available
and enabled.
#### Or convert with no image tools at all
If your hosting’s image tools cannot write WebP and you want background conversion,
turn on **Convert images with the built-in PHP encoder**. The bundled picowebp encoder
runs on the server without GD, Imagick, or a separate encoder command.
This optional method needs **PHP 8.1 or newer and zlib**. The plugin checks these
requirements automatically and disables its setting on incompatible hosts, including
PHP 7.4 and 8.0. It stays off until you enable it on a compatible host, and GD or
Imagick remain the preferred method when they can write WebP.
PHP encoding is much slower than the other methods. It is limited to **2 million
pixels per source file** by default, and the queue processes one attachment per
request, including its eligible generated sizes. Your maximum pixel setting can
lower that limit. Use browser conversion for larger images or files the bundled
readers cannot decode, such as progressive JPEGs on hosts without GD.
#### Review the results
See original and generated sizes, savings, the conversion method, and reasons for
skipped or failed files. Search and filter the report, or export matching rows as
CSV. WebP quality for JPEG and PNG sources can be adjusted separately; AVIF has
its own quality setting.
By default, a new WebP or AVIF copy is skipped if it’s the same size or larger than
its source. Files created by other tools are left alone: an existing output file
the plugin doesn’t own is reported as a conflict.
The Media Library shows status and savings too. You can exclude images from conversion
and serving, or use **Delete Generated Images** to remove this plugin’s copies while
keeping your originals.
#### Choose when visitors receive WebP and AVIF
**Use generated WebP and AVIF in WordPress image output** starts off. Review your
conversions, then enable it to use matching copies in normal WordPress image output.
Images without a matching copy keep their existing format.
WebP is served by swapping the image URL, because every current browser reads WebP.
AVIF is newer, so it is served through a `` element with WebP or your original
image as the fallback: supported browsers download the smaller AVIF file, while
browsers without AVIF support use the fallback. AVIF is offered when every responsive
candidate has a matching copy, preserving the original crops and sizes.
The plugin doesn’t rewrite saved posts, attachment URLs, CSS backgrounds, page builder
fields, theme files, or hardcoded image markup. It converts JPEG and PNG attachments
and their generated sizes.
Smaller copies reduce image downloads when your site serves them. Keeping both formats
takes more disk space.
#### Example savings from four real images
These version 1.0.0 measurements use JPEG and PNG quality 80. Browser conversion,
GD, and Imagick ran locally on the same Apple M1 Pro Mac with 32 GB RAM. They do
not measure the optional PHP encoder.
The large JPEG and PNG contain the same 3000 x 1348 photo. The small JPEG is a 600
x 270 version of it; the small PNG is a 600 x 400 transparent graphic.
**File sizes in KB, with the percentage saved in brackets.** The server column covers
GD and Imagick, which produced the same sizes in this test.
```
Image Original Browser WebP Server WebP
---------- -------- ------------- -------------
Large JPEG 1077.5 566.4 (47.4%) 566.4 (47.4%)
Small JPEG 51.4 28.0 (45.5%) 28.0 (45.5%)
Large PNG 6105.9 544.7 (91.1%) 544.7 (91.1%)
Small PNG 2.6 2.3 (11.6%) 2.3 (11.8%)
```
**Time to convert and save one file:**
```
Image Browser GD Imagick
---------- -------- -------- --------
Large JPEG 0.63 s 0.36 s 0.37 s
Small JPEG 0.10 s 0.04 s 0.04 s
Large PNG 0.74 s 0.41 s 0.41 s
Small PNG 0.09 s 0.04 s 0.04 s
```
The JPEG examples shrank by about 45-47%; the large PNG by 91%. The already-small
transparent graphic saved about 12%. Your images and quality settings will give
different results.
GD and Imagick were faster in this local test. The useful part of browser conversion
is being able to do the job when your host can’t.
**Test details:** macOS 26.6.2, WordPress 7.1.1, PHP 8.4.23 and Chrome 153.0.8010.52.
Each time is the median of five fresh conversions after one warm-up. Times include
conversion, validation, saving and local requests; they exclude queue waiting and
the first encoder download. Your hosting, computer and connection affect the time,
including the browser’s image download and WebP upload. KB means 1,000 bytes. Full-
size files were measured individually; generated sizes add more work.
Photo: [Fronalpstock by Hannes Röst](https://commons.wikimedia.org/wiki/File:Fronalpstock_big.jpg),
[CC BY-SA 3.0](https://creativecommons.org/licenses/by-sa/3.0/), resized for these
tests.
#### Start with a few images
Open **Tools -> IndexLane Safe WebP & AVIF Queue**, scan your library, and try a
few images. Check the results before enabling frontend serving or converting more.
Command-line users can also manage server jobs and reports through WP-CLI; see the
FAQ.
[Plugin details and documentation](https://indexlane.dev/plugins/safe-webp-queue).
## Screenshots
[⌊Check your hosting's WebP support, choose whether to convert on the server or
in your browser, and pick WebP or AVIF as the browser output format.⌉⌊Check your
hosting's WebP support, choose whether to convert on the server or in your browser,
and pick WebP or AVIF as the browser output format.⌉[
Check your hosting’s WebP support, choose whether to convert on the server or in
your browser, and pick WebP or AVIF as the browser output format.
[⌊Scan your Media Library, select images, and see which files need conversion or
have a conflict.⌉⌊Scan your Media Library, select images, and see which files need
conversion or have a conflict.⌉[
Scan your Media Library, select images, and see which files need conversion or have
a conflict.
[⌊Convert selected images and their generated sizes in the browser to WebP or AVIF,
with progress and a result for each file.⌉⌊Convert selected images and their generated
sizes in the browser to WebP or AVIF, with progress and a result for each file.⌉[
Convert selected images and their generated sizes in the browser to WebP or AVIF,
with progress and a result for each file.
[⌊Review completed conversions, the method used, file sizes, and savings.⌉⌊Review
completed conversions, the method used, file sizes, and savings.⌉[
Review completed conversions, the method used, file sizes, and savings.
[⌊Manage WebP status and exclusions from the Media Library list.⌉⌊Manage WebP status
and exclusions from the Media Library list.⌉[
Manage WebP status and exclusions from the Media Library list.
[⌊See the completed browser run, including the files saved and any copies skipped
because they were not smaller.⌉⌊See the completed browser run, including the files
saved and any copies skipped because they were not smaller.⌉[
See the completed browser run, including the files saved and any copies skipped
because they were not smaller.
## Installation
1. Install and activate IndexLane Safe WebP & AVIF Queue from Plugins in WordPress,
or upload the plugin folder to /wp-content/plugins/.
2. Open **Tools -> IndexLane Safe WebP & AVIF Queue** and check the server support
panel. Use your host’s WebP image tools, enable **Convert images in the browser**,
or enable the optional **built-in PHP encoder** when its requirements are met.
3. Click **Scan Media Library** and select a few eligible images.
4. Choose **Convert Selected** for server conversion, or **Convert Selected in Browser**
for browser conversion. Keep the page open during a browser run.
5. Review the file sizes, savings, and any skip reasons. Enable **Use generated WebP
and AVIF in WordPress image output** in Settings when you’re ready to use matching
copies on your site.
## FAQ
### Does version 1.2.1 still work on PHP 7.4?
Yes. The plugin still requires only PHP 7.4. picowebp is an optional conversion
backend, not a requirement for using the plugin. On PHP 7.4 or 8.0 its library is
not loaded and its setting is disabled automatically. Server conversion through
compatible GD or Imagick, browser conversion, reports, and the other plugin features
remain available.
### Can I try WebP and AVIF without losing my original images?
Yes. The plugin saves WebP and AVIF copies beside your JPEGs and PNGs, including
generated attachment sizes. Your originals remain available. You can use **Delete
Generated Images** to remove copies owned by this plugin; files created by other
tools are left alone.
### Will my site use generated copies as soon as I convert an image?
You choose when. Frontend serving starts off. Enable it in Settings to use matching
WebP and AVIF copies where your theme or plugin requests images through normal WordPress
image output. Images with no matching copy continue to use their existing format.
Saved post content, attachment URLs, CSS backgrounds, and hardcoded image markup
are not rewritten.
### Will every image be smaller?
Results vary by image and quality setting. The report shows actual file sizes and
savings so you can judge the result. By default, the plugin skips newly converted
files that are larger than their source. Keeping both formats uses additional disk
space; this plugin does not free space by deleting originals.
### Do I need an account, API key, or cloud service?
No. Conversion runs on your hosting or on your computer, depending on the method
you choose. Browser conversion exchanges images only with your own WordPress site.
The plugin does not use an external optimization API, account, or credit system.
### What if my server cannot create WebP files?
Turn on **Convert images in the browser** in Queue Settings. The image encoder that
ships with the plugin then runs inside your own browser, so the image data never
goes to another server and nothing has to be installed on your computer or your
host. Your browser sends the finished WebP or AVIF file back to your WordPress site,
where it is stored beside the original exactly like a server conversion.
This mode is attended work: keep the plugin page open while it runs.
If you would rather not keep a tab open, and your site runs PHP 8.1 or newer with
zlib, turn on **Convert images with the built-in PHP encoder** instead. The normal
background queue, whole-library jobs, automatic uploads, and WP-CLI can use it without
a WebP-capable image editor. It is much slower than GD or Imagick and is limited
to smaller images. The plugin detects compatibility automatically; this optional
setting stays disabled on PHP 7.4 or 8.0.
### Do I need anything installed for browser conversion?
No desktop software or browser extension is needed. The WebAssembly encoder comes
with the plugin and runs in a supported browser on macOS, Windows, or Linux. It
doesn’t use image tools installed on your computer.
Use a current Chrome, Edge, Firefox, or Safari browser. The admin page must use
HTTPS (localhost also works for development), and the site must allow the bundled
scripts, module workers, and WebAssembly encoder to load. The panel tests these
capabilities on your site before enabling conversion. Older browsers can lack a
required feature even if they can display WebP images.
### Does the plugin use cwebp on my hosting?
Server conversion normally uses the WordPress image editor through GD or Imagick
with WebP support. The plugin does not call the standalone `cwebp` command. If your
image editor cannot write WebP, use the optional built-in PHP encoder (PHP 8.1 or
newer with zlib) or browser conversion. Both encoders ship with the plugin.
### Are there limits to browser conversion?
Each source file must be at most 20 MiB, at most 8,192 pixels along either edge,
and at most 16 million pixels in total. Your configured maximum pixel limit also
applies. The browser processes one file at a time, and very large images may still
exceed your device’s memory or the conversion time limit.
Source images and the conversion endpoints must be available on the same origin
as your WordPress admin (the same protocol, host, and port). Offloaded images, CDN-
only uploads, or a separate media domain are not supported by browser conversion.
Your hosting must also accept the finished file upload; its upload-size limits still
apply. Animated PNGs are not supported by the browser encoder.
### Should I convert to AVIF or WebP?
It’s your choice, and you can convert the same library again later if you change
your mind.
AVIF is the newer format and is usually smaller than WebP, depending on the image
and quality settings for the same picture, so it is worth choosing when your visitors
use current browsers. WebP is the safer default: every current browser reads it,
it encodes much faster, and it is what the server background jobs produce when your
hosting can create WebP.
AVIF is produced by the browser converter in this version, so it is attended work:
keep the plugin page open while it runs. Its files are served through a picture
element with WebP or your original image as the fallback, so browsers without AVIF
support use the fallback. Some very small or already-optimized images can come out
larger as AVIF; those are skipped by default, just like oversized WebP files.
### Does browser conversion put less load on my server?
It moves the image encoding to your computer. That can help when PHP cannot spare
enough memory for an image, provided the file fits the browser’s limits. Your server
still serves the source file, receives and validates the generated upload, saves
it, and updates the conversion records. Browser conversion reduces the encoding
work on your hosting; it doesn’t remove all server work.
### Is browser conversion a replacement for the queue?
Use the server queue for background work when your hosting has a WebP-capable image
editor or the optional PHP encoder is enabled. Browser conversion handles selected
images on your computer and can help with files that exceed the server’s memory
estimate or PHP encoder limits. The browser run needs the plugin page to stay open.
### What about photos with rotation data?
WordPress normally creates an upright version when it processes a photo with EXIF
rotation data. Those images convert normally. Older uploads or images that WordPress
could not rotate may still depend on a rotation or mirror tag. Browser conversion
and the optional PHP encoder refuse those files before encoding, including mirrors
that leave the dimensions unchanged. Save an upright copy without that tag and upload
it again.
### Can I close the page while a conversion runs?
For **server conversion**, yes. Conversion progress is saved, and WP-Cron can continue
the queue when your site receives traffic. If traffic is low or WP-Cron is disabled,
work may wait until you reopen the plugin page or your configured cron runner runs.
You can pause, resume, cancel pending work, or retry failures from the queue controls.
If a whole-library job has more than 10,000 failures, retry rescans the library
and reuses valid existing WebP files. For **browser conversion**, keep the tab open:
closing it stops the remaining work, while files already saved stay in place.
### How do I convert my whole Media Library?
Choose **Convert Entire Library** when your host has a WebP-capable image editor
or the optional PHP encoder is enabled. The plugin processes images in small batches
and saves progress. WP-Cron can continue the job between visits, depending on site
traffic or your cron runner. Files beyond the PHP encoder’s limits need another
conversion method. If neither server method is available, use selected browser conversions
and keep the page open.
### Can I keep an image out of WebP conversion?
Yes. Use **Exclude from WebP** in the Media Library row actions, or the exclude
bulk action for several images at once. Excluded images are skipped by every conversion
job, are not regenerated when you change quality settings, and are not served as
WebP. Existing copies generated earlier stay on disk until you delete them, and
you can include an image again at any time.
### Where do the savings numbers come from?
The plugin records the original and WebP byte size of every file it generates, so
the totals on the plugin page reflect real files rather than estimates. Totals are
adjusted when files are regenerated or deleted. If you converted images with an
earlier version, press **Recalculate** once to rebuild the totals from the metadata
stored on your attachments.
### Can I use WP-CLI?
Yes. `wp ilswq status` reports server support, settings, queue state, and stored
savings; `wp ilswq scan` lists images with their status; `wp ilswq convert` converts
specific IDs, a dry run, or the whole library with `--all`; `wp ilswq totals` shows
or rebuilds the savings; `wp ilswq queue` inspects or controls the queue; and `wp
ilswq cleanup` removes generated WebP and AVIF files.
### Can new uploads be converted automatically?
Yes, if your server has a WebP-capable image editor or the optional PHP encoder
is enabled, and you turn on automatic new-upload conversion in Settings. It starts
off. New uploads are queued after WordPress finishes creating their image sizes.
Background conversion follows the same limits and settings as manual server jobs.
### How do I find or export a particular image?
Run a scan, then search the report by filename, attachment title, or ID. Search
works together with the status filters. **Export CSV** downloads only matching rows,
and **Convert Selected** queues only selected eligible images in that view. Clear
the search and choose **All** to see the full report again.
### Why was an image skipped or marked as a conflict?
Check the Reason column for that attachment. A file may be missing, unsupported,
above your pixel limit, or likely to need more memory than your server can spare.
A small file on disk can still require substantial memory when decoded. A conflict
means a WebP already exists that this plugin does not own, so it is left unchanged.
### What happens if I edit an image or regenerate thumbnails?
The plugin detects source-file and quality-setting changes before regenerating its
WebP output. It also reconciles its copies when attachment sizes change and cleans
them up when an attachment is deleted. Run a fresh scan to review which images need
conversion after making changes.
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“IndexLane Safe WebP & AVIF Queue” is open source software. The following people
have contributed to this plugin.
Contributors
* [ IndexLane ](https://profiles.wordpress.org/wpfixpath/)
[Translate “IndexLane Safe WebP & AVIF Queue” into your language.](https://translate.wordpress.org/projects/wp-plugins/indexlane-safe-webp-queue)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/indexlane-safe-webp-queue/),
check out the [SVN repository](https://plugins.svn.wordpress.org/indexlane-safe-webp-queue/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/indexlane-safe-webp-queue/)
by [RSS](https://plugins.trac.wordpress.org/log/indexlane-safe-webp-queue/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 1.2.1
* Preserve ownership when generated files are stale, missing, or damaged, so quality
changes and repairs can regenerate them.
* Allow WebP and AVIF conversions independently, including adding WebP through
the server queue after AVIF conversion.
* Preserve current AVIF copies during attachment metadata updates and clean obsolete
sizes in both formats.
* Match AVIF responsive candidates to exact source files, preserve crops, and retain
the existing image fallback when AVIF coverage is incomplete.
* Validate stored AVIF containers and compatible brands, including truncated files,
animation brands, and malformed box boundaries.
* Include both formats in report sizes, encoder labels, validation counts, and
cleanup wording. Clarify that AVIF uses the browser and server jobs produce WebP.
* Correct the browser encoder’s AVIF lossless quality and chroma options.
#### 1.2.0
* Added in-browser AVIF conversion. The bundled WebAssembly worker now encodes
AVIF as well as WebP, and **Browser conversion format** in Queue Settings chooses
which one a run produces. AVIF copies are typically 20-50% smaller than the equivalent
WebP.
* Added an **AVIF quality** setting (default 60, libavif’s scale) beside the existing
JPEG and PNG quality controls.
* Stored AVIF files beside WebP files instead of on top of them, so a library can
hold both and the served copy is chosen per browser. Report rows and totals cover
either format.
* Served AVIF through a `` element with WebP and the original image as
fallbacks, so an AVIF copy never reaches a browser that cannot read it. URL swaps
keep serving WebP.
* Validated AVIF output on the server with a bounded ISO-BMFF box walk that refuses
animated sequences, non-AVIF HEIF brands, and malformed boxes before anything
is written.
* Kept AVIF in the browser backend. GD and Imagick cannot be relied on to encode
AVIF on shared hosting, so the server queue, automatic uploads and WP-CLI continue
to produce WebP.
* Added the browser AVIF encoder to the release package with its libavif and libaom
licence notices.
#### 1.1.1
* Resolved Plugin Check filesystem errors in the pure-PHP encoder’s JPEG metadata
reader, preserving bounded reads and EXIF rotation and mirror protection.
* Updated release metadata and package verification for 1.1.1.
#### 1.1.0
* Added a third conversion backend: a pure-PHP WebP encoder. On PHP 8.1+ hosts
with no WebP-writing image editor, the built-in queue, whole-library jobs, automatic
uploads and WP-CLI can now create WebP files without GD, Imagick, `cwebp`, or
a browser. It is off by default, capped by megapixels, and much slower than the
other backends.
* Bundled the picowebp encoder and added a server check, a settings toggle, and
a report label for the new backend.
* Kept browser conversion as the fallback for files the pure-PHP encoder cannot
read or that exceed its size cap.
* Kept PHP 7.4 support: picowebp is optional, is never loaded on PHP 7.4 or 8.0,
and is disabled automatically when its PHP or zlib requirements are not met.
* Refreshed conversion controls after changing the PHP setting and limited automatic
PHP conversion to one attachment per request.
* Checked actual source dimensions before PHP decoding, protected EXIF-oriented
JPEGs, and retained useful fallback reasons and accurate conversion-method labels.
#### 1.0.1
* Detected ImageMagick builds that ignore WebP quality and used GD or browser conversion
instead, with a clearer server capability check.
* Corrected the WordPress.org “Tested up to” header to 7.1; compatibility testing
still uses WordPress 7.1.1.
* Explicitly sanitized Media Library row-action IDs before normalizing them, resolving
the Plugin Check input warning.
* Updated release metadata and packaging checks for 1.0.1.
#### 1.0.0
* Added browser (WebAssembly) conversion: a copy of the WebP encoder ships with
the plugin and can create WebP files on your own computer, so images can still
be converted on hosts whose image tools cannot write WebP.
* Added a browser conversion panel with a capability report, per-file progress,
a running result log, a stop control, and the same report, savings, and serving
updates as server conversion.
* Added a “Convert images in the browser” setting, off by default, and a report
reason that names the files only the browser can convert.
* Wrote every browser conversion through the same install, ownership, conflict,
totals, and generated-map path as the local image editor backends.
* Kept the server queue from accepting work it cannot perform on a host without
a WebP writer, and skipped browser-only files instead of reporting them as failures.
* Added an integration test for the browser backend that covers routing, the REST
handshake, container validation, trust boundaries, stored metadata, and frontend
serving.
* Fixed server conversion ignoring the selected quality when WordPress changes
the output format to WebP.
* Fixed stale browser results after quality changes, damaged outputs, or a replaced
attachment source; browser saves recheck the current source and settings.
* Serialized cleanup, totals recalculation, and browser saves with the server queue,
kept conflicting controls disabled during a browser run, and allowed conversion
after a server job is paused.
* Added a real worker/codec capability probe, useful server error messages, bounded
uploads, and EXIF rotation/mirror rejection before decoding.
* Corrected encoder labels and savings for partially converted attachments, and
applied memory limits to regeneration too.
* Stopped automatic uploads from retrying browser-only images.
* Verified WordPress 7.1.1 with GD, Imagick, WP-CLI, and the browser backend regressions;
updated the CI matrix.
* Added measured size and speed comparisons for large/small JPEG and PNG files
using Chrome, GD, and Imagick at quality 80.
* Rewrote the description for shared-hosting users and refreshed six screenshots,
including a live WebAssembly conversion.
* Tested browser WebAssembly conversion in Google Chrome 153.0.8010.52 on WordPress
7.1.1 and real Safari 26.6.2 on WordPress 7.1 (macOS), covering JPEGs, transparent
PNGs, generated sizes, saved results, and larger-output skips.
#### 0.3.0
* Added whole-library background conversion with bounded batches, stable attachment
cursors, and existing queue controls.
* Added Media Library WebP status, savings, conversion actions, and per-image exclusions
for conversion and serving.
* Added stored savings totals and a bounded rebuild for images converted by earlier
versions.
* Added WP-CLI commands for status, scanning, conversion, queue controls, savings,
and cleanup.
* Kept exclusions effective after queuing and corrected savings accounting for
partial cleanup and orphan retries.
* Validated real WP-CLI formatting, automatic queue draining, and cleanup conflict
checks.
#### 0.2.1
* Added report search by filename, attachment title, and ID with matching result
counts.
* Made CSV exports and conversion selection respect the active search and status
filter.
* Added a clear-search control, a no-results message, and accessible status-filter
states.
#### 0.2.0
* Added persistent, resumable conversion jobs with progress, pause, resume, cancel,
and failed-item retry controls.
* Added bounded queue workers with duplicate-worker locking and WP-Cron continuation.
* Moved automatic new-upload conversion out of the upload request and into retryable
background work.
* Added generation fingerprints to detect source-file and quality-setting changes
before safe regeneration.
* Reconciled plugin-owned WebP files when attachment sizes change or attachments
are deleted.
* Retained failed attachment cleanup for safe background retries.
#### 0.1.5
* Renamed the plugin to IndexLane Safe WebP Queue and aligned WordPress.org release
metadata.
* Protected unrelated sibling WebP files as conflicts instead of replacing or deleting
them.
* Generated and validated WebP output in a temporary file before installing it
at the final path.
* Made statuses, browser request errors, CSV headers, selection labels, and result
summaries translation-ready.
* Added a root GPL license, dated project changelog, repeatable release packaging,
and exact-package checks.
* Declared testing through WordPress 7.1 with GD and Imagick coverage.
#### 0.1.4
* Fixed cleanup pagination restarting when a page contains no generated files.
* Preserved generated-file ownership metadata when physical deletion fails so cleanup
can be retried safely.
* Neutralized formula-like values in CSV exports to prevent spreadsheet formula
injection.
* Validated every stored WebP file across the current report instead of stopping
after the first valid file.
* Cached frontend generated-file inspection once per attachment and request.
* Added regression coverage for admin cleanup, CSV export, complete validation,
and failed cleanup retries.
#### 0.1.3
* Renamed the generated-file check from Delivery Check to Validate WebP.
* Added Mac/archive ZIP ignores to the repository.
* Refreshed screenshots with safety defaults visible and the Reason column readable.
* Widened the screenshot capture viewport for public plugin assets.
#### 0.1.2
* Added generated attachment size conversion.
* Added stored WebP file map per attachment.
* Added optional frontend serving for normal WordPress image output.
* Added optional WebP generation for new uploads.
* Added pause, stop, resume, result filters, and WebP validation controls.
* Added generated WebP output validation.
* Added stale and invalid existing WebP detection.
* Stored new WebP maps with uploads-relative paths.
* Hardened uploads-directory validation before scan and conversion.
* Hardened cleanup path validation.
* Hardened AJAX settings and ID handling.
* Added clean Plugin Check CI build handling and ignored IDE/build artifacts.
* Removed full server paths from admin AJAX rows.
* Lowered the max pixel setting ceiling.
#### 0.1.0
* Initial release.
* Added server capability checks.
* Added Media Library dry-run scan.
* Added small-batch selected conversion.
* Added sibling WebP output with originals preserved.
* Added skip reasons and CSV export.
* Added explicit cleanup for generated WebP files.
## Meta
* Version **1.2.1**
* Last updated **2 days ago**
* Active installations **Fewer than 10**
* WordPress version ** 6.0 or higher **
* Tested up to **7.1.3**
* PHP version ** 7.4 or higher **
* Language
* [English (US)](https://wordpress.org/plugins/indexlane-safe-webp-queue/)
* Tags
* [AVIF](https://kea.wordpress.org/plugins/tags/avif/)[image optimization](https://kea.wordpress.org/plugins/tags/image-optimization/)
[media library](https://kea.wordpress.org/plugins/tags/media-library/)[performance](https://kea.wordpress.org/plugins/tags/performance/)
[webp](https://kea.wordpress.org/plugins/tags/webp/)
* [Advanced View](https://kea.wordpress.org/plugins/indexlane-safe-webp-queue/advanced/)
## Ratings
No reviews have been submitted yet.
[Your review](https://wordpress.org/support/plugin/indexlane-safe-webp-queue/reviews/#new-post)
[See all reviews](https://wordpress.org/support/plugin/indexlane-safe-webp-queue/reviews/)
## Contributors
* [ IndexLane ](https://profiles.wordpress.org/wpfixpath/)
## Support
Got something to say? Need help?
[View support forum](https://wordpress.org/support/plugin/indexlane-safe-webp-queue/)