| 开发者 | phucbm |
|---|---|
| 更新时间 | 2026年10月18日 23:27 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
foo.jpg gets a foo.jpg.webp sibling;
the conversion never modifies the source file..htaccess block on Apache/LiteSpeed, with an
<img> to <picture> fallback on nginx or when .htaccess is not writable.wp perxel-image) for running it over SSH.perxel-image-optimizer folder to /wp-content/plugins/.The WebP conversion never does: every converted file is a new .webp sibling
next to the original. The image size limit does, by design: a new upload
bigger than the maximum (1920 px by default) is scaled down, and the full-size
original WordPress keeps beside the scaled copy is deleted. Set the maximum to
0 for no limit, or turn off "Delete originals of scaled uploads" to keep them.
"Shrink existing images" (or wp perxel-image cleanup) changes images already
uploaded only when you run it, and cannot be undone.
Yes, with WP-CLI: wp perxel-image status, wp perxel-image convert,
wp perxel-image cleanup --dry-run and wp perxel-image settings get|set.
The .htaccess swap is Apache-only. On nginx the plugin rewrites <img> tags to
<picture> with a WebP source instead.
wp perxel-image status, convert, cleanup (with --dry-run) and settings..htaccess block on Apache/LiteSpeed, with an <img> to
<picture> fallback elsewhere.