| 开发者 | cleanor |
|---|---|
| 更新时间 | 2026年7月11日 19:28 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
<picture> tag. Nothing breaks, and any image reverts in one click. Prefer the classic approach? Switch to "Replace files" mode any time..bak of every source file is stored by default so you can revert any image, or the whole library, with one click.<picture> tag. Your files, URLs and MIME types never change. (In Replace files mode, the optimized versions replace the originals and WordPress serves the smaller files everywhere instead.)https://mcp.cleanor.app) purely to be re-encoded, and only the optimized bytes are returned. Cleanor does not require an account and does not retain your images. You can also point the plugin at your own self-hosted endpoint. See our privacy policy at https://cleanor.app/privacy.
cleanor-tools.zip, and click Install Now. (Or copy the cleanor-tools folder into wp-content/plugins/.)No. With the default Auto engine, images are optimized right on your server and nothing is sent anywhere. If the API fallback is used it is free and key-free (rate-limited per site). An API-key field is included for future plans and self-hosting.
Not with the default Auto engine when your server can handle the format (WebP is supported almost everywhere via Imagick or GD). Images are then re-encoded locally and never leave your site. The Cleanor API is only contacted as a fallback, most often for AVIF on hosts without AVIF support. Choose "On this server only" in Settings to guarantee no external requests at all. Settings shows exactly what your server can do.
No, not in the default Keep originals, serve modern mode: your files, extensions and URLs are never changed. Cleanor stores a WebP/AVIF copy beside each image and serves it through a <picture> tag, so supporting browsers get the smaller file while everything else falls back to your untouched original. If you switch to Replace files mode, the file extension changes and WordPress is updated to serve the new file everywhere it references the attachment (old direct hot-links to the previous extension would need updating).
Keep originals, serve modern (default) is non-destructive: originals stay on disk untouched and modern copies are served via <picture>. Safest for existing sites and fully reversible, at the cost of a little extra storage for the copies. Replace files rewrites the actual file to WebP/AVIF (smallest storage, but URLs/extensions change). You can switch modes at any time in Cleanor → Settings → Delivery; already-processed images keep whatever mode they were done in until you re-optimize or restore them.
Yes, and it is on by default. Keep a .bak copy of the original file preserves each replaced file as filename.ext.bak, which is what powers the Restore actions. Turn it off if you would rather save the disk space.
Yes. Set Resize to a maximum width (for example 2560) in settings and any image wider than that is downscaled before it is stored. Set it to 0 to keep original dimensions. Generated thumbnails are never resized by this setting.
Yes, when Remove EXIF, GPS & camera metadata is enabled (default on). This makes files a little smaller and keeps location and camera data out of your public uploads.
Yes. In the Media Library list view, tick the images you want, then pick Optimize with Cleanor (or Restore original (Cleanor)) from the Bulk Actions dropdown and click Apply. You can also narrow the list first with the Cleanor status dropdown (all / optimized / not optimized / restorable).
That is expected in the default "Keep originals, serve modern" mode. Cleanor does not change your original file, so its size in the Media Library stays the same. Instead it writes a smaller WebP or AVIF copy right next to the original on disk (same name plus .webp or .avif, for example photo.jpg.webp) and serves that copy to visitors through a <picture> tag. Because it is a sibling file and not a separate attachment, it does not show up as its own item in the Media Library. To see every processed image with its before and after size and a direct link to the exact file being served, open Cleanor → Images. If you would rather the file on disk itself get smaller, switch to "Replace files" mode in Settings.
Yes. Open Cleanor → Bulk Optimize → Convert to a modern format, pick WebP or AVIF, and click Convert all images. It re-encodes every image in one pass, following your current delivery mode.
Open Cleanor → CleanUp. There you can delete the kept .bak originals (from Replace mode) and remove orphaned WebP/AVIF copies whose source image no longer exists. In the default keep mode your originals are deliberately kept as the fallback served to older browsers, so they are not deleted there; if you want that space back, switch Delivery to "Replace files" in Settings and re-run Bulk Optimize, then delete the resulting backups. When you delete an image from the Media Library, Cleanor now also removes its sibling copies automatically, so nothing is left behind.
It is designed to be reversible. Cleanor does not erase images: it moves the ones that look unused to the WordPress Trash, where you can restore them for about 30 days, and the files stay on disk (so a wrongly flagged image keeps displaying) until you empty the Trash. Emptying the Trash is what frees the space. An image is treated as used if it is attached to a post, set as a featured image, or its file name or ID appears in any post content, custom field or option, so anything else is reported as "looks unused". This is still a best guess and can miss images used only inside some page builders, sliders or theme options, so review the results first and, ideally, keep a site backup.
On single posts and pages it adds a high-priority <link rel="preload"> for the post thumbnail, pointing at its WebP/AVIF version when one exists. The browser fetches your hero image sooner, which usually improves the Largest Contentful Paint metric in Core Web Vitals. It adds no extra requests and can be turned off in Settings → Performance. WordPress itself already handles lazy-loading, async decoding and image width/height, so Cleanor does not duplicate those.
Yes, when Also convert generated thumbnail sizes is enabled (default on).
JPEG, PNG, WebP and AVIF sources. GIF and SVG are skipped for safety.
Yes. Set the API endpoint to any server that implements the Cleanor /v1/optimize contract.
Settings and stats are per-site.
<link rel="preload"> for the post thumbnail on single views, pointing at its WebP/AVIF derivative. No extra requests. Toggle in Settings → Performance.<picture> tag, without changing your original files, URLs or MIME types. Nothing breaks and any image reverts instantly.<picture> wrapping for content images and template/featured images, with automatic browser fallback to the original.