WordPress 7.1 Beta 4 Checklist: What to Verify Before Updating

WordPress 7.1 Beta 4 arrived on 29 July 2026 and closed the beta cycle. The build carries more than 114 fixes against the previous release candidate, split between the block editor and core. With release candidates running from 5 August to 18 August and a planned launch on 19 August at WordCamp US, the feature set is effectively locked. That leaves roughly three weeks for site owners, developers, and agencies to test what the new version actually does before it lands on every dashboard that opts into major updates.

This guide walks through the timing, the headline changes in WordPress 7.1, and a practical five-point checklist for preparing a production site for the update. It is written for website owners who manage their own installs, developers maintaining client builds, and hosting customers who want a calm upgrade window rather than a fire drill.

Key Takeaways

• Beta 4 is the final beta of the cycle, with 114 fixes shipped across core and the editor.
• WordPress 7.1 is scheduled to ship on 19 August 2026 at WordCamp US.
• Two features deserve real attention: Notes (inline @mentions and rich comments) and per-block responsive styling.
• Beta code belongs on staging or local installs, never on a live site.
• Most update failures trace back to plugins, themes, and PHP versions rather than WordPress core itself.

Where the 7.1 Cycle Stands Now

Each beta in this cycle was a bug-fix release rather than a feature drop. Beta 4 finalised that pattern. Many of those fixes cluster around the Notes feature, including how comments stay anchored to the passage they refer to and how tagged users render in the editor.

The release window is short. Site owners who want to influence what gets fixed still have a narrow reporting window through the WordPress support forums and Trac.

What WordPress 7.1 Changes for Day-to-Day Work

Two features define the 7.1 release for most users. Notes is the first. For teams that previously exported drafts to email or shared documents for feedback, Notes removes a round trip.

Responsive styling is the second. Around those two flagships sit deeper styling controls, interactive styling refinements, a smoother media experience, and a more personalised admin interface.

Several media fixes from Beta 3 are also worth noting. Long animated GIF uploads no longer hang during processing. EXIF-rotated images now orient correctly. That illustrates an important point: features can still move between a beta announcement and the stable release, so anything you plan to build on should be reverified closer to launch.

Beta 4 vs Stable: What the Final Beta Means

The takeaway from the table is simple. Plugin and theme authors should treat the current build as the most reliable reference for what the public release will look like.

Why You Should Not Run Beta Code on a Live Site

WordPress's own guidance is unambiguous: beta releases are for testing and development. The reasoning is operational rather than theoretical. The Make Core test team also publishes the areas needing attention in each release, which is the fastest way to know where to focus.

If you tested earlier betas, the official WordPress 7.1 beta 3 testing notes are still useful background for the cycle as a whole. Reviewing them helps explain which fixes landed when.

The Five Checks to Run Before the WordPress 7.1 Update

The update itself is a single click. The work is everything you do beforehand. The five checks below take roughly an afternoon and remove most of the surprises that turn a major release into an outage.

1. Test on a staging site first

A staging site is a working copy of your live site where you can apply the update without risk. Submit your forms. Open anything powered by a third-party plugin you did not build yourself. If the staging copy survives a normal session, the live site almost certainly will too.

2. Audit plugins and themes now

Core releases rarely break WordPress. Plugins break WordPress. Three weeks is enough time to email a developer and get an answer; it is not enough time on the day before launch.

3. Confirm your PHP version

WordPress 7.1 will run on whatever PHP version your host provides, but an older runtime narrows what works. Anything past the PHP project's official end-of-life date stops receiving security patches regardless of what your host advertises.

4. Verify your backup and your restore path

A backup you have never restored is a hope, not a safety net. Before 19 August, take a full backup and restore it somewhere clean. Confirm the database came with it. Time the restore. Ten minutes and forty minutes lead to very different decisions when the site is already down.

5. Decide on automatic updates for major releases

WordPress installs minor and security releases automatically by default. Turning auto-updates off is defensible for sites that rely on heavy plugin stacks or custom themes where a controlled upgrade window matters more than immediate access to new features.

How Site Owners Can Prepare in the Next Three Weeks

The remaining cycle is short, so prioritise by blast radius. The guide on how to restore WordPress core through a control panel is a useful safety net if a rollback becomes necessary after the update.

Frequently Asked Questions

When does WordPress 7.1 release?

WordPress 7.1 is scheduled to ship on 19 August 2026 at WordCamp US. Release candidates run from 5 August to 18 August, so any further fixes must clear that two-week stabilisation window. If a blocking issue surfaces, the date can shift, but as of Beta 4 the project is on track for the 19 August launch.

Is WordPress 7.1 Beta 4 safe to install on a live site?

No. WordPress explicitly states that beta releases are for testing and development, and the recommended path is a local install or a staging environment. Beta code can contain regressions that are difficult to roll back on production traffic, so it is worth waiting for the stable release unless you are an experienced tester reporting bugs back to the project.

What is the Notes feature in WordPress 7.1?

Notes is an inline commenting layer inside the block editor that supports @mentions and rich text formatting. It is designed for asynchronous feedback, so reviewers can leave comments on a draft without everyone needing to be in the editor at the same time. For teams that previously sent drafts out by email, it removes a round trip from the review process.

Do I need to update PHP before installing WordPress 7.1?

You do not strictly need to update PHP before installing 7.1, but running an outdated PHP version increases the risk of plugin or theme failures after the upgrade. Check your current version under Tools, then Site Health, then Info in the WordPress dashboard, and compare it against the PHP project's supported versions. Any version past its official end-of-life date no longer receives security patches.

How should I back up my WordPress site before a major update?

Take a full backup that includes both the filesystem and the database, then restore it in a separate environment to confirm the backup is actually usable. Time the restore so you know how long recovery takes. A backup that has never been tested is a hope, not a recovery plan, especially on the day a major release lands.

Conclusion

WordPress 7.1 Beta 4 is the final beta of the cycle, and the release timeline is tight. The most useful work you can do in the next three weeks is staged testing, a real plugin and theme audit, a PHP version check, a verified backup, and a deliberate decision about automatic major updates. None of those steps depend on beta code, so you can complete them now and still benefit when the stable release arrives.

For a deeper look at one of the smaller but useful improvements in this release, the article on accessibility in WordPress themes is worth reading alongside this checklist, since many of the styling refinements in 7.1 also make accessibility work easier. If you maintain client sites, the same five-point routine is a useful template to standardise across every install you manage before 19 August.