Ludwig You

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 1 week, 1 day ago by Ludwig You.
• This reply was modified 1 week, 1 day ago by Ludwig You.

Hi Spencer,

Thank you again for this excellent suggestion and for your clear comments.

Good news: We’ve just released improvements to the Code Editor experience.

What’s new:

A full screen button has been added to the top right of the editor.
Fullscreen support is now available in all similar code editors in the plugin, not just the Custom Frontend CSS.
You can exit full screen with the button or by pressing Esc.
This should make long CSS/JS/HTML snippets much easier to use.

Thanks again for helping us improve the plugin.

Hello,

Why not open a topic on support?

Can you tell me more about your problem?

I don’t speak Russian, but if I believe the translation, I understand that the plugin would not have “detected your forms”, except that in no case is it used to detect forms. but to add a Honey pot without having to configure anything.

Hello Peter,

Je viens de corriger le souci, le patch se trouve dans la version 2.17.1.

Merci de m’avoir remonté ce petit bug.

Bonne journée !

Hello,

This has just been patched in version 2.15.0.

Thank you for reporting this issue.

Hello,

Thanks for reporting this. We’ve tested the latest WPMasterToolKit release on our side and, so far, we’re not able to reproduce any issue with HTML emails in the SMTP module.

To help us investigate further, could you please provide:

1. An export of your WPMasterToolKit configuration
2. A list of all active plugins on your site

With this information, we should be able to better understand what’s happening.
If the issue still isn’t reproducible, we may need temporary access to your site to go further.

Thanks in advance for your help.

Note: If you want to send your configuration confidentially, you can send it to [email protected].

• This reply was modified 5 months, 2 weeks ago by Ludwig You.

Bonjour,

Merci pour le signalement détaillé et pour la proposition de correctif 👍
Nous avons pu reproduire le comportement de notre côté.

Nous avons intégré un correctif basé sur la méthode native WordPress wp_image_maybe_exif_rotate, en appliquant la rotation EXIF directement après l’instanciation de l’image et avant toute optimisation ou conversion.

Le correctif :

• lit les données EXIF (exif_read_data)
• applique la logique de rotation/flip selon l’orientation détectée
• reste compatible avec les filtres WordPress existants
• n’impacte pas les images sans données EXIF

Ce fix a été intégré et publié dans la version 3.2.7 de l’extension.

Merci encore pour votre retour précis et la piste technique fournie, c’est exactement le type de feedback qui permet d’améliorer rapidement le plugin 👍
N’hésitez pas si vous constatez d’autres cas limites ou comportements similaires.

Bonjour,

Alors pas d’inquiétude, rien d’irréversible, si vous avez utilisé la fonctionnalité de conversion en masse, vous pouvez à tout moment désactiver pour que cela revienne à la normale.

Voici la configuration que je vous recommande :

Sur “Display images in WebP format on the site” choisissez “Use rewrite rules” qui fonctionne mieux que l’option ” Use <picture> tags” généralement.

En tout cas le plugin ne devrais pas avoir de souci avec Elementor, car massivement utiliser avec.

NB: Si vous avez un serveur NGINX il se peut que les règles de réécritures ne soient pas prise en compte, mais dans se cas vous verrez l’image d’origine logiquement.

NB: Seulement des correctifs sont désormais proposé sur QuickWebP, mais pas de nouveauté, car QuickWebP fait maintenant partie du plugin WPMasterToolKit. Je vous recommande donc de switcher ver celui-ci. Une migration automatique vous sera proposé et depuis WPMasterToolKit vous aurez plus d’options.

Un tuto est d’ailleurs disponible en vidéo dans votre interface QuickWebP.