Thank you for your feedback! I’ll clarify a few important points about how QuickWebP works: 1. Compression quality ≠ Maximum file size
Your request for a “maximum file size” instead of a percentage shows a misunderstanding of how image compression works.
What QuickWebP currently does — like all image compression tools:
The “Quality” setting, currently 0–100%, default 75%, controls the compression level applied to the image.
The lower the quality, the more the image is compressed, and the smaller the file becomes.
It is a compression algorithm, not a file size limit.
Why a “maximum file size” cannot be reliably defined:
The final size of a compressed image depends on its visual complexity — colors, details, contrast — not only on its dimensions.
A 1000×1000px photo with a lot of details can be heavier than a very simple 2000×2000px image, even with the same quality setting.
Concrete example:
- Complex photo, landscape, 1000×1000px at 75% quality → 250 KB
- Simple logo, 2000×2000px at 75% quality → 80 KB
If you set “maximum size = 150 KB”, the logo would be perfectly fine, but the photo would need to be over-compressed and could become unreadable.
The right approach — the one used by QuickWebP:
Setting a consistent quality level, for example 75%, ensures that all your images keep the same visual quality level.
Each image will have a different file size depending on its complexity, but all of them will remain visually optimized.
You can adjust the global quality depending on your needs:
- 70% for stronger compression
- 85% for higher quality
Also, QuickWebP already provides a setting to resize images using a maximum width in pixels, which is the proper way to help control file sizes. 2. Bulk optimization: already available!
QuickWebP already includes a Bulk Optimization feature, available in the plugin settings. This feature allows you to optimize all existing images in your media library.
Please check the Bulk Optimization section in your QuickWebP settings:
Media → QuickWebP 3. WP All Import: technical limitation
QuickWebP integrates with standard WordPress hooks during image upload, such as wp_handle_upload_prefilter.
If WP All Import bypasses these native WordPress hooks, which is likely for performance reasons, QuickWebP cannot intercept those images.
-
This reply was modified 6 days, 4 hours ago by
Ludwig You.
-
This reply was modified 6 days, 4 hours ago by
Ludwig You.