WordPress 7.0 “Armstrong” shipped on May 20, and it is the biggest WordPress release in years. New admin interface, AI built into core, browser-side image processing, and a PHP version cutoff that will leave some sites behind. Here is what actually changed, what it means for your site, and what to check before you hit the update button.
The admin interface got its first real overhaul in over a decade
The Posts, Pages, and Media screens in wp-admin have used the same basic table layout since roughly 2013. WordPress 7.0 replaces that with DataViews, a React-based interface that supports grid and table layouts, client-side filtering and sorting without page reloads, and inline bulk editing.
If you spend time in the WordPress admin managing content, this is the most immediately visible change. The new interface is faster, more flexible, and brings the admin closer to the block editor’s design language. There is also a new default color scheme with better typography and contrast, and a Command Palette (Cmd+K on Mac, Ctrl+K on Windows) that lets you jump to any admin screen without clicking through menus.
The trade-off: if you use plugins that add custom columns, filters, or bulk actions to the Posts or Pages screen, they may not render correctly until those plugins ship DataViews-compatible updates. The old WP_List_Table API that those customizations relied on is being phased out. Check your plugins before updating.
AI is now built into WordPress core (but it is opt-in)
WordPress 7.0 ships with a native AI Client and a Connectors API that standardize how themes and plugins interact with AI models. Three providers are supported out of the box: Anthropic (Claude), Google (Gemini), and OpenAI (ChatGPT). Configuration happens under a new Settings > Connectors screen in wp-admin.
The important detail: none of this is active by default. WordPress does not send any data to any AI service unless a site administrator explicitly connects a provider and enters an API key. If you never visit the Connectors screen, your site behaves exactly as it did on 6.9.
For site owners who do want AI features – content drafting assistance, automated image alt text, content summaries – the built-in infrastructure means you no longer need a separate plugin for each provider. Plugins can now use a single standardized API and let you choose which provider backs it.
One thing to watch: security researchers flagged on launch day that AI API keys entered in wp-admin are stored in the database and exposed in the browser’s autocomplete. If you connect an AI provider, treat those credentials like any other sensitive key – use a dedicated API key with the minimum permissions required, and rotate it periodically. If you want to disable the AI infrastructure entirely, add define('WP_AI_SUPPORT', false); to your wp-config.php.
Your browser now handles image processing
WordPress has always processed images on the server. When you upload a photo, the server generates thumbnails and intermediate sizes. This works, but it puts CPU load on the hosting server – especially on shared hosting where hundreds of accounts share the same resources.
WordPress 7.0 shifts this work to the browser using wasm-vips, a WebAssembly port of the libvips image processing library. When you upload an image, your browser resizes, compresses, and generates the required image sizes before sending them to the server. The result is significantly less CPU usage on the server during uploads and faster upload times for the user.
If the browser does not support WebAssembly (rare in 2026, but possible on very old devices), WordPress silently falls back to server-side processing. There is no configuration needed.
From a hosting perspective, this is a meaningful improvement for shared hosting environments. Image processing is one of the heavier operations WordPress performs on the server, and offloading it to the client means less resource contention during peak upload periods.
PHP 7.2 and 7.3 are officially dropped
WordPress 7.0 requires PHP 7.4 as the minimum and recommends PHP 8.3 or newer for best performance. If your site runs PHP 7.2 or 7.3, WordPress will not offer the 7.0 auto-update, and manual updates will be blocked until you upgrade PHP.
This is the change most likely to catch site owners off guard. When WordPress announced the deprecation in January, PHP 7.2 and 7.3 together accounted for about 3.8% of monitored WordPress installations. That is a small percentage globally, but it still represents thousands of sites that need to update their PHP version before they can run WordPress 7.0.
Sites stuck on old PHP will stay on the WordPress 6.9 branch. WordPress has historically backported security fixes to older branches, but this is described as a courtesy rather than a commitment. The practical advice is to upgrade PHP sooner rather than later.
On CanSpace shared hosting, PHP 8.1 through 8.4 are all available, and you can switch your site’s PHP version through cPanel’s MultiPHP Manager in under a minute. If you are not sure which version your site is running, check the MultiPHP Manager screen in cPanel, or open WordPress’s Site Health tool (Tools > Site Health > Info > Server) where it is listed under “PHP version.”
What got pulled: real-time collaboration
WordPress 7.0 was originally supposed to ship with real-time collaboration – the ability for multiple users to edit the same post simultaneously, Google Docs-style. The feature was pulled on May 8, twelve days before launch, after the development team found recurring bugs through fuzz testing and decided it was not stable enough to ship.
This was positioned as the flagship feature of WordPress’s Phase 3 (Collaboration) roadmap, and the decision to pull it was the right call. The WordPress community broadly praised the team for choosing stability over a headline feature. Real-time collaboration is now targeted for WordPress 7.1, expected in August 2026.
New blocks and design tools
Beyond the headline features, WordPress 7.0 adds several practical improvements worth knowing about:
A new Breadcrumbs block generates breadcrumb trails automatically based on your site’s page hierarchy or taxonomy – no plugin required. An Icons block gives access to the full WordPress icon library, searchable by name, with resize and recolor options. The Gallery block’s lightbox now functions as a slideshow (navigate between images without closing), Cover blocks support video backgrounds from YouTube and Vimeo, and you can now apply custom CSS to individual blocks through a new sidebar option.
The visual revisions system also got an upgrade: you can now visually compare two revisions side by side using a slider, with color-coded indicators showing what changed, what was added, and what was removed.
Before you hit “Update”
WordPress 7.0 is a major release. If your site is critical to your business, take these steps before updating:
Check your PHP version. You need PHP 7.4 at minimum. PHP 8.3 is recommended. If you are still on 7.2 or 7.3, upgrade PHP first – WordPress will block the update until you do.
Back up everything. Full file and database backup before any major update. If your hosting includes nightly backups, make sure you have a recent one. Take a manual backup if you want to be safe.
Update your plugins and theme first. Major WordPress releases often require plugin compatibility updates. WooCommerce (10.4.2+), Yoast SEO (26.6+), and Elementor (3.24+) have all shipped WordPress 7.0 compatibility updates already. Update these and any other plugins before updating core.
Check plugin compatibility. Plugins that add custom columns, filters, or actions to admin screens may need updates for the DataViews change. If a plugin has not been updated in the past few months, check its changelog or support forum.
Consider waiting for 7.0.1. The first minor release typically arrives 2-4 weeks after a major release and addresses issues found after launch. If your site is mission-critical and you are not in a rush, waiting for 7.0.1 is reasonable.
The bottom line
WordPress 7.0 is the most substantial WordPress release in years, with 875+ contributors delivering 420+ enhancements. The admin overhaul, browser-side image processing, and PHP version cleanup are genuine improvements that affect how you manage your site day to day. The AI integration is thoughtfully implemented as an opt-in infrastructure layer rather than something that activates without your knowledge.
Update your plugins now, verify your PHP version, take a backup, and update when you are ready. If you have been putting off a PHP upgrade, WordPress just gave you a deadline.
This article is on a hosting provider’s blog. Full disclosure: we’re CanSpace, and we host a lot of WordPress sites on Canadian servers. Everything discussed above – PHP version management, server-side processing loads, plugin compatibility, nightly backups – is part of what we handle for our hosting clients as part of our managed service.
If you are looking at WordPress hosting options, our WordPress hosting plans include all of the PHP versions WordPress 7.0 supports, nightly backups, and Canadian-staffed support. Our full hosting plans page has the feature breakdown, and our why-Canadian explainer covers the data residency angle. Or reach out directly if you have questions about upgrading.
