| 开发者 | tmmtechnology |
|---|---|
| 更新时间 | 2026年11月4日 18:01 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
Resizing after upload requires the original image to reach the server first. This plugin resizes supported images in the browser before transfer through compatible uploaders, so the server can receive a smaller image. WordPress can still generate thumbnails and other image sizes after receiving the upload.
WordPress has built-in image scaling, and newer upload workflows can also provide browser-side processing. The behaviour depends on your WordPress version and the uploader used by the editor, Media Library or frontend form. This plugin targets compatible Plupload-based WordPress uploaders. If your workflow already resizes images before transfer, it may not need an additional plugin. Test the actual workflow rather than assuming every upload screen behaves the same way.
The bundled uploader's resize path targets JPEG and PNG images. Do not rely on it to resize GIF, SVG, WebP, AVIF, HEIC or other formats. WordPress and other plugins may handle those formats separately.
No. It creates the resized upload in the browser and does not overwrite the source file on your device. When browser resizing succeeds, the uploaded image is the resized version; the plugin does not upload a separate full-resolution original.
No. It applies to new uploads through supported uploaders. Existing images are unchanged.
Its main purpose is to reduce pixel dimensions before upload. Resizing can involve re-encoding, but the plugin does not provide a target file-size setting or automatic WebP/AVIF conversion. It is not a replacement for every image-optimization tool.
Reducing dimensions removes image detail, and re-encoding can change appearance or file size. Choose dimensions suitable for your website, inspect representative photos and graphics, and keep your original files separately.
It can work with product-image uploads that use the compatible WordPress media uploader. Test your product editor and gallery workflow, particularly when another plugin replaces the upload interface.
Only when the workflow uses the compatible uploader and the plugin is enabled for that request context. Some visual page editors run on the front end, so an admin-only setting may not cover them. Custom upload widgets and direct API uploads are not automatically covered.
No. Smaller images can reduce transfer and processing work, but browser memory, file validation, upload limits and server configuration still matter. A file may be rejected before resizing takes place. Very large images can also exceed the browser's own processing capacity.
No. Image resizing happens in the browser, and images are uploaded to your site's configured upload destination. The plugin's administrative notification service is described below.
Open a topic in the WordPress.org support forum or email wp@tmm.ventures. Include your WordPress and plugin versions, browser, uploader mode, enabled context, image format, original dimensions and the upload screen you used. Use a non-sensitive sample image when reporting a problem.
init hook (required since WP 6.7).moxiejs/plupload scripts during the wp_default_scripts hook re-dispatched that hook (via wp_script_is() initializing WP_Scripts), re-entering the handler and recursing until memory was exhausted. The re-entrancy guard is now set before any script API call so nested dispatches return immediately.