WordPress 7.0 Launches 20 May: Will It Break Your Site?
Most WordPress updates slip out quietly. Version 7.0 is not that. Scheduled for 20 May 2026, this is the biggest version number jump in years — and with RC3 now out, the countdown is real.
Published 9 May 2026.
What We Know About WordPress 7.0
The third Release Candidate (RC3) dropped this week, according to the official WordPress.org announcement. A Release Candidate is basically the near-final version — the developers believe it's ready, but they're still hunting for last-minute bugs before the public launch.
RC3 addresses 143+ issues found since RC2. That's not a small number. It tells you this release has had a complicated road.
Here's what caught my eye: Real-Time Collaboration — the feature that would let multiple people edit a page at the same time, like Google Docs inside WordPress — has been dropped from 7.0 entirely. It'll be reconsidered for WordPress 7.1. The WordPress team confirmed this directly in the RC3 announcement, noting that "because of this, this RC3 version is no longer considered a 'new Beta 1'."
So the headline feature is gone. What's left is still a major release, with full developer notes available for anyone who wants to dig into the specifics.
The final release date is 20 May 2026. That's 11 days away as you're reading this.
What's Still Unclear
Honestly, this is where it gets a bit thin. The source material confirms the release date, the RC3 milestone, and the Real-Time Collaboration cut — but doesn't detail which specific features made the final cut or what's most likely to cause compatibility problems with existing plugins and themes.
What should you actually be worried about? That's the real question here, and the answer is: we don't have a confirmed list yet.
What we do know from past major WordPress releases is that version number jumps often come with changes to how the block editor (Gutenberg) handles things — and that tends to be where conflicts show up first. Page builder plugins, custom theme templates, and anything that touches the editor are historically the first to show cracks after a big update.
No official documentation exists yet on which plugin categories are most at risk for 7.0 specifically.
What This Means For You Right Now
Do not update on 20 May.
That's the short version. Here's the longer one.
If you manage a client site — or run any site that earns money, takes bookings, or handles enquiries — wait at least two weeks after the 20 May release before updating. Let other people find the bugs first. That's not laziness. That's just sensible.
Here's what to do before the update eventually lands:
- Check your theme and page builder — if you're using something like Elementor, Divi, or a premium theme, go to their website or changelog and look for any 7.0 compatibility notes. If there's nothing, wait longer.
- Back up your site the day before you update — not a week before. The day before. Your host almost certainly has a one-click backup option.
- Test on a staging site first — a staging site is a private copy of your site where you can try updates without touching the live version. Most managed WordPress hosts offer this free.
- Update plugins before the core update — outdated plugins are the most common reason sites break after a WordPress update.
If your site does go down or slow to a crawl after the update, you want to know immediately — not when a client calls you. Uptrue monitors WordPress sites for downtime, slow response, and SSL issues around the clock, and alerts you the moment something goes wrong. Worth having set up before 20 May, not after.
Frequently Asked Questions
Should I update to WordPress 7.0 on release day? No. Unless you're running a test site, wait at least two weeks after 20 May 2026 to let any major compatibility issues surface and get patched by plugin and theme developers.
What was Real-Time Collaboration in WordPress 7.0? It was a planned feature that would let multiple people edit the same page at the same time — similar to how Google Docs works. It has been removed from the 7.0 release and will be reviewed for WordPress 7.1 instead.
How do I know if my plugins are compatible with WordPress 7.0? Check the plugin's page on WordPress.org or the developer's own website. Look for any update released around or after 20 May 2026 that mentions 7.0 compatibility.
What breaks most often after a major WordPress update? Page builders, custom themes, and plugins that modify the block editor (Gutenberg) are historically the most likely to show problems after a major version release.
How can I get warned if my site goes down after updating? Set up uptime monitoring before you update. Uptrue's site tracker checks your site continuously and alerts you straight away if it goes offline or starts responding slowly — so you're not the last to know.