If you have been wondering what’s new in WordPress 7.0, the short version is: quite a lot, and most of it is good. The first major release of 2026 brings real upgrades to the editor, a cleaner admin area, and a handful of features people have been asking for since blocks first showed up. But there’s a catch sitting underneath the feature list, and it decides whether any of this lands on your site or just sits in your dashboard looking nice. We’ll get there.
First, the tour.
The editor upgrades everyone is talking about
The headline features in WordPress 7.0 live in the editor, and a few of them are the kind of thing site owners have wanted for years.
The biggest is responsive block visibility. You can now show or hide any block depending on whether someone is on a phone, tablet, or desktop, without writing a line of CSS. Want a full-size image on desktop and a compact version on mobile? Want to hide a chunky sidebar element on small screens? Select the block, open the new visibility options, and pick which devices to hide it on. Blocks with rules applied even get a little device icon in List View so you can see at a glance what’s hidden where. Page builders have done this for ages. Now it’s part of WordPress itself.
Revisions got a real upgrade too. WordPress has tracked revisions forever, but seeing what actually changed between two versions used to mean squinting. Now you can compare two revisions side by side with color-coded overlays. Green outlines mean a block was added, red means it was removed, and yellow means the settings changed. For text, added words show up green and underlined, removed words show up red with a strikethrough. The sidebar also lists which block settings changed, so you’re not guessing. If you have ever rolled back a page and hoped for the best, this is a quiet relief.
There’s also custom CSS for a single block. Before 7.0, restyling one button or adding a little breathing room around one image meant a workaround through Global Styles or a custom class. Now there’s a Custom CSS field right in the block’s Advanced panel, and whatever you type applies only to that one block. Nothing else on the page moves. The styling even travels with the block if you copy or move it.
WordPress 7.0 ships three new native blocks that used to require plugins. There’s an Icons block with a built-in icon library you can search, resize, and recolor, handy for feature lists and service cards (third-party sets like Font Awesome are not included yet, but support is slated for 7.1). There’s a Breadcrumbs block that builds a trail automatically based on your site structure, which helps visitors jump back up to a category page and doubles as an SEO signal Google uses in search snippets. And there’s a Headings block that pulls all six heading levels into one place so your structure stays intentional instead of accidental.
Rounding it out: mobile navigation overlays are no longer experimental and come with a guided setup and pre-built design options, block patterns now open in a simplified content-only mode that’s far less overwhelming when you just want to swap text and images, and the gallery lightbox finally has back and next buttons plus arrow-key support.
Good list. Now the catch.
What’s new in WordPress 7.0 if your site was built the old way
Here’s the part most recaps skip. Almost everything above lives in the modern block editor. If your site runs on a classic theme, or a page builder bolted onto an older setup, or a custom build that predates blocks, you can update to WordPress 7.0 and find that very little changes for you. The responsive visibility controls, the per-block CSS, the new blocks, the smarter pattern editing: they show up in the dashboard, but your site can’t actually reach most of them.
That’s not a knock on those sites. Plenty of them work fine. But it does mean the gap between “WordPress released this” and “I can use this” comes down entirely to how your site was built. A modern foundation gets the features the day they ship. An older one gets a version number and a slightly nicer admin screen.
Which brings us to the things you do get no matter how your site was made.
The WordPress 7.0 upgrades that work for everyone
Not all of 7.0 is gated behind the block editor, and a few of these are genuinely useful on any site.
The admin area got a refresh. Updated colors, cleaner typography, and smoother transitions between screens mean clicking from Posts to Settings to the editor no longer triggers a full page reload every time. If you publish often, that adds up fast. The Command Palette, previously stuck inside the block editor, now works everywhere in the admin. Press Cmd+K on a Mac or Ctrl+K on Windows to jump to any page, open a setting, or run a common action without reaching for the mouse. It’s optional and the regular menus all still work, so ignore it if keyboard shortcuts aren’t your thing.
The Font Library is the sleeper win for older sites. It now has a dedicated management page, and more importantly it works across every theme type: block, hybrid, and classic. Before 7.0 it was limited to block themes only. So if your site uses a classic theme, this is one modern feature you can finally use to manage and install fonts in one place.
There are also two changes worth knowing about even if you never touch them directly. New user accounts can no longer be assigned Administrator or Editor as a default role, which closes a quiet security hole that has bitten plenty of sites. And the minimum PHP version is now 7.4, with the core team recommending PHP 8.3 or 8.4 for performance and security. If your hosting is running something older, this release is a nudge to fix that.
Should you update to WordPress 7.0?
Yes, but on your terms. Back up your site first. If your site is busy or you can’t afford downtime, test the update on a staging copy before pushing it live. None of this is unique to 7.0; it’s just good practice for any major release. If your site is on managed hosting, a lot of this happens for you, including the backups and the safe rollout.
The harder question isn’t whether to update. It’s whether updating actually gets you anything. For a modern, block-based site, 7.0 hands you a stack of new tools the moment you click update. For an older build, it’s mostly housekeeping.
Getting the features instead of reading about them
If the responsive controls and per-block styling sound like exactly what you’ve been missing, the honest path is a current foundation, not a plugin patched onto an aging one. That’s the thinking behind how we build on Launchpad: sites built on the modern WordPress Full Site Editor, so when a release like 7.0 lands, the new features are simply there. No migration project, no plugin shopping, no “we’ll look at it next quarter.” The next release becomes something you use rather than something you read about.
WordPress 7.0 is a strong release. The question worth asking is whether your site is built to receive it.
Frequently asked questions about WordPress 7.0
You should, but back up your site first and test on a staging copy if your site is busy or mission-critical. Staying on an old version means missing security and performance improvements, even if the flashier editor features don’t apply to your build.
Most sites update cleanly. The main things to check are your PHP version (7.0 requires at least 7.4) and any custom blocks, since the editor now switches to a more stable iframed layout for newer blocks. A backup and a staging test before you update on a live site covers you.
Only if your site is built on the modern block editor. Features like responsive block visibility, per-block custom CSS, and the new Icons, Breadcrumbs, and Headings blocks all live in the editor. Sites on classic themes or older page-builder setups will see these in the dashboard but won’t be able to use most of them on the front end.
Yes. WordPress itself is free and open source. Your costs are hosting, any premium plugins or themes you choose, and whatever help you bring in to build and maintain the site.
