| 开发者 | edaniels |
|---|---|
| 更新时间 | 2026年9月30日 17:38 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
<picture> mode exists in Settings (off by default).Yes. It hooks into WordPress core media/image APIs, so themes and plugins that use standard WordPress image functions work without theme changes.
No. Originals stay on your server as fallbacks. The plugin creates optimized copies (or cloud/CDN URLs when that service is enabled). You can keep serving or restoring from the originals.
No. Optimized versions are added alongside originals. Untouched originals remain available for unsupported browsers or if you disable optimization for a file.
Download / page weight: Optimized outputs are commonly 50–70% smaller to transfer than the source files. Format-level ranges are summarized under “File size savings” in the Description. Overview and attachment panels show your byte totals and percentages. Disk space: Originals are kept, so server storage is not reduced by default. Savings are about faster pages and less bandwidth for visitors — not freeing upload-directory capacity.
Conversion (especially video) is CPU-intensive while jobs run. Work is queued in the background so front-end browsing stays responsive, but a busy bulk run can still load the server. If CPU is limited, enable optional Flux Suite cloud processing so heavy conversion runs off-site, or process the library in smaller batches.
Local video optimization and some animated HEIF → animated WebP paths need FFmpeg on the server. Image-only WebP/AVIF conversion uses GD/Imagick and does not require FFmpeg. Overview shows whether FFmpeg is detected. Without FFmpeg, use Flux Suite cloud processing for video (when licensed and enabled), or stick to images locally.
Local AVIF output needs a library stack that can encode AVIF (typically a capable Imagick/libheif build). The plugin detects capabilities and only offers formats your server can produce. If local AVIF is missing, keep WebP local, or use optional Flux Suite cloud processing to generate formats on Flux infrastructure.
Default: processing is local — media files are not uploaded to Flux for optimization. Optional cloud/CDN: only after you activate a license and enable the external service. Then media (and related metadata) may be sent for processing and CDN delivery. License validation and compatibility checks may send limited site/plugin metadata (see External services below). Newsletter signup sends email only if an admin opts in on the settings form. Full policy: https://fluxplugins.com/privacy-policy/
Yes. Disable external/cloud processing in plugin settings anytime to return to local-only optimization; new work stays on your server. CDN URLs stop being used for new delivery according to your settings once cloud is off (existing CDN-hosted assets may remain on Flux until cleaned up per service terms). Billing or license cancellation for a paid Flux Suite subscription is managed on fluxplugins.com (the plugin cannot cancel a store subscription by itself).
With a valid license and cloud/CDN enabled, optimized (and optionally other) media can be stored on Flux's global CDN and served over HTTPS from allowlisted hosts. Core local optimization does not require the CDN. CDN is opt-in, intended for faster worldwide delivery and to pair with offloaded processing — not a replacement for keeping originals locally unless you choose that workflow.
This plugin can optionally use the Flux Plugins API for license validation and for optional cloud media processing / CDN delivery. Local image and video optimization works without any external service, license, or outbound media upload.
https://api.fluxplugins.com.https://fluxplugins.com/wp-admin/admin-ajax.php?action=tnp&na=sYes, via wp-config.php constants when needed (staging, custom endpoints): FLUX_MEDIA_OPTIMIZER_EXTERNAL_SERVICE_URL / FLUX_PLUGINS_COMMON_EXTERNAL_SERVICE_URL (common wins if both are set), and the matching *_EXTERNAL_SERVICE_TIMEOUT constants. Most sites never need these.
Yes. Use settings to bulk-convert the media library. Pages that hard-coded old file URLs may need a refresh or re-save so they pick up optimized URLs.
Yes. Media Library list view: Optimization column plus filters for Optimized, Pending, Failed, Disabled, and Unprocessed. Attachment details show per-size savings. Overview shows library-wide totals.
The plugin detects server capabilities and only creates supported formats. For missing encoders, enable optional Flux Suite cloud processing (licensed) so conversion runs on Flux servers, or use whichever local formats are available (often WebP when AVIF is missing).
Yes. With Imagick available, animated GIFs can be converted while preserving animation. Static GIFs are handled as still images.
Yes when the server can decode the file. Static HEIC/HEIF needs Imagick HEIC support; libheif 1.18.2+ is recommended for modern iOS HDR/gain-map photos. Output follows your WebP/AVIF settings. Rare animated HEIF sequences need FFmpeg and WebP enabled for animated WebP; otherwise you get static first-frame output. Apple Live Photos (HEIC + paired MOV) are not supported as a single combined asset. Undecodable files show as Failed in the Media Library.
Yes. Separate WebP and AVIF quality settings let you balance size and visual quality.
Yes. Product images go through the media library, so on-upload and bulk optimization apply like other attachments.
Locally (with FFmpeg): convert to AV1 in an MP4 container and/or WebM, with bitrate/quality controls. Jobs run in the background. Without FFmpeg, use optional cloud processing when licensed, or optimize images only.
mode=list).assets/js/src, src/assets/common/js/src) per Guideline 4; maps/tests/node remain excluded.edit_post attachment capabilities.