Title: IndexLane Safe WebP Queue Author: IndexLane Published: September 2, 2026 Last modified: September 8, 2026 --- Search plugins ![](https://ps.w.org/indexlane-safe-webp-queue/assets/banner-772x250.png?rev=3677308) ![](https://ps.w.org/indexlane-safe-webp-queue/assets/icon-256x256.png?rev=3677308) # IndexLane Safe WebP Queue By [IndexLane](https://profiles.wordpress.org/wpfixpath/) [Download](https://downloads.wordpress.org/plugin/indexlane-safe-webp-queue.0.2.1.zip) * [Details](https://test.wordpress.org/plugins/indexlane-safe-webp-queue/#description) * [Reviews](https://test.wordpress.org/plugins/indexlane-safe-webp-queue/#reviews) * [Installation](https://test.wordpress.org/plugins/indexlane-safe-webp-queue/#installation) * [Development](https://test.wordpress.org/plugins/indexlane-safe-webp-queue/#developers) [Support](https://wordpress.org/support/plugin/indexlane-safe-webp-queue/) ## Description **Lighter images. Your originals kept. You’re in control.** Give your WordPress images a smaller WebP version without giving up the JPEGs and PNGs you already have. IndexLane Safe WebP Queue helps you convert your Media Library, see the file-size savings, and put those WebP copies to work when you’re ready. Everything runs on your own server, right inside WordPress. No cloud account to connect, no API key to manage, and no images sent to an optimization service. #### Make images lighter, at your own pace Start with a scan to see which images your server can convert. Choose a few to try or work through your library in small batches. The plugin covers both your main attachment images and the thumbnail and other sizes WordPress creates. Your conversion job keeps its progress if you close the page. Pause when you need to, resume later, and retry failed conversions from the same screen. Background processing uses WP-Cron, so progress while you’re away depends on site traffic or a configured cron runner. #### Keep the images you trust Your original JPEGs and PNGs stay where they are. WebP copies are saved beside them, and you can remove the copies created by this plugin whenever you choose. Before converting, the plugin checks your server’s WebP support and estimates memory needs. It skips files that exceed your settings or look too demanding for your server, and leaves WebP files created by other tools untouched. By default, it also skips a new WebP if it would be larger than its source. #### See what changed and what needs attention Compare original and WebP file sizes, check savings for each attachment, and see a reason when something is skipped or fails. Search the report by filename, title, or attachment ID, then narrow it by status. Convert the selected images in that view or export the matching results as CSV. It’s a quick way to find one image, review a problem, or share the results of your work. #### Put WebP to work when you’re ready Turn on optional frontend serving to use matching WebP copies in normal WordPress image output. Smaller files can reduce the image data your visitors download; actual savings depend on your images and how your site displays them. You can also enable automatic conversion for future uploads. New images join the queue after WordPress creates their sizes, keeping conversion out of the upload request. Both options start **off**, so you can convert and review your images before changing what visitors receive. #### Start with a few images Open **Tools -> IndexLane Safe WebP Queue**, scan your library, and convert a small selection. Review the results, then enable frontend serving if it fits your site. This plugin works with JPEG and PNG Media Library attachments. It keeps saved content and attachment URLs unchanged. Frontend serving applies where WordPress uses its standard image-output filters; it does not cover saved image HTML, CSS backgrounds, theme files, page builder fields, or hardcoded URLs. GIF, SVG, AVIF, and existing WebP files are outside its conversion scope. [Learn more about IndexLane Safe WebP Queue](https://indexlane.dev/plugins/safe-webp-queue). ## Screenshots [⌊Check that your server is ready and choose the conversion settings that suit your images.⌉⌊Check that your server is ready and choose the conversion settings that suit your images.⌉[ Check that your server is ready and choose the conversion settings that suit your images. [⌊Review your Media Library before converting, with eligible images and existing WebP conflicts clearly identified.⌉⌊Review your Media Library before converting, with eligible images and existing WebP conflicts clearly identified.⌉[ Review your Media Library before converting, with eligible images and existing WebP conflicts clearly identified. [⌊Compare image sizes and savings, and see the reason for each conversion result.⌉⌊ Compare image sizes and savings, and see the reason for each conversion result.⌉[ Compare image sizes and savings, and see the reason for each conversion result. [⌊Choose when to serve WebP to visitors and whether to convert future uploads automatically.⌉⌊ Choose when to serve WebP to visitors and whether to convert future uploads automatically .⌉[ Choose when to serve WebP to visitors and whether to convert future uploads automatically. ## Installation 1. Install and activate IndexLane Safe WebP Queue from Plugins in WordPress, or upload the plugin folder to /wp-content/plugins/. 2. Open **Tools -> IndexLane Safe WebP Queue** and check that your server supports WebP conversion. 3. Select **Scan Media Library**, then choose a few eligible images and click **Convert Selected**. 4. Review the file sizes, savings, and any skip reasons. Enable frontend serving in Settings when you’re ready to use matching WebP copies on your site. ## FAQ ### Can I try WebP without losing my original images? Yes. The plugin saves WebP copies beside your JPEGs and PNGs, including generated attachment sizes. Your originals remain available. You can use **Delete Generated WebPs** to remove copies owned by this plugin; files created by other tools are left alone. ### Will my site use WebP as soon as I convert an image? You choose when. Frontend serving starts off. Enable it in Settings to use matching WebP 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. Your server does the conversion using a compatible WordPress image editor with GD or Imagick WebP support. Your images are not uploaded to an external optimization service. ### Can I close the page while a conversion runs? 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. ### Can new uploads be converted automatically? Yes, if you enable automatic new-upload conversion in Settings. It starts off. Once enabled, new uploads are queued after WordPress finishes creating their image sizes. Conversion runs in the background and follows the same server checks and conversion settings. ### 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 Queue” is open source software. The following people have contributed to this plugin. Contributors * [ IndexLane ](https://profiles.wordpress.org/wpfixpath/) [Translate “IndexLane Safe WebP 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 #### 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 **0.2.1** * Last updated **2 hours ago** * Active installations **Fewer than 10** * WordPress version ** 6.0 or higher ** * Tested up to **7.1** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/indexlane-safe-webp-queue/) * Tags * [image optimization](https://test.wordpress.org/plugins/tags/image-optimization/) [images](https://test.wordpress.org/plugins/tags/images/)[media library](https://test.wordpress.org/plugins/tags/media-library/) [performance](https://test.wordpress.org/plugins/tags/performance/)[webp](https://test.wordpress.org/plugins/tags/webp/) * [Advanced View](https://test.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/)