Does QuickWebP Delete/Replace the Original Uploaded Image after Converting

  • Resolved NagaTheme

    (@nagatheme)


    1 week, 6 days ago

    Hello My Friends at QuickWebP,

    1. I have a technical question regarding your plugin because I am conducting an in-depth comparison of WordPress image optimization plugins.

    Could you please clarify the following behavior?

    Suppose a user uploads this file:

    example.jpg or example.png

    After your plugin optimizes and converts it to WebP, what exactly happens to the original (source) uploaded JPG/PNG file?

    To avoid any misunderstanding, I’m not asking about backup files created before optimization.

    I’m specifically asking about the original (source) uploaded image that WordPress stores in the Media Library.

    Which of the following best describes your plugin’s behavior?

    Option A

    • The original JPG/PNG remains on disk.
    • A WebP version is created alongside it.
    • Both files continue to exist on the server.

    Option B

    • After successful conversion, the original JPG/PNG is automatically deleted.
    • The optimized WebP becomes the only image stored on disk.
    • WordPress Media Library is updated to use the new image.

    2. If your plugin supports both behaviors, could you please specify:

    • Which option is the default?
    • Which settings enable each behavior?

    3. If the original JPG/PNG is deleted (Option B), are all generated WordPress image sizes (thumbnails, medium, large, etc.) also generated from the WebP image, and does this remain fully compatible with the standard WordPress Media Library and image editing features?

    Or does your plugin intentionally keep the original JPG/PNG to maintain compatibility with WordPress core and third-party plugins?

    4. If the original JPG/PNG is deleted (Option B), does it work for pre-existing images? Or just work for new uploads?

    Thank you very much for your clarification.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Ludwig You

    (@ludwigyou)

    1 week, 5 days ago

    Hello

    Thanks for your very detailed questions, and happy to clarify.

    For QuickWebP 3.2.8, both behaviors exist depending on settings:

    1. What happens to the uploaded source JPG/PNG?
      – Default behavior for new uploads: Option B.
      – The uploaded file is converted during upload, and WordPress stores the converted WebP version as the attachment file.
      – In this default mode, the original JPG/PNG source is not kept as a separate file.
    2. If both behaviors are supported, which is default and which setting controls it?
      – Default: Option B (original not preserved).
      – To enable Option A (keep originals + create WebP alongside), enable the setting:
      “Save original images”.
    3. If originals are deleted (Option B), what about generated image sizes and compatibility?
      – In Option B mode (new uploads), WordPress generates image sizes from the uploaded/converted WebP source.
      – Media Library remains standard (the attachment is a normal WordPress image attachment, but in WebP format).
      – Compatibility generally follows WordPress/WebP support on the server and image editor stack (GD/Imagick).
      – If you need maximum fallback compatibility with plugins expecting JPG/PNG files on disk, use “Save original images” (Option A).
    4. Does deletion/replacement (Option B) apply to pre-existing images or only new uploads?
      – Option B applies to new uploads.
      – Pre-existing images optimized via QuickWebP bulk/single optimization are handled as sidecar WebP files (original files are preserved), which corresponds to Option A behavior for existing media.

    ⚠️ For Option A, please note one important detail: enabling “Save original images” keeps the original JPG/PNG and creates WebP files alongside it, but to actually serve WebP on the frontend you should also enable one of the “Display images in WebP format on the site” modes (either “Use <picture> tags” or “Use rewrite rules”). If display mode is left disabled, WebP files may exist, but WordPress/frontend output may still serve the original JPG/PNG by default.

    Thread Starter NagaTheme

    (@nagatheme)

    6 days, 15 hours ago

    Thank you so much for your great and complete reply. I have share my review of QuickWebP here: https://wordpress.org/support/topic/quickwebp-the-essential-image-optimization-plugin-for-wordpress/

    Wish You All The Best

    Plugin Author Ludwig You

    (@ludwigyou)

    6 days, 3 hours ago

    Thank you very much for your feedback; I just read and replied to it.

    Please note that I released version 3.3.0 seven days ago, and it includes significant UI/UX improvements. I hope this will make the options clearer.

    Best regards

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.