diegopetroncari

<p><strong>Petro SEO Images to WebP</strong> converts your existing JPEG and PNG attachments to WebP in bulk, then serves them on the front-end through the standard <code><picture></code> element with a full responsive <code>srcset</code>. The original files stay untouched on disk, so reverting is as simple as flipping a switch.</p>
<p>Designed to be small, dependency-free and predictable. No external services, no images uploaded anywhere, no opaque queue.</p>
<h4>What it does</h4>
<ul>
<li>Converts every registered image size (full + thumbnails) to <code>.webp</code> next to the original (e.g. <code>photo.jpg</code> <span aria-hidden="true" class="wp-exclude-emoji">→</span> <code>photo.jpg.webp</code>).</li>
<li>Wraps <code><img></code> tags from <code>wp_get_attachment_image()</code> and <code>the_content</code> in <code><picture><source type="image/webp">…</picture></code>, preserving full <code>srcset</code> and <code>sizes</code>.</li>
<li>Skips images automatically if a previous run failed because of filesystem permissions, so you can retry on demand without reprocessing the whole library.</li>
<li>Ramps the WebP quality down (75 <span aria-hidden="true" class="wp-exclude-emoji">→</span> 60 <span aria-hidden="true" class="wp-exclude-emoji">→</span> 45 <span aria-hidden="true" class="wp-exclude-emoji">→</span> 40) when the encoded file ends up larger than the original, so you never ship a “WebP” that is heavier than the JPEG.</li>
<li>Idempotent: re-running the bulk job only touches new or updated images.</li>
</ul>
<h4>What it does NOT do</h4>
<ul>
<li>It does not delete or modify your original JPG/PNG files.</li>
<li>It does not require Imagick or a specific image library beyond what WordPress already uses (<code>wp_get_image_editor()</code>).</li>
<li>It does not phone home, register endpoints, or load remote scripts.</li>
</ul>
<h4>Privacy</h4>
<p>The plugin processes images locally using WordPress’s built-in image editor. No data is sent to third-party services.</p>


Petro SEO Images to WebP

Bulk-convert media library images to WebP for better SEO and Core Web Vitals. Originals stay on disk; the front-end serves WebP via the  tag.

Orangelab

Rickard Westerlind

<p>Dramatically improve the quality of re-sized images by making WordPress use ImageMagick instead of standard GD image library.</p>
<p>Features</p>
<ul>
<li>Preserve embedded color profile in re-sized image</li>
<li>Automatically recognize custom image sizes</li>
<li>Allow regeneration of existing images (optionally for selected image sizes only)</li>
<li>Configure image quality or use dynamically computed default value</li>
<li>Optimize different image sizes for either quality or size</li>
</ul>
<p>Lnguages: English, French, German, Swedish, Turkish</p>
<p>Requires either ImageMagick binary or Imagick PHP module.</p>
<h3>Contribute</h3>
<p>Code repo available on https://github.com/orangelabweb/imagemagick-engine/</p>


ImageMagick Engine

Maybe even better.  It uses ImageMagick Engine that is installed and allows me to easily regenerate all my images.

Works as advertised

The thumbnail regeneration could be a bit faster though. I have used it for longer than I can remember, at least 5 years.

Simple, functional

Improve the quality of re-sized images by replacing standard GD library with ImageMagick.

Petro SEO Images to WebP vs ImageMagick Engine