WordPress 7.0 was released on 20 May 2026, followed by version 7.1 on 19 August 2026. The updates bring an AI Client in core, a reworked dashboard and new blocks. For PHP, the rule is: at least 7.4, with 8.3 or newer recommended. This guide explains what changes for WooCommerce shops and how to plan the update properly.
Overview: What's New in WordPress 7.0?
The official release announcement describes WordPress 7.0 as laying the foundation for AI across the WordPress experience. The key changes from 7.0 and 7.1 at a glance:
AI Client in Core
WordPress can communicate with generative AI models, with connections managed centrally in the dashboard.
PHP 7.4 to 8.5
PHP 7.2 and 7.3 are dropped, PHP 8.3 or newer is recommended.
Dashboard and Blocks
Reworked dashboard, new blocks for breadcrumbs and icons, custom CSS per block.
Media and Display: Less Server Load
For online shops with many product images, the changes to media handling are the most relevant:
- Image processing in the browser (7.1): Compression, resizing and thumbnail generation run in the browser instead of on the server
- New image formats (7.1): Native support for AVIF, HEIC and HDR gain maps
- Responsive settings (7.1): In addition to hiding and showing blocks per device, blocks can now be styled per screen size without custom CSS
- Many detailed fixes (7.0): According to the release announcement, more than 420 enhancements and fixes
For WooCommerce shops this means: image uploads put less load on the server, and modern image formats help keep product pages lean, which supports SEO and Core Web Vitals.
How an update affects load times depends on hosting, theme and plugins. Measure TTFB and LCP before and after the update on staging instead of relying on general claims.
PHP: 7.4 Minimum, 8.3 Recommended
With WordPress 7.0, PHP 7.4 is the minimum version and support for PHP 7.2 and 7.3 is dropped. WordPress.org recommends PHP 8.3 or newer. Older versions still run but no longer receive security updates.
| PHP Version | WordPress 7.x | Security updates until | Recommendation |
|---|---|---|---|
| PHP 7.2 / 7.3 | Not supported | Ended | Upgrade required |
| PHP 7.4 / 8.0 / 8.1 | Runs | Ended | Upgrade urgently |
| PHP 8.2 | Runs | 31 Dec 2026 | Plan the switch |
| PHP 8.3 | Recommended | 31 Dec 2027 | Recommended |
| PHP 8.4 | Runs | 31 Dec 2028 | Suitable |
| PHP 8.5 | Runs | 31 Dec 2029 | Suitable |
What does this mean for you? If your shop still runs on PHP 8.1 or older, the runtime receives no more security updates. Plan the switch to PHP 8.3 or newer together with the WordPress update. With most hosting plans, the PHP version can be changed in the control panel.
Not every plugin and theme is compatible with newer PHP versions. Before switching: test plugins and theme against the target version on staging or check with the developer. Outdated extensions can cause errors after the switch.
Why PHP 8.3 or Newer
Moving to a current PHP version pays off regardless of WordPress:
- Longer security updates: PHP 8.3 receives security updates until 31 Dec 2027, PHP 8.4 until 31 Dec 2028
- Predictability: Security updates for PHP 8.2 end on 31 Dec 2026
- Modern language features: Typed class constants and further additions for maintainable code
- WordPress.org recommendation: The official requirements name PHP 8.3 or newer
Gutenberg Phase 3: Collaboration
According to the official roadmap, Phase 3 of the Gutenberg project is currently underway. It focuses on collaborative editing and workflows. Part of this has already arrived in 7.0 and 7.1:
- Visual revision comparison (7.0): Scrub through older versions and see changes at a glance
- Notes with rich text and mentions (7.1): Leave feedback directly on the content and loop in the right people
- Unified editor (7.1): The post editor is fully iframed for all themes, matching the Site Editor
- Real-time collaboration: A stated goal of Phase 3, not yet fully in core
Especially relevant for WooCommerce shops: product and category texts can be coordinated in the team via notes and revisions without losing track of changes.
WooCommerce and WordPress 7.0
WooCommerce and its extensions are developed independently of WordPress core. What WooCommerce shop operators should watch out for when updating:
Ensuring Compatibility
- Bring WooCommerce to the current version
- Compare the "Tested up to" value of every extension with the WordPress version
- Test payment methods and shipping integrations on staging
- Check the theme for compatibility with WordPress 7.x
- Set up a staging environment for the test update
AI Client and Abilities API
The biggest technical change in 7.0 concerns AI. For shops, it matters what is in core and what is not:
- AI Client in core: A unified interface through which WordPress communicates with generative AI models
- Abilities API: Describes what a site can do and was extended in 7.1 with validation and shared discovery
- Official AI plugin: Image editing, titles, excerpts and alt text run through a separate plugin, not through core
- Use in the shop: Whether AI supports product texts or alt text is a deliberate decision. We integrate AI tools with an approval step and a privacy review
This is what your online shop could look like:
Outdoor Equipment
Migration and Update Strategy
A major update such as WordPress 7.x should not be rushed. The recommended approach:
- Create backup: Complete backup (files + database) before any changes
- Check PHP version: Determine the current version; 8.3 or newer is recommended, at least 7.4
- Staging environment: Create copy of shop on test server
- Update plugins: Bring all plugins to latest version
- Perform test update: Install the current 7.1.x version on staging
- Function test: Click through all shop functions (checkout, payment, etc.)
- Measure performance: Compare load times before/after
- Live update: Update production after successful test
- Activate monitoring: Increased vigilance after update
Updates before the weekend are risky. If something goes wrong, nobody may be available. Plan updates for Tuesday or Wednesday morning – time to react, support available.
Common Problems and Solutions
Plugin Incompatibility
A common problem with major updates. Solutions:
- Look for plugin alternatives: There are often more modern, compatible alternatives
- Contact the developer: Ask whether an update is planned
- Deactivate the plugin: Temporarily deactivate until an update is available
- Custom adaptation: For essential plugins, commission an individual adaptation
Theme Problems
Outdated themes can show display errors after the update:
- Update the theme: Get the latest version from the developer
- Use a child theme: Customizations in the child theme are protected from update losses
- Migrate to a block theme: Move classic themes to modern block themes
- Check custom themes: For individual themes, clarify compatibility with the developer
Timeline: Releases and Maintenance
WordPress 7.0 has been released, and the 7.1 series is already receiving maintenance releases. The dates so far:
- WordPress 7.0: 20 May 2026
- WordPress 7.1: 19 August 2026
- WordPress 7.1.1: 17 September 2026
- WordPress 7.1.2: 22 September 2026
Our recommendation: According to WordPress.org, only the most recent release in the 7.1 series is actively maintained. Apply maintenance releases promptly, first on staging and then in the live shop.
Checklist: Updating to WordPress 7.x
- Current PHP version checked (8.3 or newer recommended, at least 7.4)
- Complete backup created (files + database)
- All plugins updated to latest version
- Plugin compatibility with the target version checked
- Theme compatibility checked
- Staging environment set up
- WooCommerce and extensions updated
- Payment methods tested after update
- Performance baseline measured (for comparison after update)
- Update time window planned (not Friday!)
Promptly, but planned. According to WordPress.org, only the most recent release in the 7.1 series is actively maintained. Older versions no longer receive regular fixes. We recommend preparing the update on a staging environment and then applying it in a quiet time window.
WordPress 7.x runs from PHP 7.4, but 8.3 or newer is recommended. If your host offers no current version, request an upgrade or consider switching. We offer WordPress hosting with current PHP versions.
With proper preparation (backup, staging test, plugin check), the risk is minimal. Typical problems arise from outdated plugins or themes – these should be updated before the upgrade.
Not necessarily. A first indicator is the "Tested up to" value in the plugin directory. Reliable, however, is only a test on staging with your real data, because combinations of plugins and theme usually behave differently than each plugin on its own.
The update itself takes only a few minutes. However, preparation (backup, staging, tests) can take several hours to days – depending on the complexity of the shop and number of plugins.
Usually yes. Security updates for PHP 8.2 end on 31 Dec 2026, while PHP 8.3 is supported until 31 Dec 2027. Switching early spreads the risk: if a problem occurs, it can be clearly attributed to the PHP change.
Well Prepared for the Update
WordPress 7.0 and 7.1 bring noticeable changes, from the AI Client to image processing in the browser. For shops, careful preparation matters most: a current PHP version, tested extensions and an update process via staging.
We support you with WordPress and WooCommerce (WooCommerce agency) updates to the current 7.x version – from compatibility check to go-live. Contact us for consultation.
This article is based on the official release announcements from WordPress.org and the support periods published by php.net. How much an update improves speed depends on hosting, database and plugins in use and can only be measured in your own shop. As of: September 2026.