WordPress 7.1 Beta 1 shipped on 15 July 2026, and the Test team published Help Test WordPress 7.1 the same day. The headline feature is responsive styling in the block editor: set different font sizes, spacing and colours for tablet and mobile viewports without writing a line of CSS. The final release is scheduled for 19 August at WordCamp US, which gives the release cycle roughly five weeks of beta and RC testing.
This is a beta, so nothing here is guaranteed to land unchanged. But the shape of 7.1 is now on the record, and it is a styling release with a collaboration control bolted on the side.
Responsive styling without CSS in WordPress 7.1 Beta 1
The responsive controls extend the existing block supports. Instead of one font size, one padding value and one text colour, you get a viewport switcher in the editor sidebar: desktop, tablet, mobile. Change a value on tablet and it applies from the tablet breakpoint down, with the desktop value as the fallback. The generated CSS is still theme.json-shaped, so anything you set in the editor is inspectable and overridable in a child theme.
Two things matter for agencies. First, this reduces the number of one-off custom blocks built purely to get a different heading size on mobile. Second, it puts responsive decisions in the hands of whoever edits the page, which is either the point or the problem depending on your client.
What the beta does not do is expose arbitrary breakpoints. You get the viewports the editor defines. If your design system runs on custom media queries, you are still writing CSS.
Apply globally now has a review step
The “Apply globally” option no longer pushes every modified style into Global Styles in one click. It opens a review step where you choose which modified styles go global; the rest stay as local overrides on the block. That is a direct response to the way Global Styles edits could quietly rewrite a site’s typography, and it is the right call. Review the list before you commit, because the local overrides you leave behind are the ones that will confuse the next person to open the page.
Text shadow, Icon block controls and ThemeProvider
Global Styles gains text shadow support, which means shadow values live in theme.json alongside the rest of your typography tokens rather than in a custom stylesheet. The Icon block picks up flip and rotate controls, closing a gap that pushed people toward image blocks for simple arrow and chevron work.
On the developer side, ThemeProvider is exported as a public API from @wordpress/theme. If you build blocks or admin screens that need to consume theme tokens, that import is now a supported surface rather than something you reach into internals for. Treat it as stable from 7.1 and pin accordingly.
The Gutenberg plugin’s minimum WordPress version also moves to 6.9. If you run Gutenberg on top of an older core, you are now outside the supported matrix.
Collaboration you can switch off per post type
Real-time collaboration can be disabled per post type. That is the feature most technical leads will care about, because it is the one that decides whether 7.1 is a quiet upgrade or a support ticket generator.
Editorial teams on a shared post type generally want collaboration on. Structured content, product records, landing pages built by one person against a template: those are the post types where a second cursor in the room is noise. Being able to turn it off per post type means you can keep the feature where it earns its keep and leave the rest of the site alone.
Test this against your own post types before the 19 August release, not after. Collaboration touches autosaves and revisions, and that is where the edge cases live.
What to test before 19 August
The Test team’s call for testing is the place to start. A short list for a staging site:
- Set responsive font sizes and spacing on a page with a complex block pattern, then check the tablet and mobile breakpoints in a real browser, not just the editor preview.
- Use “Apply globally” on a modified style and confirm the review step lists what you expect. Check what stays local.
- Add a text shadow in Global Styles and confirm it survives a theme switch and a child theme override.
- Disable collaboration on one post type and confirm the editor still autosaves and revisions still generate.
- If you ship a plugin that imports from
@wordpress/theme, test against the new publicThemeProviderexport.
| Feature | Who it affects | Risk to check |
|---|---|---|
| Responsive styling per viewport | Editors, agencies | Generated CSS vs. child theme overrides |
| Apply globally review step | Site builders | Local overrides left behind |
| Global Styles text shadow | Theme developers | theme.json token conflicts |
| Icon block flip and rotate | Content teams | Low |
| Collaboration per post type | Technical leads | Autosaves and revisions |
| ThemeProvider public API | Plugin developers | Import paths and version pins |
If you are testing on managed infrastructure, take a staging clone rather than a live site. Kinsta and WP Engine both give you a disposable environment for exactly this kind of beta run, and you will want one you can throw away when the RC changes behaviour.
What it means
WordPress 7.1 is a styling release with a governance feature attached. Responsive styling without CSS removes a real reason to reach for page builders on simpler sites, and the review step on “Apply globally” patches a genuine footgun in Global Styles. The per-post-type collaboration switch is the sleeper: it is the difference between a feature you enable and a feature you tolerate.
We conclude that 7.1 is worth a staging run now, not the week of 19 August. The release cycle gives you five weeks. Use them.
FAQ
When does WordPress 7.1 leave beta?
The final release is scheduled for 19 August 2026 at WordCamp US. Beta 1 landed on 15 July, so expect release candidates in the weeks between.
Do I still need CSS for responsive design in 7.1?
For the viewports the editor exposes, no. Font size, spacing and colours can be set per tablet and mobile viewport in the block editor. Custom breakpoints and anything outside block supports still need CSS.
Can I turn off real-time collaboration?
Yes. WordPress 7.1 Beta 1 lets you disable collaboration per post type, so you can keep it for editorial work and switch it off for structured or single-author content.
