On-Demand Image regeneration: When Will WordPress Implement It?

  • razaanstha

    (@razaanstha)


    3 months, 1 week ago

    I’ve been thinking about how WordPress handles images for many years, and it seems like there should be some type of discussion for improvements and new ideas. Currently, every time we upload a new image, WordPress regenerates the image in all registered sizes, leading to unnecessary storage use and clutter.

    It would be better if WordPress generated sizes only when needed instead all regenraring in all registered sizes? While AVIF and WebP formats are nice steps forward, they don’t fully address the existing issues. We need more modern approach to image regeneration and cropping. Features like content-aware cropping, which ensures people and important objects are cropped correctly, would be fantastic. WordPress still doesn’t support on-demand image size generation natively. It would be great if this feature could be implemented natively to help users optimize storage usage while reducing clutter for unused and unnecessary sizes.

    Has anyone heard of any updates or new features that might address this? I’d love to hear your thoughts and experiences from the communicty!

Viewing 1 replies (of 1 total)
  • Krystle Salazar

    (@krysal)

    3 months ago

    Hi @razaanstha 👋 Your thoughts on this topic resonated greatly with me. I can see how the default preference is the speed of having images ready to load over saving on storage, but still, some might prefer the other way around.

    The most recent recent discussion I found on this is in this GitHub issue, which links to an older track ticket. I don’t have the whole picture; there are plugins as proof of concept, but it seems some complex edge cases for when things don’t go as expected or how exactly it will work under the hood are missing consensus and work. The post looks like it lost momentum since the original poster stopped replying (understandable after the time elapsed), but if you consider it important and still relevant, you can continue the conversation in those threads. That will signal the maintainers that the feature is highly required and considered a priority for future versions.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.