WordPress powers 43.5% of all websites globally and holds 62% of the CMS market. Every major WordPress release affects hundreds of millions of sites — and the transition to WordPress 7 represents the most significant architectural shift since WordPress 5.0 introduced the block editor in December 2018. This guide covers what WordPress 7 will bring, when it is expected, what it changes for themes and page builders, how it affects your hosting requirements, and an 8-point preparation checklist you can apply today so your UK WordPress site is ready on release day. Every preparation step is actionable now, regardless of your current WordPress version.
WordPress 7: the next major milestone · The Gutenberg roadmap context · Key expected features · Block themes: the new default · Performance improvements · What WordPress 7 means for your hosting · Your 8-point preparation checklist · Expected release timeline · Risks and common concerns · Frequently asked questions
The 6.x series has progressively built toward this moment. WordPress 6.5 introduced the Interactivity API. WordPress 6.6 refined pattern management and layout controls. WordPress 6.7 and 6.8 expanded block theme capabilities and Phase 3 (Collaboration) development.
WordPress 7.0 is expected to be the release that declares the block-based architecture fully mature and the default WordPress experience. For UK businesses running WordPress sites — simple brochure sites, content-heavy blogs, WooCommerce stores — WordPress 7 brings both opportunities and preparation requirements. The features are exciting; the hosting implications are practical and immediate.
WordPress development follows a four-phase roadmap for the block editor.
WordPress 7.0 sits at the boundary between Phase 2 (complete) and Phase 3 (maturing). It consolidates the 6.x cycle and establishes block-based architecture as the way to build with WordPress going forward.
Based on the Gutenberg roadmap, WordPress core team communications and the 6.x trajectory.
Site Editor, Global Styles, block patterns and template editing reach full production quality — no longer marked "beta" or "experimental". For UK businesses still on classic themes, WordPress 7 is the moment when block themes become the standard path.
The most user-facing new feature is expected to be real-time co-editing — multiple users editing the same post or page simultaneously, seeing each other's changes in real time (similar to Google Docs). In development through the Gutenberg plugin since 2024; expected to reach a shippable state by WordPress 7.
For UK businesses, content teams can work on pages together without the "Sorry, this post is currently being edited by another user" lock-out that has frustrated WordPress users for years. Marketing drafting landing pages, editorial reviewing blog posts, developers adjusting page layouts — all simultaneously.
The Interactivity API, introduced in WordPress 6.5, provides a standardised way to add client-side interactivity to blocks without requiring React or other JavaScript frameworks. Real-time search filtering, dynamic navigation, interactive UI elements — all using a lightweight declarative approach that does not add heavy JavaScript bundles.
In WordPress 7, this API is expected to be mature enough for theme and plugin developers to rely on as a stable foundation. Result: more interactive WordPress sites that are faster than sites built with traditional JavaScript-heavy page builders — because the Interactivity API is designed to minimise JavaScript payload.
Matt Mullenweg has highlighted data portability as a key WordPress project goal. WordPress 7 is expected to include significant improvements to the import/export system, making it easier to move content between WordPress installations, between WordPress and other platforms, and to back up in portable formats. Aligns with WordPress's open-source philosophy of user ownership of data.
The minimum PHP requirement is expected to rise, dropping support for PHP 7.4 and potentially PHP 8.0. PHP 7.4 has been end-of-life since November 2022 and has received no security patches for over three years.
Speculative loading, module-based script loading, lazy loading refinements, reduced JavaScript payload for the block editor. Cumulative gains on top of the 6.x series' improvements.
WordPress 7 is expected to make block themes the default and recommended approach for building WordPress sites. Classic themes continue to work (backward compatibility is a WordPress core principle), but new features, new default themes and the primary WordPress experience will all be oriented around block themes.
| Aspect | Classic themes | Block themes |
|---|---|---|
| Page layout | PHP template files | HTML block templates |
| Header/footer editing | Code or Customiser | Visual Site Editor |
| Global styling | CSS + Customiser | Global Styles UI (theme.json) |
| Template customisation | Child theme + PHP | Visual editor, no code |
| Page builder dependency | Often required (Elementor) | Built into WordPress core |
| Performance | Varies widely | Generally lighter (less JS) |
| Plugin compatibility | Mature ecosystem | Growing, some gaps remain |
Block theme adoption currently sits at approximately 15–25% of all WordPress sites — growing but still a minority. The majority of existing sites run classic themes like Astra, GeneratePress, OceanWP and Hello Elementor. The WordPress.org theme directory has been pushing block themes heavily, with most new theme submissions being block themes.
If you run a classic theme, your site will continue to work on WordPress 7. You will not be forced to switch. However, you will increasingly find that new WordPress features are designed for block themes and may not be available in classic theme contexts. Practical advice: keep your current theme for now, but plan your next redesign around a block theme.
If you run a page builder (Elementor, Bricks, WPBakery), it will continue to function. The major page builders are actively developing compatibility with WordPress 7 and the block editor. Elementor has been adding block editor integration features. The long-term trend is clear: WordPress's native editing capabilities are catching up to what page builders offer, and the performance advantage of native blocks is significant.
The WordPress Performance Team has made substantial progress through the 6.x series.
Pre-fetches pages users are likely to navigate to next — based on hover behaviour over navigation links. When the user clicks, the page appears to load instantly because the browser has already started fetching. Rolled out progressively through 6.x; expected to be refined in WordPress 7.
WordPress 7 is expected to shift more of its JavaScript to ES module format, enabling browsers to load scripts more efficiently — in parallel rather than sequentially. Directly improves INP (Interaction to Next Paint), the Core Web Vitals metric WordPress sites struggle with most.
The block editor's JavaScript payload has been progressively reduced through the 6.x series. WordPress 7 continues this, particularly for the front-end rendering of block-based content. Block themes already produce lighter output than page builder-generated content; WordPress 7 aims to widen that gap.
Currently, approximately 40–45% of WordPress sites pass all three Core Web Vitals (LCP, INP, CLS) — up from 25–30% in 2022. WordPress 7's combined performance improvements are expected to push this higher, particularly for sites using block themes and modern hosting. The gap between "optimised WordPress on quality hosting" and "default WordPress on budget hosting" will widen further.
Every WordPress major release has hosting implications. WordPress 7's changes are more significant than a typical minor version bump.
WordPress 7 is expected to require PHP 8.0 or 8.1 minimum, with PHP 8.2+ recommended for optimal performance and security. PHP 7.4 has been end-of-life since November 2022 and has received no security patches for over three years. If your current host still runs PHP 7.4, WordPress 7 will likely not function correctly — and even if it does, you are running on an insecure foundation.
The JIT (Just-In-Time) compiler in PHP 8.x delivers 5–20% better performance for WordPress workloads. Combined with WordPress 7's own improvements, the cumulative speed gain for sites on PHP 8.3 vs PHP 7.4 is substantial.
Block themes and the Collaboration features in WordPress 7 increase the complexity of database interactions — more dynamic rendering, more editor state management, more template queries. Redis object caching becomes even more valuable in this context, keeping frequently accessed data in memory and reducing database queries by 30–50% for dynamic pages.
smartxhosting.uk includes Redis on every WordPress plan, pre-installed. Enable via LiteSpeed Cache's Object tab or the Redis Object Cache plugin.
The Interactivity API, real-time Collaboration and expanded REST API endpoints all increase the attack surface available to malicious actors. Server-level protection via Imunify360 — with its ML-powered WAF, PHP Hardening and real-time malware scanning — becomes increasingly important as WordPress adds more interactive, API-driven functionality.
A major version update should never be applied directly to a live site. Staging environments let you test WordPress 7 — including plugin and theme compatibility — in an isolated copy before committing. Plesk WP Toolkit on smartxhosting.uk WordPress hosting provides one-click staging that clones your live site, lets you run the update, and shows you the result before anything goes live.
Every smartxhosting.uk WordPress plan already provides everything WordPress 7 will need:
Every item is actionable today, regardless of your current WordPress version.
Log in to your hosting panel and verify you are running PHP 8.2 or higher. If on PHP 7.4 or 8.0, upgrade now — do not wait. smartxhosting.uk supports PHP 8.1/8.2/8.3 with one-click switching in Plesk.
Check each plugin for PHP 8.2+ compatibility and recent update history. Plugins not updated in 12+ months are red flags. Remove plugins you are not actively using — each one is a potential security vulnerability (plugins account for 96–97% of all WordPress vulnerabilities).
Is it a classic theme or a block theme? If classic, check that the developer has confirmed WordPress 7 compatibility. If you are planning a redesign, start evaluating block themes now — Twenty Twenty-Five is the reference block theme from WordPress core.
Before any major update, ensure you have a complete backup of files and database. On smartxhosting.uk, daily backups are included, and Plesk WP Toolkit allows on-demand backups before updates.
Clone your live site to staging and apply the WordPress 7 update there first. Check every page, every form, every payment flow, every plugin. Plesk WP Toolkit creates staging environments in one click on smartxhosting.uk.
If you have not already, activate Redis. The increased database complexity of block themes and Collaboration features makes object caching more valuable than ever. Redis is pre-installed on all smartxhosting.uk WordPress plans.
Update all plugins and themes to their latest versions. Verify your SPF, DKIM and DMARC records are correct. Check your SSL certificate is valid and auto-renewing. Ensure Imunify360 (or equivalent WAF) is active. Check for open 2FA on admin accounts.
Does your current host support PHP 8.2+, Redis, NVMe SSD and staging environments? If not, the WordPress 7 transition is the ideal trigger to move to hosting that includes these features as standard. smartxhosting.uk offers free migration assistance for existing WordPress sites.
WordPress follows a time-based release cycle with roughly three major versions per year. The 6.x series has progressed through 6.5, 6.6, 6.7 and 6.8. If the pattern follows the 5.x-to-6.0 transition, WordPress 7.0 is expected in late 2025 or the first half of 2026.
WordPress does not pre-announce major version numbers far in advance, so the exact date will be confirmed closer to release. Follow wordpress.org/news for official announcements.
Best practice: do not apply WordPress 7.0 on the same day of release. Wait 2–4 weeks for the 7.0.1 / 7.0.2 patch releases and for plugin authors to issue compatibility updates.
Not every plugin will be updated in time for WordPress 7.0 release day. Major plugins (WooCommerce, Yoast, Rank Math, Elementor) are usually ready; smaller plugins may lag. Before updating WordPress 7, check each active plugin's "Tested up to" version and changelog.
Page builders (especially Elementor) rely on specific WordPress internals. Most major builders will issue WordPress 7 compatibility updates within 1–4 weeks of release. Avoid applying WordPress 7 until your page builder confirms compatibility.
Older classic themes (particularly custom or heavily modified ones) may encounter issues. Block themes built to current standards should work cleanly. Staging first catches this.
Major WordPress versions occasionally include database schema changes. A failed update mid-database-upgrade can leave the site in a broken state. A pre-update backup is the safety net. smartxhosting.uk daily backups plus Plesk WP Toolkit's on-demand backups give you two layers of protection.
Rare but possible. Test Core Web Vitals on staging after applying WordPress 7 and compare to pre-update scores.
When is WordPress 7 expected to be released?
WordPress follows a time-based release cycle with roughly three major versions per year. The 6.x series has progressed through 6.5, 6.6, 6.7 and 6.8. If the pattern follows the 5.x-to-6.0 transition, WordPress 7.0 is expected in late 2025 or the first half of 2026. The exact date will be confirmed closer to release via wordpress.org/news.
Will WordPress 7 break my existing site?
WordPress major releases are designed for backward compatibility, but some breaking changes are possible — particularly around PHP version requirements. If your site runs PHP 7.4 (end-of-life since November 2022), it is likely to be incompatible with WordPress 7. If your theme is a classic theme, it will still work but may not benefit from new block-based features. The safest approach is to test the update on a staging environment before applying to live. Plesk WP Toolkit on smartxhosting.uk makes this a one-click operation.
Do I need a new theme for WordPress 7?
No — classic themes continue to work. However, WordPress 7 is expected to make block themes the default paradigm. New features (Global Styles, Site Editor, template editing, block patterns) will be designed primarily for block themes. If you are currently on a classic theme, you do not need to switch immediately, but you will increasingly miss out on new capabilities. Consider evaluating block themes like Twenty Twenty-Five during your next redesign cycle.
What PHP version will WordPress 7 require?
WordPress has been gradually raising its PHP minimum. WordPress 6.x requires PHP 7.4 minimum but recommends 8.0 or higher. WordPress 7 is expected to require PHP 8.0 or 8.1 as the minimum, with PHP 8.2 or 8.3 recommended for optimal performance. The JIT compiler in PHP 8.x delivers 5–20% better performance for WordPress workloads. smartxhosting.uk supports PHP 8.1, 8.2 and 8.3 with one-click version switching.
Do I need to upgrade my hosting for WordPress 7?
If your current hosting supports PHP 8.2 or higher, provides Redis object caching, uses NVMe SSD, and includes staging environments for testing updates, you are ready for WordPress 7. If your host is still running PHP 7.4, uses SATA storage or does not offer staging, the upgrade to WordPress 7 is a good trigger to switch to modern hosting. smartxhosting.uk WordPress plans include all of these as standard.
What is Data Liberation?
A WordPress project priority focused on making it easier to move content in and out of WordPress — between installations, between WordPress and other platforms, and for backup in portable formats. WordPress 7 is expected to include improved import/export tooling supporting this goal.
Will page builders like Elementor still work with WordPress 7?
Yes. Elementor, Bricks and other major page builders actively develop WordPress compatibility. Expect compatibility updates within 1–4 weeks of WordPress 7 release. Test on staging before applying to production, and check the builder's changelog for "Tested up to: 7.0" confirmation.
How long should I wait before updating to WordPress 7?
Do not apply WordPress 7.0 on release day. Wait 2–4 weeks for the 7.0.1 / 7.0.2 patch releases and for major plugins/themes to issue compatibility updates. Always test on staging first. Plesk WP Toolkit's Smart Update feature adds automatic rollback if the update breaks the site.
What about the Collaboration features — do I need anything special?
Real-time collaboration requires a modern browser (Chrome, Firefox, Safari, Edge — all current versions). No special hosting configuration needed beyond what WordPress 7 requires generally (PHP 8.2+, adequate memory). Redis object caching improves collaboration performance because editor state is queried frequently.
Can I skip WordPress 6.x and go straight to 7?
Not ideal. WordPress upgrades are cumulative; going from 6.2 straight to 7.0 applies many schema changes in one transaction, increasing risk. Stay current through 6.x releases now; when 7.0 arrives, the jump is small.
Launch your WordPress site on smartxhosting.uk
UK hosting with the Plesk WordPress Toolkit, LiteSpeed Cache, Redis object caching, Imunify360 server-level security, free Let’s Encrypt SSL, free CDN and daily backups — from £2/month.
View WordPress hosting plans →