WordPress | July Updates Prepare Themes and Plugins for 7.1
WordPress has published its July 2026 developer roundup as the platform moves into the testing phase for WordPress 7.1. The update covers responsive block styling, new theme layout controls, React 19 compatibility work, media improvements, AI development APIs, and changes that plugin and theme authors should review before the final release arrives on August 19, 2026.
WordPress 7.1 testing is now the main priority
WordPress 7.1 Beta 1 is now available for testing, giving theme and plugin developers their first official opportunity to check compatibility with the next major release. Additional betas are scheduled for July 22 and July 29, followed by the first release candidate on August 5.
This testing period matters because several editor, layout, component, and API changes can affect existing products. Problems found during beta are usually easier to address than issues discovered after client sites and commercial templates have already updated to the final version.
WordPress 7.0.1 was also released on July 9 as a maintenance update containing fixes across Core, the block editor, media tools, and the administration interface. Production sites should remain on stable releases, while WordPress 7.1 testing should be limited to local or staging environments.
Responsive block styling is ready for practical testing
One of the most important design changes is responsive styling inside the block editor. Designers can apply different block styles for individual viewport sizes instead of depending entirely on custom CSS or separate layout variations.
Gutenberg 23.5 also replaces the fixed desktop, tablet, and mobile preview buttons with a freely resizable preview canvas. This gives theme creators a more realistic way to inspect how blocks respond between common breakpoints rather than checking only three preset sizes.
Blocks using standard WordPress block supports can receive responsive settings automatically. Custom block controls require additional work, so developers maintaining their own spacing, aspect ratio, alignment, or layout interfaces should test them carefully.
Theme layouts gain fixed widths and more flexible grids
WordPress 7.1 also brings more precise layout behavior for block themes. Flex items configured with a fixed width will now remain fixed instead of shrinking when the container becomes crowded. The previous flexible behavior is being separated into a Max width option.
Grid layouts are gaining a Fill available space control based on CSS auto-fit. This allows columns to expand when fewer items are present instead of reserving space for empty tracks. For theme builders, that can improve card grids, product collections, post lists, and other reusable layouts without additional CSS.
Block Bindings are also expanding to List Item blocks and nested content. This gives developers more options for connecting dynamic data to structured page elements while preserving inner blocks instead of flattening their content.
Plugin interfaces need React and component checks
Plugin developers should begin testing against React 19. Gutenberg includes an experimental flag that replaces the current React 18 bundles with React 19 and reports warnings when a plugin depends on removed or outdated behavior.
This is particularly relevant for plugins that ship compiled JSX, use @wordpress/element, or interact directly with editor internals. Fixing warnings during the beta cycle can prevent broken controls and support problems when the platform completes the transition.
WordPress components are also standardizing around a 40-pixel control height. The temporary __next40pxDefaultSize property is being deprecated across controls such as text fields, range controls, font size pickers, unit controls, and selection components.
Icon styling changes may affect existing plugin designs
All icons in the latest @wordpress/icons package now use currentColor. Plugins and themes should style icon colors with the CSS color property rather than targeting fill.
This small change can affect toolbar buttons, settings panels, custom blocks, and administration screens where icons use brand colors or state-specific styling. A visual review is worthwhile even when the interface continues to function correctly.
WordPress 7.1 is also preparing a broader Icons API, including registration functions and an endpoint for icon collections. This should eventually give theme and plugin authors a more consistent way to supply their own icons inside the editor.
IMPORTANT: WordPress 7.1 Beta 1 is intended only for development and testing. Do not install it on production, client, store, membership, or other mission-critical websites. Use WordPress Playground, WordPress Studio, a local installation, or a separate staging site.{alertWarning}
WordPress continues building foundations for AI tools
The WordPress AI Client is preparing streaming responses and embedding support for version 7.1. These are developer-level building blocks rather than finished AI features, but they can help plugins provide generated content, semantic search, and vector-based retrieval through a more consistent foundation.
The Abilities API is also moving toward its first practical Core abilities for reading settings, content, and users. These operations remain subject to existing WordPress permissions and are designed to give automation tools a controlled way to understand what a site allows them to do.
For site creators, the long-term value will depend on how responsibly plugin developers use these APIs. Clear permissions, limited access, useful controls, and transparent actions will remain important when AI tools can interact with real site data.
Media and development tools receive useful improvements
Media development continues with more resilient upload queues, better preservation of Ultra HDR data, expanded HEIC and HEIF handling, and new REST options for output format, image quality, and progressive rendering. Infinite scrolling is also returning to the Media Library with an option for users who prefer not to use it.
WordPress Studio is now available on Linux, expanding the official local development application beyond macOS and Windows. The application has also added Studio Code, an agent-assisted development feature available during its beta period.
These changes give developers more options for testing themes and plugins locally before introducing updates to a live site. They are also useful for preparing reproducible test environments when reporting compatibility problems during the WordPress 7.1 beta cycle.
Daisuki's Take: What This Means for Web Designers
For web designers, responsive styling is the most visible part of the July update. Being able to adjust block presentation across viewport sizes directly inside the editor can reduce some of the custom CSS normally required for mobile and tablet layouts.
We think theme and template creators should pay equal attention to the less visible compatibility changes. Fixed flex widths, auto-fit grids, larger component controls, React 19, and new icon behavior can all affect how an existing product looks or behaves after an update.
The practical step is to create a copy of an active theme or plugin in a test environment, install WordPress 7.1 Beta 1, and inspect editor controls, responsive layouts, blocks, icons, media, and frontend output. Testing now gives creators time to correct problems before users receive the final release in August.
Sources and Recommended Links
- What's new for developers (July 2026) | WordPress Developer Blog
- WordPress 7.1 Beta 1 | WordPress News
- WordPress 7.1 release schedule | Make WordPress Core
