This article is current as of 18 August 2026. At that date, WordPress 7.1 is scheduled for release on 19 August; it is not described here as an already published final release. Verify the calendar on the official WordPress Core 7.1 page.
Announced features
Beta and roadmap materials mention improvements for responsive styling and breakpoints, pseudo-state styling, media processing and editorial Notes, alongside API and developer changes. Consult the WordPress 7.1 Beta 1 announcement and the 7.1 roadmap.
New responsive controls can be useful for a custom site, but working components do not need to be rewritten automatically. A healthy theme adopts new features only when they simplify management or improve experience without adding incompatibility.
Why production should not update first
A major release can change editor, block and API behaviour. WordPress values backward compatibility, but every concrete site combines a different theme, plugins and infrastructure.
- verify PHP and hosting requirements;
- update the theme and extensions in staging;
- test frequently edited pages;
- check responsive behaviour on iOS and Android;
- measure LCP, INP and CLS;
- verify forms, payments, email and analytics;
- prepare a documented rollback.
The first 72 hours
- Watch the final announcement and known issues.
- Review PHP logs, browser console and uptime monitoring.
- Compare conversions and GA4 events with the baseline.
- Test real devices, including iOS Safari.
- Delay unrelated changes so errors remain diagnosable.
The best update is not the first installed; it is the one prepared, tested and observed. If WordPress 7.1 launches as scheduled, each website should still be evaluated individually before production deployment.