On April 21, 2026, the WordPress Core Performance team convened to discuss ongoing efforts around enhancing image handling and layout optimization, focusing in particular on the Auto Sizes feature. This feature, which dynamically calculates responsive image sizes, is a key step toward improving front-end performance across diverse WordPress sites.
Key Takeaways
- The Auto Sizes feature for responsive images remains a priority for WordPress Core performance improvements.
- Issue #2449, outlining next steps for Auto Sizes, has been opened and is under review by contributors.
- Resolving the sizes issue specifically for the Gallery block is seen as critical before proposing the feature for core inclusion.
- Community engagement is encouraged, with developers like @ravikhadka expressing interest in contributing to the feature’s development.
- The next Core Performance chat is scheduled for May 5, 2026, at 16:00 UTC, continuing the collaborative momentum.
Context and Importance of the Auto Sizes Feature
Responsive images have long been an essential part of modern web performance strategies. By delivering the right image size to the right device, sites reduce unnecessary bandwidth consumption and improve page load speeds. WordPress, powering over 45% of the web, must optimize this core capability to maintain and enhance user experience at scale.
The Auto Sizes feature automates the generation of the sizes attribute in HTML <img> tags. This attribute informs browsers about the intended display width of an image based on the viewport, enabling them to select the most appropriate image source from the available srcset candidates. Without accurate sizes information, browsers may download images that are too large or too small, resulting in wasted data or degraded quality.
In practice, implementing Auto Sizes within WordPress is challenging due to the complexity of theme layouts, block variations, and dynamic content. The Gallery block, which allows users to arrange images in grids or masonry layouts, poses additional sizing calculation challenges. The performance team’s efforts to resolve the sizing issue for this block are pivotal because the Gallery is widely used and impacts many sites’ visual and performance characteristics.
Progress Report from the April 21 Performance Chat
The team shared updates from recent discussions, including a presentation by @westonruter at WordCamp Asia where the Auto Sizes feature was highlighted. This external exposure has helped galvanize interest and clarify the path forward in issue #2449 on the WordPress core Trac.
@mukesh27, a key contributor to the Performance Lab plugin which prototypes performance enhancements, indicated plans to revisit the sizing issue soon. He encouraged other developers to contribute to the dialogue and implementation, reinforcing that community collaboration remains essential to moving the feature into the core.
Additionally, @ravikhadka expressed enthusiasm for helping advance the Auto Sizes feature. Such community participation is vital given the complexity of the underlying CSS and JavaScript interactions required to accurately detect display conditions and generate correct sizes values.
The team also reaffirmed the upcoming chat scheduled for May 5, 2026, at 16:00 UTC, providing a fixed cadence for ongoing coordination.
Technical Challenges and Considerations
From an engineering perspective, Auto Sizes must handle a wide range of scenarios. WordPress themes vary greatly in their CSS layouts, from fixed-width containers to fully fluid grids, and from simple column layouts to complex flexbox or grid-based designs. Calculating the accurate image display size requires understanding these styles in real time or approximating them server-side.
For blocks like Gallery, the challenge multiplies because multiple images coexist in a responsive layout, and user choices affect the arrangement. The feature needs to dynamically adjust sizes attributes per image in the block, ensuring that each image’s loading strategy is optimized.
Previous attempts at static sizes or hard-coded attributes have proven insufficient in real-world deployments, often causing images to load suboptimally. The Performance Lab plugin serves as a testing ground for these approaches, iterating toward an implementation that is both performant and compatible with typical WordPress usage.
Integration Path and Future Outlook
The current strategy focuses on stabilizing Auto Sizes for the Gallery block first. Once this is addressed, the feature can be proposed for broader inclusion in WordPress Core. This incremental approach allows the team to validate the feature’s behavior on a critical use case before expanding to other blocks and themes.
The WordPress Core team’s rigorous review process ensures that any performance enhancement is compatible with the diverse ecosystem of themes, plugins, and hosting environments. The Auto Sizes feature promises to reduce unnecessary image downloads and speed up page loads without requiring user intervention.
In the broader context, this work aligns with WordPress’ commitment to improving Core Web Vitals metrics, which are increasingly important for SEO and user experience. Auto Sizes is one piece of a larger puzzle that includes image lazy loading, optimized asset loading, and modern JavaScript improvements.
What This Means for WordPress Users
For WordPress developers, especially theme and block authors, the Auto Sizes initiative signals an upcoming shift toward smarter image handling baked into Core. We recommend following the progress of issue #2449 and participating in the #core-performance Slack channel if you want to contribute or test early implementations.
Site owners should anticipate improved front-end performance once Auto Sizes lands in Core, particularly for sites heavily using the Gallery block or image-rich content. This improvement will help reduce bandwidth costs and improve visitor engagement through faster load times.
Agencies and hosting providers should prepare to incorporate updated performance testing in their workflows, as these changes may affect caching strategies and front-end diagnostics. Early adoption of the Performance Lab plugin can provide insights into how these improvements behave in real environments.
Overall, the active community involvement and structured roadmap for Auto Sizes indicate a thoughtful approach that balances technical complexity with practical impact. We expect this feature to become a foundational part of WordPress’ performance toolkit within the next several months.
Frequently Asked Questions
What is the Auto Sizes feature in WordPress?
Auto Sizes automatically generates the sizes attribute for responsive images, optimizing which image variant a browser downloads based on the display size. This improves page load times and bandwidth efficiency.
Why is the Gallery block important for this feature?
The Gallery block presents multiple images in responsive layouts, making sizing calculations more complex. Fixing sizing issues here ensures the feature works well in one of the most commonly used blocks.
How can developers contribute to the Auto Sizes feature?
Developers can join the #core-performance channel on Slack, review issue #2449 in the WordPress Core Trac, and test or submit patches to the Performance Lab plugin where the feature is actively developed.
When will Auto Sizes be included in WordPress Core?
There is no fixed release date yet, but progress is ongoing. The team is focusing on stabilizing the feature for the Gallery block before proposing it for core inclusion. Expect updates in upcoming core releases later this year.
