| 开发者 | enetrato |
|---|---|
| 更新时间 | 2026年9月3日 22:03 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/veloimg/ directory, or install the plugin through the WordPress plugins screen.No. Original JPG and PNG files are not modified. VeloIMG writes derivative files into the uploads derivative storage.
It depends on the selected strategy. For example, with AVIF -> WebP -> original, the browser receives AVIF when possible, then WebP, then the original image.
PHP Safe delivery rewrites WordPress image markup into picture/source markup and lets the browser choose supported generated formats.
Apache/LiteSpeed delivery keeps HTML unchanged and uses rules in uploads/.htaccess to serve generated AVIF or WebP files according to the browser Accept header and the selected format strategy.
VeloIMG records a reason when generation fails or a derivative is intentionally not saved. Common reasons include missing encoder support, unreadable source files, invalid generated files, transparency loss during AVIF conversion, or a generated file being larger than the original.
Some server AVIF encoders can remove transparency. VeloIMG checks this case and does not save an AVIF file when transparency would be lost.
Yes. Bulk generation can be stopped and continued. Progress is stored so already processed files do not need to be processed again unless files are deleted or regenerated.
Yes. WebP and AVIF use separate generation flows. On limited shared hosting, running them one after another is recommended to reduce server load.
Only when you explicitly use the delete controls. Deleting derivatives does not delete original images.