开发者 | coreessentials |
---|---|
更新时间 | 2025年6月30日 15:21 |
PHP版本: | 5.8 及以上 |
WordPress版本: | 6.8 |
版权: | GPLv2 or later |
版权网址: | 版权信息 |
.webp
, so posts and pages seamlessly use the new files./wp-content/uploads/
directory and database before running a bulk conversion. Testing on a staging site is also strongly recommended.
/wp-content/uploads/
directory and database.Only after successfully converting to WebP and verifying the WebP is smaller. Otherwise, originals remain. Always keep backups.
WordPress stores more than just the single file you see in the Media Library.\ For every image it also creates several thumbnail sizes, so the true footprint is: (original file + all JPEG/PNG/GIF thumbnails) When WebP Image Converter & Replacer shows savings it compares the combined size of those originals with the combined size after conversion: (original file + JPEG/PNG/GIF thumbs) − (WebP file + WebP thumbs) = space saved Because thumbnails often add up to more kilobytes than the original, the reported savings can exceed the size of the single file you uploaded—this is expected and accurate.
Your site continues serving the WebP images. Uninstalling removes plugin settings but does not restore deleted images.
As of 2025, nearly all modern browsers (Chrome, Firefox, Edge, Safari 14+, Opera, most mobile) support WebP. If legacy browsers matter to you, consider keeping originals or using a JavaScript fallback.
It converts format. WebP's algorithm usually shrinks file size significantly without extra quality loss. It does not downscale or apply custom compression levels in this version.
Currently WebP only. AVIF may be added once browser support and server tooling are more mature.
Not via UI in version 1.0. Default quality (~80–85) balances size and clarity. Advanced users can adjust via a filter hook or Imagick defaults.
Partially. Activate network-wide, then run bulk conversion per site. Test carefully and back up each site first.
Restart conversion; processed images are skipped. For persistent issues, convert in smaller batches, raise PHP memory/time limits, or consult your error logs.