內容簡介
IndexLane Safe WebP Queue 外掛可將您的媒體庫中的 JPEG、PNG 及其他圖片格式轉換為 WebP 格式，幫助減少圖片下載大小，提升網站載入速度，並確保原始圖片安全無虞。
【主要功能】
• 將多種圖片格式轉換為 WebP
• 支援瀏覽器內轉換及伺服器背景轉換
• 無需訂閱或外部轉換服務
• 可隨時檢視轉換結果與節省的空間
• 保留原始圖片，隨時可移除生成的副本
外掛標籤
開發者團隊
② 後台搜尋「IndexLane Safe WebP & AVIF Queue」→ 直接安裝（推薦）
原文外掛簡介
Smaller images. Smarter media reviews. You stay in control.
Give your WordPress Media Library two useful upgrades: WebP and AVIF conversion to reduce image downloads, and optional AI Media Review to help you write alternative text and spot images that deserve a closer look.
Keep your original images. See the actual savings. Review AI suggestions before applying them. One plugin brings image conversion and a second pair of eyes into your WordPress admin.
Put AI to work on your Media Library
Connect your own OpenAI, Claude, or Grok API key and choose a vision-capable model. Media Review can help you:
Draft alternative text: get a concise description proposal instead of starting from a blank field. Focus on images without alt text, or include images that already have it.
Catch possible context mismatches: compare an image with its attachment parent page’s title and a short excerpt. Useful for spotting a product photo or illustration that may not fit the surrounding topic.
Spot visible privacy concerns: flag readable email addresses, phone numbers, names, account identifiers, credentials, and other sensitive information visible in the image. Handy when reviewing screenshots before sharing them.
Identify potentially decorative images: review suggestions for empty alt text when an image adds no information.
Act on clear proposals: see the suggested text alongside the current text, context findings, and privacy flags. Apply or dismiss each proposal yourself.
Your judgment stays in the loop. AI findings can be wrong. The plugin does not redact images, identify people, rewrite pages, or automatically publish AI text. Applying a proposal updates the attachment’s alternative text; it does not rewrite alt attributes already saved inside posts or page builders. You can restore the previous value while that review remains current and no later edit has changed it.
Media Review follows the open scan report’s filters and search, reviewing up to 10 matching images per run, one at a time. You choose whether to include parent-page context. It uses the attachment’s recorded parent, not every page where an image appears.
Optional, with your own provider account. Media Review starts off. Running it sends a temporary, metadata-stripped preview directly to your chosen provider; provider API charges may apply. Previews are limited to 1600 pixels on the longest edge and 4 MiB. WordPress needs a working image editor to prepare them. Conversion works independently without an AI account or API key.
Get lighter images without a conversion subscription
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; compare the actual results for your images and quality settings.
Convert on your computer: the bundled browser encoder creates WebP and AVIF, even when your host cannot write those formats. No desktop app or browser extension.
Let your hosting handle WebP: run selected images, your whole library, or future uploads through resumable background jobs.
Use the built-in PHP fallback: on compatible hosts, create WebP without GD, Imagick, or a separate encoder command.
See what you saved: inspect file sizes and savings, search and filter the report, or export matching rows as CSV.
Choose when to serve the results: enable generated-image output when you are ready, with fallbacks for AVIF.
Keep your originals: remove this plugin’s generated copies whenever you need to. Files owned by other tools stay untouched.
Everything needed for conversion is included: no conversion credits, external optimization API, or conversion subscription. Browser conversion keeps the plugin tab open; server jobs can continue through WP-Cron.
The plugin supports PHP 7.4 and newer. The optional built-in PHP encoder requires PHP 8.1+ and zlib and is detected automatically. AVIF conversion runs in the browser; server jobs produce WebP.
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
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, CC 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.
