Hi @ademkuday,
Thank you for reaching out to Cloudinary! I behavior that you would like to achieve ultimately affects how WordPress would generate the images in its storage. That said, can you please try to set under the WordPress media settings. Setting each max width and height to 0 (zero) will stop WordPress to generating image variations such as Thumbnail, Medium, Large size and should only place the original image in your WordPress storage. Let me know how it goes.
Hi @ademkuday, Thanks for the update. Unfortunately, altering WordPress behavior is out of our plug-in’s scope. However, you may download a third-party plugin that will do this job. Consequently, our plug-in will follow this behavior and will not generate the media sizes that you would normally expect.
Hi @atdcloud Anthony,
Thank you for the quick follow-up and for clarifying the current scope.
I believe the desired behavior could be achieved nicely by adding a new storage/sync option in the “Media Library Sync Settings > Storage” section.Currently the options are:
– Cloudinary and WordPress
– Cloudinary and WordPress (low resolution)
– Cloudinary only (removes everything locally)
A new hybrid option such as “Cloudinary delivery + keep original locally only” (or similar wording) would be a valuable addition:
– Keep only the original full-size file on the server (for backup/archive/full-res access)
– Serve all sizes — including variants and the original — optimized via Cloudinary’s CDN
This would offer an ideal balance: secure local original backup without wasting space on variants, while fully utilizing Cloudinary’s optimization and delivery capabilities. It would be particularly helpful for users who value data sovereignty or long-term archiving.
If this hasn’t been passed to the development team yet, could you kindly forward the suggestion? I’m hopeful that a solution like this could be considered in a future update.
Thank you again for your support and responsiveness!
Hi @ademkuday ,
Thank you for sharing your detailed response. We are conversing if this can be added to our feature candidate. We will surely let you know when we this is added.
Thanks.
The ‘Cloudinary only’ option currently deletes all local files. I believe that a simple modification to allow original files to remain on the server would add great value to this feature. Thanks.
Hi @ademkuday,
We’re still in the early stages of discussions on this, so we don’t have a timeline to share for the feature request right now.
In the meantime, if there’s anything else we can help with, just let us know.
