The WordPress core roadmap continues to evolve in 2026, with major releases and longer-term development work shaping the future of the platform. Whether you run a business website, build themes or manage client sites, keeping up with WordPress development is about more than discovering new features – it can help you plan upgrades, maintain compatibility and make better decisions about your website’s future.
With WordPress 7.0 released earlier this year and WordPress 7.1 continuing that development path, attention is now turning to what comes next. Ongoing work across the WordPress project includes improvements to the block editor, collaboration tools, performance, accessibility and the technologies developers use to build modern WordPress experiences.
In this article, we look at the WordPress roadmap for the rest of 2026 and beyond, separating features that have already arrived from developments that are still being explored or actively worked on. We’ll also examine what these changes could mean for website owners, developers and agencies preparing for the next stage of WordPress.
WordPress Roadmap Core Overview and Strategic Direction
The WordPress roadmap is about more than introducing individual features. Core development is guided by contributors across the project, with ongoing work focused on making WordPress easier to use, more capable and better prepared for the changing needs of website owners, publishers and developers.
A major part of that direction is the continued evolution of the block editor and Site Editor, alongside improvements to performance, accessibility, collaboration and the overall editing experience. WordPress is also continuing its focus on Data Liberation, making it easier for users to move content between platforms and retain greater control over their data.
Longer-term development is closely tied to the wider Gutenberg roadmap, including collaborative workflows and improvements to publishing and site management. At the same time, contributors must balance new capabilities with backward compatibility, web standards and the enormous ecosystem of existing WordPress themes, plugins and websites.
This means the roadmap is not a fixed list of guaranteed features and release dates. Priorities can change as features are tested, technical challenges emerge and feedback is gathered from the WordPress community. For businesses and developers, following this broader direction can provide a clearer picture of where WordPress is heading and which changes may affect future website projects.
Expected Release Timeline and Scheduled Releases for 2026
- WordPress 7.0 – Released 20 May 2026:
WordPress 7.0 marked the first major release in the 7.x series. Originally planned for earlier in the year, its final release was moved to 20 May following additional development and testing. - WordPress 7.1 – Released 19 August 2026:
The second major WordPress release of 2026 arrived on 19 August. Its development focused on areas including collaboration, improvements to Notes, responsive styling, editor enhancements and new tools designed to support modern publishing workflows. - WordPress 7.2 – Planned for December 2026:
WordPress 7.2 is expected to be the third and final major release of the year. Development began in August, with Beta 1 currently planned for 20–22 October, followed by additional beta releases throughout late October and early November. - WordPress 7.2 Release Candidates:
The first release candidate is currently planned for 17–19 November, followed by RC2 on 24–26 November and RC3 on 1–3 December. These pre-release versions give developers, agencies and hosting providers an opportunity to test compatibility before the final release. - WordPress 7.2 Final Release:
The current release window is 8–10 December 2026, although WordPress development schedules can change as testing progresses. Maintenance and security releases may also appear between major versions when fixes are required.
For businesses, developers and agencies, following these milestones provides valuable time to test themes, plugins and custom functionality before deploying a major WordPress update to a live website.
Key Platform-Level Changes Coming to WordPress 7.0
-
Released on 20 May 2026, WordPress 7.0 introduced a substantial collection of changes across the editor, administration experience and developer APIs. Rather than representing a single architectural overhaul, the release continued WordPress’s broader shift towards more flexible block-based editing and extensible site-building tools.
- Site Editor and Routing Improvements: WordPress 7.0 laid further foundations for an extensible Site Editor, including improvements to routing and route validation. A new
@wordpress/bootpackage also gives plugin developers additional options for building custom pages that integrate with the Site Editor experience. - Interactivity API Enhancements: The Interactivity API continued to mature in WordPress 7.0, including the introduction of a new
watch()function. These improvements give developers more options for creating interactive front-end experiences while working within WordPress’s block-based architecture. - DataViews and DataForms Improvements: WordPress 7.0 expanded DataViews and DataForms with interface and extensibility improvements, including new Activity and Details layouts, refinements to modal interfaces and support for registering third-party types through the Field API.
- Block Bindings and Pattern Overrides: Improvements to the Block Bindings API expanded the ways developers can connect dynamic data to blocks. WordPress 7.0 also continued work around pattern overrides, helping make block patterns more flexible for structured and reusable website designs.
- Broader Core and Admin Improvements: WordPress 7.0 included hundreds of Core tickets covering enhancements, feature requests and bug fixes. More than 40 tickets focused on the Editor, while over 90 addressed the WordPress administration experience, alongside numerous developer-focused changes throughout Core.
- Site Editor and Routing Improvements: WordPress 7.0 laid further foundations for an extensible Site Editor, including improvements to routing and route validation. A new
React 19 Upgrade Remains on the WordPress Roadmap
The planned move from React 18 to React 19 remains an important technical change for WordPress, but the transition is taking longer than originally expected. React 19 was initially targeted for WordPress 7.1, but compatibility problems discovered during testing led contributors to postpone its inclusion in Core. As a result, WordPress 7.1 continues to use React 18.3.
Testing has not stopped. React 19 is available as an experimental feature in recent versions of the Gutenberg plugin, giving plugin and theme developers an opportunity to identify compatibility problems before the framework eventually reaches WordPress Core.
One of the main issues uncovered during testing involved plugins that bundle their own React runtime components. Differences between React 18 and React 19 caused some existing plugins to fail, highlighting why a more gradual migration is necessary. Developers whose plugins use compiled JSX, `@wordpress/element` or private editor functionality should therefore pay particular attention to React 19 compatibility testing.
For website owners, there is no immediate React 19 migration required simply because WordPress 7.1 has been installed. For developers, however, the experimental period provides valuable preparation time. Testing plugins and custom functionality now can help identify deprecated React features and other compatibility issues before React 19 eventually becomes part of WordPress Core.
The eventual upgrade should give WordPress access to newer React capabilities while keeping its JavaScript foundations aligned with the wider React ecosystem. However, the experience so far also demonstrates WordPress’s emphasis on backward compatibility: rather than forcing the change into a major release, contributors postponed it while compatibility issues are investigated and resolved.
Gutenberg Collaboration and AI Continue to Evolve
Collaboration remains an important part of the long-term Gutenberg roadmap, although some of its most ambitious features are still under development. Real-time collaborative editing has undergone extensive testing, but it was not enabled in either WordPress 7.0 or WordPress 7.1. Work continues on areas such as conflict handling, compatibility and the technical foundations required before simultaneous editing can become a reliable part of WordPress Core.
WordPress 7.1 did introduce further improvements to collaborative workflows through Notes. Features including email notifications for @mentions and shareable revision links make it easier for teams to discuss and review content inside WordPress, while development continues towards richer collaboration experiences.
AI is also becoming a more important part of the WordPress ecosystem, but its current role should not be confused with having a built-in AI writing assistant in the block editor. Recent Core development has focused largely on infrastructure for developers, including the WordPress AI Client, Abilities API and MCP Adapter. Together, these technologies can help plugin developers build AI-powered features while providing more standardised ways for WordPress functionality to interact with AI systems.
At the same time, Gutenberg and WordPress Core continue to improve the block-editing experience. WordPress 7.1 brought developments such as responsive block styling and pseudo-state styling, alongside continued work on blocks including Tabs, Playlist and Table of Contents.
For website owners and content teams, the direction is clear: WordPress is working towards richer collaborative workflows, more capable design tools and stronger foundations for AI integrations. However, some of these technologies remain works in progress rather than finished Core features, making it important to distinguish what is available today from what remains on the roadmap.
Collaboration and Real-Time Editing in Gutenberg
WordPress continues to work towards a more collaborative editing experience, but some of the most ambitious features remain under development rather than being available in WordPress Core today.
- Real-Time Collaborative Editing:
WordPress has been testing technology that allows multiple people to edit the same post or page simultaneously, similar to collaborative document-editing platforms. The feature was originally considered for WordPress 7.0 but was removed before release following concerns around reliability, race conditions, server load and memory efficiency. Further testing continued during the WordPress 7.1 development cycle, but real-time collaboration is not enabled in the final 7.1 release. - Notes and Editorial Feedback:
Notes are becoming an increasingly important part of WordPress’s approach to collaboration. Development has explored richer feedback tools, including suggestions, reactions and more detailed discussions attached to content. These features aim to make it easier for writers, editors and clients to review content without moving every conversation to a separate communication platform. - @Mention Email Notifications:
WordPress 7.1 introduced email notifications for @mentions in Notes. This makes it easier to bring a colleague or client into a content discussion and helps ensure important editorial feedback is not missed. - Shareable Revision Links:
Another collaboration improvement in WordPress 7.1 is the ability to share links to specific revisions. This can make review workflows more practical by allowing team members to direct others to a particular version of a post or page. - Real-Time Collaboration Remains in Testing:
Development of simultaneous editing is continuing through Gutenberg, where the technology can be tested before wider integration into WordPress Core. This gradual approach gives contributors more time to address performance, compatibility and conflict-handling challenges across different hosting environments.
For businesses, agencies and editorial teams, the direction is promising, but it is important to distinguish between collaboration features already available in WordPress 7.1 and experimental functionality still being tested for future Core releases.
Unlocking AI Capabilities: Infrastructure for Developers
WordPress is laying important foundations for AI-powered websites, but its current approach is focused primarily on providing developers with reusable infrastructure rather than adding a built-in AI writing assistant to the block editor.
- Built-In WordPress AI Client:
WordPress 7.0 introduced a provider-agnostic AI Client in Core. This PHP API gives plugin developers a standard way to send prompts to supported AI models and receive responses without building a separate integration for every AI provider. Providers can be connected separately, allowing developers to build AI features without tying their plugins to a single model or service. - AI-Powered Plugin Development:
The AI Client can be used to build features such as text generation, image analysis and other AI-assisted workflows. For example, developers could create plugins that generate draft content, describe images or automate specific publishing tasks. These capabilities are made possible by the underlying APIs, rather than being standard content-generation features automatically available in the WordPress editor. - Abilities API:
The Abilities API gives WordPress and plugins a standardised way to describe functionality that can be discovered and executed programmatically. This creates a useful bridge between traditional WordPress functionality, automation tools and AI systems, while retaining WordPress permission checks around what users and applications are allowed to do. - Connectors for External Services:
WordPress 7.0 also introduced infrastructure for managing connections to external services. For AI applications, provider plugins can use this system to connect WordPress with supported AI services while giving administrators a central location for managing the necessary credentials. - MCP and AI Agent Integration:
The WordPress MCP Adapter builds on the Abilities API by allowing compatible AI agents to discover and execute WordPress abilities through the Model Context Protocol. This opens the door to more advanced workflows in which AI tools can interact with authorised WordPress functionality rather than simply generate text.
Together, these technologies give developers a more consistent foundation for creating AI-powered WordPress plugins, automation and agent-based workflows. The important distinction for website owners is that WordPress is currently providing the infrastructure for these experiences rather than automatically adding features such as AI copywriting, brand-voice training or content optimisation to every WordPress website.
Gutenberg Block and Editing Improvements
Development of Gutenberg continues to expand the range of blocks and design tools available to WordPress users. Recent releases have introduced or refined experimental blocks, responsive styling controls and editing tools that could eventually make more complex layouts possible without relying as heavily on additional plugins or custom code.
- Playlist Block:
Work on the experimental Playlist block is exploring new ways to organise and present collections of audio and video content. Development has focused on improving the block’s structure and editing experience as it moves through the Gutenberg testing process. - Table of Contents Block:
The experimental Table of Contents block is designed to generate a structured list of headings from a post or page. Continued Gutenberg development is refining how the block works and how users can control the content included in the generated table of contents. - Tabs Block:
Gutenberg development is also progressing on an experimental Tabs block for organising related content into selectable sections. This could eventually provide a native option for layouts commonly used for product information, service details and other content that benefits from being divided into tabs. - Pseudo-State Styling:
WordPress 7.1 expanded block styling capabilities with support for additional pseudo-states. These controls allow compatible blocks to have different styles for states such as hover and focus, reducing the need for custom CSS in some common design scenarios. - Responsive Styling:
Responsive editing also advanced in WordPress 7.1, giving users greater control over how supported block styles behave across different screen sizes. This forms part of the broader effort to make responsive design more manageable directly within the WordPress editing experience.
Together, these developments show Gutenberg moving towards more flexible block layouts and more sophisticated visual controls. However, features being tested as experimental Gutenberg blocks should not be treated as guaranteed WordPress Core functionality until they have completed development and are included in a stable WordPress release.
WordPress Admin Redesign Continues to Evolve
The WordPress administration experience is undergoing a gradual modernisation rather than a single, all-at-once redesign. WordPress 7.0 introduced several visible changes, including the new Modern admin colour scheme, dashboard improvements and wider access to the Command Palette. WordPress 7.1 continued that work with further interface, navigation and accessibility improvements.
An important part of this longer-term direction is the evolving WordPress Design System. WordPress 7.1 introduced a theming foundation built around shared design tokens, helping Core and plugin developers create more consistent interfaces while providing structured controls for characteristics such as colours, sizing and corner radius.
Navigation is becoming more consistent as well. The persistent admin bar now remains available across supported editor screens, helping users move between the front end, administration area, Site Editor and Block Editor without losing familiar navigation controls. Work on DataViews and DataForms is also helping WordPress establish more consistent approaches to displaying and editing information across modern administration interfaces.
Accessibility remains an important part of the process. WordPress 7.1 included improvements to contrast, focus behaviour, keyboard and pointer interactions, administration screens and assistive-technology support. These changes may appear incremental individually, but together they contribute to a more consistent and accessible administration experience.
For businesses, agencies and developers, the important point is that WordPress admin modernisation is already happening release by release. Rather than expecting a completely redesigned dashboard to arrive overnight, users can expect Core interfaces to continue evolving as the shared design system and newer administration technologies mature.
Developer-Friendly Updates: Command Palette and APIs
- Improved Command Palette: The WordPress Command Palette continues to make navigation and common actions quicker. Recent improvements organise commands into clearer sections, including recent, suggested and matching commands, while frequently used commands can persist between sessions. This helps users and developers reach tools and actions without repeatedly navigating through administration menus.
- Expanded Abilities API: WordPress 7.1 significantly expanded the Abilities API introduced in WordPress 6.9. Improvements include better discovery and filtering of registered abilities, execution lifecycle hooks, stronger schema handling and a unified way to expose appropriate abilities to external clients. These foundations are particularly useful for developers building automation, AI integrations and other tools that need to interact with WordPress functionality in a structured way.
- REST API and External Integrations: The Abilities API is also becoming more closely integrated with the WordPress REST API. WordPress 7.1 introduced improvements to how ability inputs are validated and handled, while public abilities can be discovered and accessed by authorised external clients. This provides developers with more consistent building blocks for integrations and automated workflows.
- Developer Documentation and Testing Resources: WordPress continues to support major releases with Field Guides, developer notes, testing calls and practical resources through the WordPress Developer Blog. These resources help plugin and theme developers understand API changes, identify compatibility issues and prepare their projects before adopting new WordPress functionality.
Performance Lab and WordPress Core Performance Improvements
Performance remains a major focus for WordPress development. The Performance Lab plugin, maintained by the WordPress Performance Team, provides a way to discover and test performance features being developed before they are considered for inclusion in WordPress Core.
Rather than operating as a single collection of experimental settings, Performance Lab now works alongside individual feature plugins. Current projects include Enhanced Responsive Images, Image Prioritizer, Speculative Loading, View Transitions, Modern Image Formats and Instant Back/Forward. This approach allows individual performance technologies to be developed, tested and refined independently.
Some performance work has already progressed into recent WordPress releases. WordPress 7.1, for example, introduced significant client-side media processing improvements. Supported image-processing tasks can be handled in the browser rather than relying entirely on the web server, helping reduce server CPU and memory usage while improving support for modern image formats. The system also includes automatic fallbacks when client-side processing is unavailable.
Other performance projects remain under active development. Enhanced Responsive Images aims to help browsers select more appropriately sized images, while View Transitions is exploring smoother navigation between front-end pages. Speculative Loading is also being refined to make navigation feel faster by intelligently pre-loading or pre-rendering likely destinations.
For developers and technical site managers, these feature plugins provide an opportunity to evaluate upcoming performance technologies before wider adoption. Testing should generally take place on staging or development websites first, particularly where a site relies on complex themes, caching systems, media-processing plugins or custom functionality.
Improvements in Media Handling and Responsive Block Styling
- Improved Image Cropping:
WordPress 7.1 expands image-editing capabilities with improved cropping controls, including support for free-form cropping. This gives users greater flexibility when adjusting images without having to rely on a fixed aspect ratio. - Ultra HDR Image Support:
WordPress 7.1 adds support for Ultra HDR JPEG images, allowing compatible images to retain extended dynamic-range information during processing. On supported displays and browsers, this can produce brighter highlights and a wider range of visible tones while maintaining compatibility with standard displays. - Responsive Block Styling:
Responsive styling capabilities introduced in WordPress 7.1 give users greater control over how supported block styles appear at different viewport sizes. This makes it possible to tailor certain design properties for different screen sizes directly through the editing interface rather than relying entirely on custom CSS. - Pseudo-State Styling:
WordPress 7.1 also expands support for styling interactive states such as:hoverand:focuson supported blocks and elements. These controls make it easier to create visual feedback for interactive content while maintaining a consistent design across a website.
Together, these improvements give users more control over media and responsive design while continuing WordPress’s broader move towards more capable visual editing tools.
Community Discussions, Bug Scrubs and the WordPress Release Process
WordPress development is shaped by a global community of contributors working across Core, Gutenberg, accessibility, performance, testing, documentation and many other areas of the project. Major releases go through an open development process that includes regular meetings, testing periods, bug scrubs and public discussions.
Bug scrubs are an important part of this process. Contributors review open tickets, assess bugs, discuss priorities and help determine whether fixes are ready for an upcoming release. These sessions become particularly important as a major WordPress version moves through its beta and release candidate stages.
Much of the coordination takes place through the Make WordPress project and the WordPress.org Slack workspace. Contributors can follow Core development discussions, participate in scheduled meetings, review tickets in WordPress Trac and test beta or release candidate versions before they reach production websites.
You do not need to be a Core developer to contribute. Website owners, designers, developers and testers can help by reproducing bugs, reporting detailed test results, reviewing documentation and testing upcoming releases against different themes and plugins. This wider testing can uncover compatibility and usability issues that may not appear during routine development.
For anyone who wants to follow the WordPress roadmap more closely, participating in these discussions and testing cycles provides a useful view of how decisions are made and how features progress from early development towards a stable Core release.
Open Floor Discussions, Community Feedback and What This Means for Users
Open-floor discussions are a regular part of WordPress Core development meetings, giving contributors an opportunity to raise topics that are not already covered by the main agenda. These discussions can include requests for help with Core tickets, technical concerns, testing feedback and questions affecting upcoming WordPress releases.
Important development topics can also receive dedicated discussion time during Core meetings. Contributors can propose subjects in advance, provide relevant tickets or pull requests and explain what feedback or assistance they need. This creates an open process in which technical decisions and potential changes can be discussed before work progresses further.
Recent release cycles show why this feedback matters. During the development of WordPress 7.1, contributors raised concerns about features including responsive styling, while other technical changes such as the planned React 19 upgrade were postponed when compatibility issues emerged. This demonstrates that roadmap items can change as testing, technical review and community feedback reveal new challenges.
For business owners and developers, following these discussions can provide useful early warning of changes that may affect themes, plugins, custom development or future upgrade plans. However, an item being discussed does not necessarily mean it will become part of WordPress Core. Features can be changed, delayed or removed from a release as development progresses.
Anyone interested in getting involved can follow Make WordPress Core agendas, join relevant discussions in the WordPress.org Slack workspace and participate in testing calls. Providing reproducible bug reports and detailed testing feedback can help contributors identify problems before changes reach millions of production websites.
Data Liberation and Longer-Term Platform Changes
Data Liberation remains an important part of WordPress’s longer-term vision for the open web. The initiative is designed to give users greater control over their content by making it easier to import, export and move data between WordPress and other platforms.
The project is progressing through several phases. Current work includes migration guides and improved tools for importing and exporting structured data, with a focus on challenges such as transferring media, updating links, handling large websites and recovering when a migration is interrupted.
Another area of development focuses on liberating content from closed platforms. WordPress is exploring tools that could help users move content from websites, social networks, page builders and other systems into an open environment where they retain greater control over their data.
Further ahead, the Data Liberation roadmap includes direct WordPress-to-WordPress synchronisation. The aim is to make it easier to copy, synchronise and move WordPress sites and their content, which could benefit website migrations, backups, staging environments and publishing workflows.
The project’s longer-term vision goes further still, positioning WordPress as a central content hub where users could create, store and synchronise different types of content across devices and publishing destinations. These ideas remain future-facing rather than confirmed features for a particular WordPress release.
For businesses, the broader direction reinforces one of WordPress’s longstanding strengths: ownership and portability of content. As the Data Liberation project develops, easier migrations and greater interoperability could reduce dependence on individual platforms or hosting environments and give organisations more flexibility over where and how their content is managed.
Usability, Accessibility and Internationalisation
- Accessibility Improvements:
Accessibility remains an ongoing priority for WordPress Core and Gutenberg. WordPress 7.1 introduced improvements across administration screens, media management and the block editor, including better focus behaviour, clearer labels, improved screen reader support and a new accessible tooltip mechanism. - WCAG 2.2 Alignment:
New and updated WordPress interfaces continue to be reviewed with accessibility standards in mind. WordPress has committed to meeting WCAG 2.2 Level AA for new and updated code, helping ensure that future interfaces work more effectively with keyboards, screen readers and other assistive technologies. - Internationalisation and Translation:
WordPress continues to support a global community through its established internationalisation and translation systems. Contributors can translate WordPress Core and related projects into more than 100 languages, while developers have access to established APIs and standards for making themes and plugins translation-ready. - Ongoing Testing and Community Feedback:
Usability and accessibility improvements are developed through testing, contributor feedback and dedicated WordPress teams. Beta and release candidate testing provides opportunities to identify problems before major releases reach production websites, while accessibility reviews help evaluate new and updated interfaces throughout development.
For businesses and developers, these ongoing improvements reinforce the importance of testing websites for accessibility, usability and localisation rather than assuming that a new WordPress release automatically addresses every requirement. WordPress Core provides an increasingly capable foundation, but themes, plugins and custom development also play an important role in the final user experience.
WordPress Security Hardening in 2026 and Beyond
Security remains an ongoing priority for WordPress Core, with improvements arriving through major releases, dedicated security updates and longer-term work by the WordPress Security Team. Rather than relying on a single collection of security features in WordPress 7.0, the project continues to strengthen different areas of Core as vulnerabilities and new risks are identified.
Safer User Registration Defaults:
WordPress 7.0 introduced a security improvement to user registration settings by removing the Administrator and Editor roles from the default-role selector. Site Health can also warn administrators where one of these higher-privilege roles was previously configured as the default, helping reduce the risk of accidentally granting excessive permissions to new users.Improved Security Release Process:
The WordPress Core Security Initiative is working towards a tighter and more automated security release process. This includes improved end-to-end testing designed to help security fixes ship more reliably and predictably when vulnerabilities need to be addressed.Reducing the Security Backlog:
Another priority is working through outstanding vulnerability reports and known security issues. Additional contributors and resources are being directed towards reviewing and resolving reports, with the longer-term goal of reducing the backlog of open security findings.AI-Assisted Vulnerability Detection:
WordPress is also exploring AI-assisted scanning and security tooling to help identify potential vulnerabilities before they can be exploited. This is intended to complement, rather than replace, traditional security research, testing and responsible vulnerability disclosure.Responsible Vulnerability Disclosure:
Security researchers are encouraged to report potential WordPress Core vulnerabilities privately through the project’s official disclosure process. This gives the WordPress Security Team an opportunity to investigate and coordinate fixes before technical details become public and potentially expose websites to unnecessary risk.
For businesses and developers, these developments reinforce the importance of keeping WordPress Core, themes and plugins updated. Security hardening is an ongoing process rather than something delivered by a single major release, and maintenance or security updates can arrive between scheduled feature releases when vulnerabilities need to be addressed.
PHP Version Support and WordPress Hosting Best Practices
Keeping the server environment up to date is an important part of maintaining WordPress performance, compatibility and security. WordPress continues to support some older PHP versions for backward compatibility, but the minimum version that technically works should not be confused with the version recommended for a modern production website.
PHP Requirements for WordPress 7.x:
WordPress 7.0 raised the minimum supported PHP version to 7.4, dropping support for PHP 7.2 and 7.3. WordPress 7.1 retains the same PHP 7.4 minimum. However, WordPress currently recommends PHP 8.3 or greater for better security and performance.Use a Supported PHP Release:
Although WordPress can continue to run on some older PHP versions, website owners should avoid PHP releases that have reached end of life and no longer receive upstream security updates. Hosting environments should therefore be reviewed regularly and moved to an actively maintained PHP version where theme and plugin compatibility allows.PHP Compatibility Testing:
Developers should test themes, plugins and custom functionality against newer PHP releases before upgrading production websites. Deprecated functions, stricter type handling and other PHP changes can expose compatibility problems in older or poorly maintained code even when WordPress Core itself supports the PHP version.Modern Hosting Environment:
WordPress currently recommends PHP 8.3 or greater, MariaDB 10.11 or MySQL 8.0 or greater, together with HTTPS. Apache or Nginx are recommended server options, although WordPress can run on other compatible web server configurations.Server-Level Performance and Security:
Features such as PHP OPcache, appropriate file permissions, page and object caching, HTTPS and properly configured server resources can all contribute to a faster and more secure WordPress installation. The exact configuration should be tailored to the website, hosting platform and expected traffic rather than treated as a universal WordPress Core requirement.
For businesses and agencies, the practical approach is to use a modern, actively supported PHP version while testing compatibility before each major server upgrade. Running the oldest PHP version that WordPress technically supports may keep a site operational, but it is not the recommended strategy for security or long-term maintenance.
Latest Core Announcements and What’s Next for WordPress Users
With WordPress 7.1 released on 19 August 2026, attention is now turning towards WordPress 7.2, the third and final major WordPress release planned for the year. Development is already underway, with beta testing expected to begin in October and the final release currently scheduled for December.
WordPress 7.2 Release Schedule:
The current roadmap places WordPress 7.2 Beta 1 between 20 and 22 October 2026, followed by additional beta releases and three planned release candidates. The final WordPress 7.2 release is currently scheduled for 8–10 December. As with any development schedule, these dates may change as testing progresses.Watch the 7.2 Roadmap:
Not every feature explored during development is guaranteed to reach the final release. WordPress 7.1 demonstrated this with features such as real-time collaboration being deferred for further work. Developers and agencies should therefore follow beta releases, developer notes and the eventual WordPress 7.2 Field Guide to see which changes are actually ready for Core.Performance, Accessibility and Security Remain Priorities:
Recent releases have delivered significant improvements across accessibility, media processing, administration interfaces, developer APIs and performance. Security work is also continuing through the newly announced Core Security Initiative, which focuses on improving the security release process, reducing the backlog of reported vulnerabilities and exploring AI-assisted vulnerability detection.Prepare Before Major Updates:
Before deploying a major WordPress release, create a reliable backup and test important themes, plugins and custom functionality in a staging environment. Developers and agencies can also test beta and release candidate builds ahead of time to identify compatibility problems before the final release reaches production websites.Follow Official WordPress Development Updates:
Release schedules, developer notes, testing calls, bug scrubs and Core development discussions are published through Make WordPress Core. Following these official updates is one of the best ways to distinguish confirmed changes from experimental features that may be delayed, altered or removed before release.
For businesses and website owners, the WordPress roadmap is best viewed as an evolving direction rather than a fixed list of promised features. WordPress 7.0 and 7.1 have already introduced substantial changes in 2026, while WordPress 7.2 and longer-term projects point towards continued improvements in editing, performance, accessibility, collaboration, AI infrastructure and platform flexibility.
Explore WordPress: Additional Resources and Supporting Guides
WordPress Field Guides:
WordPress Field Guides bring together the major technical changes included in each Core release, with links to individual developer notes covering new APIs, deprecated functionality and compatibility considerations. They are particularly useful for developers and agencies preparing for a major WordPress update.WordPress Developer Blog:
The WordPress Developer Blog provides practical articles covering block development, themes, APIs, performance and other changes across the WordPress ecosystem. It can help developers understand how new Core capabilities can be applied in real-world projects.WordPress Playground:
WordPress Playground lets you run WordPress quickly in a browser without setting up a traditional server environment. It can be useful for experimenting with WordPress versions, themes and plugins, testing code and exploring new functionality without making changes to a live website.Make WordPress Core:
For the latest roadmap information, release schedules and development discussions, Make WordPress Core is one of the most important resources to follow. It publishes development updates, meeting agendas, testing calls, Field Guides and release-specific technical information.WordPress Plugin Directory:
When Core does not provide a particular feature, the official WordPress Plugin Directory provides thousands of extensions covering areas such as ecommerce, SEO, security, forms, accessibility and workflow automation. Always check compatibility, update history and support information before installing a plugin.
Together, these resources provide a reliable way to follow WordPress development, test upcoming changes and understand how new Core features may affect your website, themes and plugins.
