WordPress 7.0 “Armstrong” landed on May 20, 2026. It is the biggest core release in years, and the update button is probably sitting in your dashboard right now.
Here is what most people get wrong about a major version jump. The update itself is one click and takes about a minute. The update is not the risk. The risk is what your plugins and theme do after it. A major version can change how WordPress works under the hood, and anything that was relying on the old way can break the moment you upgrade.
So this WordPress 7.0 update guide covers two things. First, what actually changed in 7.0. Then the safe way to install it: back up, test on a copy, and only then go live. Do it in that order and a major update is a non-event. Skip it and you find out which plugin was holding your site together.
What Changed in WordPress 7.0
The headline features first, because they are genuinely good.
- AI built into core. WordPress 7.0 adds a built-in AI client, a single interface that lets plugins talk to AI models without each one reinventing the wheel. You connect a provider once in settings and plugins use it from there.
- New blocks and editor upgrades. There are new Heading, Breadcrumbs, and Icons blocks, the Cover block can use a video background, and the Grid block now adapts to screen size on its own.
- A proper Font Library. Fonts get a dedicated management page, so uploading and managing fonts across your site lives in one place instead of being scattered.
- A refreshed admin. A modernised dashboard look, a command palette you open with Ctrl+K or Cmd+K, and side-by-side visual revisions so you can compare changes with a slider.
Those features are not what breaks sites. Two quieter changes are the ones to actually watch.
- The minimum PHP version is now 7.4. If your site is still on an older version of PHP, WordPress 7.0 expects you to move up first. Most decent hosts are well past this, but cheap shared plans sometimes are not, so it is worth checking before you update.
- HTML5 script theme support was removed. This is a developer-level change, but the practical effect is simple: an older theme that leaned on the old behaviour can misbehave after the update. Themes that are actively maintained will already have handled it.
Neither of those is a reason to avoid 7.0. They are a reason to check a couple of things before you click update, which is exactly what the rest of this guide is for.
Is WordPress 7.0 Safe to Update? Major Updates vs Minor Ones
WordPress version numbers tell you how much changed. A move from 6.8 to 6.9 is a minor update, mostly fixes and small additions, and almost always safe to install straight away. A move to 7.0 is a major version. More changed, and more of it sits in the parts that plugins and themes depend on.
That is the whole source of update-day pain. WordPress core itself is tested heavily and rarely the problem. The problem is the plugin written three years ago that nobody has touched, or the custom theme built for an older way of doing things. When core changes and they have not kept up, something on your site stops working. A contact form goes quiet. A layout collapses. Checkout throws an error.
So is 7.0 safe to update? Yes, if you test it first. The more plugins you run, the higher the odds that one of them is not ready for 7.0 yet. That is not a reason to fear the update. It is the reason you test before you commit.
The Safe Way to Update to WordPress 7.0
This is the part that matters. Five steps, in order. Do not skip the order.
Step 1: Take a full backup first
Before you change anything, back up the whole site. All of it: the WordPress files, the uploads folder, the themes and plugins, and the full database. Keep that backup somewhere off the server.
This is your undo button. If the update goes sideways, a complete backup means you can put the site back exactly as it was in minutes. An update without a backup is a gamble, not a plan.
Step 2: Check compatibility before you touch update
Two quick checks save most update-day disasters.
- Confirm your PHP version is 7.4 or higher, since that is what 7.0 requires. Most hosts show this in the dashboard, and on a managed host it is handled for you.
- Update your plugins and theme to their latest versions first, while still on your current WordPress version. Plugin authors ship 7.0 compatibility in their own updates, so getting current first clears out a lot of the risk before you touch core.
If a plugin has not been updated in a long time and shows no sign of 7.0 support, treat that as a yellow flag to test carefully, or a prompt to find a maintained alternative.
Step 3: Test on a staging copy, not on your live site
This is the single step that turns a risky update into a safe one. A staging site is a private copy of your live site that the public never sees. You run the update there first, break things there if they are going to break, and your real site keeps serving visitors the whole time.
Never run a major update on production and hope. Run it on the copy.
Step 4: Update on staging, then click through everything
On the staging copy, run the WordPress 7.0 update, then actually use the site like a visitor would. Check:
- Your key pages load and look right.
- The menu and internal links work.
- Contact forms send and arrive.
- Logins work for you and your team.
- If you run a store, the cart and checkout work end to end.
If something is broken, you found it on the copy, with no visitor affected and no pressure. Fix it on staging, or hold off and wait for the plugin author to ship a fix.
Step 5: Only then push it live
Once the staging copy is clean and everything works, you are ready. Take one more fresh backup of the live site, run the update on production, and watch the site for the rest of the day. Because you already proved it on staging, this last step is a formality rather than a leap of faith.
What to Do If Something Breaks Anyway
If you skipped staging and the live site broke, do not start editing files in a panic. Restore the backup you took in Step 1. That puts the site back to its working state, and then you can move to staging and do it properly. This is exactly why Step 1 is not optional.
WordPress 7.0 Update FAQ
Is WordPress 7.0 safe to update?
Yes, if you test it first. WordPress 7.0 core is stable, but a major version update can break plugins or themes that have not kept up. The safe approach is to run the update on a staging copy first, confirm everything works, and then push live. Skipping staging means you find broken plugins on the live site instead of on a copy.
What are the known WordPress 7.0 problems to watch for?
Two specific changes cause the most issues. WordPress 7.0 requires PHP 7.4 or higher, so if your host is still on PHP 7.2 or 7.3 you will need to update that first. HTML5 script theme support was also removed, which can affect older unmaintained themes. Beyond those, the most common problem is a plugin that has not shipped 7.0 compatibility yet. Updating all plugins before upgrading core removes most of that risk.
What are the main new features in WordPress 7.0?
The headline additions are a built-in AI client that lets plugins share one AI provider connection, new blocks (Heading, Breadcrumbs, Icons) plus video background support in the Cover block, a dedicated Font Library for managing fonts site-wide, and a modernised admin with a command palette (Ctrl+K or Cmd+K) and side-by-side visual revision comparison.
Or Let Forge Handle the Whole Thing
Everything above is doable yourself. It also takes a backup routine, a staging environment, a careful eye on plugin compatibility, and the time to click through your whole site twice. On update day for a big release like 7.0, that is real work, and it is the kind of work that is easy to put off until something forces it.
Forge is managed WordPress hosting, which means version updates like 7.0 are our job, not yours.
Every Forge plan includes a staging environment, and our approach to a major update is to test it on a copy of your site before it ever touches production. With managed updates, we run that process for you: update on staging, check the site works, then push live. If a plugin is not ready for 7.0 yet, we catch it on the copy, not on your live store. And because we keep proactive monitoring on your site around the clock, if anything does go wrong, we tend to know about it before you do.
Your site also runs on its own dedicated server, never shared with other customers, so its performance and stability are not at the mercy of someone else’s bad update on the same box. That server is protected by BitNinja security, with all-in-one WordPress security and a built-in CDN, and your transactional email runs through ForgeMail so the messages your site sends actually arrive.
Forge pricing is flat: $39 to $209 a month depending on plan, with everything above included and no renewal increase. Every plan also comes with a free migration that we run end to end, so moving to managed hosting does not become its own update-day project.
A major version update should be boring. If you would rather not babysit the next one, that is what managed hosting is for.
See managed WordPress hosting plans
