WordPress 7.1 beta is now available for testing, and we have been running it on our test sites for the past week.

The official release is scheduled for August 19, 2026, timed with WordCamp US.

While WordPress 7.0 rebuilt the admin and introduced the AI Client, 7.1 turns to the editor. For the first time, you can design for tablets and phones, and style hover and focus states, without writing a line of CSS.

Let’s take a look at what’s coming in WordPress 7.1, with screenshots and examples of how each feature works.

TL;DR: What’s coming in WordPress 7.1

• Notes get a major upgrade with @mentions, the ability to add notes to specific text, support for multiple discussion threads, and rich formatting.
• Responsive styling lets you control how blocks look on tablets and phones, directly in the editor, without custom CSS.
• A new image editor and smarter media handling, including HEIC support and uploads pause if your connection drops, then continue when you are back online.
• New Tabs and Playlist blocks, plus the admin toolbar now stays visible while you work in the editor.

When Is WordPress 7.1 Coming Out?

WordPress 7.1 will be released on August 19, 2026, which is the final day of WordCamp US 2026. The date is still marked tentative on the official WordPress release schedule, so it could shift if testing uncovers a serious bug.

Before then, WordPress 7.1 will go through two release candidates, on August 5 and August 12. Those are near-final builds, so you will know exactly what is in the release by early August.

Collaborate Better With the Upgraded Notes

The Notes feature arrived in WordPress 6.9 as a simple way to leave comments on blocks. WordPress 7.1 will turn it into a proper feedback system.

The most useful addition is @mentions. Typing ‘@’ inside a note brings up a searchable list of collaborators to tag directly. This makes it much easier to direct feedback to the right person on your team.

Inline notes are new too. Instead of attaching a comment to an entire block, you can select a specific sentence or phrase and leave a note on just that text. The selection stays highlighted, so everyone can see exactly what the note refers to.

This removes a lot of guesswork. Previously, a note saying “please rephrase this” could apply to anything in a long paragraph. Now, it points at the exact words.

Other Notes improvements include:

• Multiple threads: More than one conversation can run on the same block, instead of folding every comment into a single thread.
• Text formatting: Notes now support bold, italic, code, links, and emoji.
• Show more / show less: Long notes collapse by default to keep the sidebar tidy.

These changes make Notes genuinely useful for teams, agencies, and multi-author blogs.

Responsive Styling Without Writing CSS

You can now define how a block looks at different screen sizes directly in the editor.

For example, a smaller font size for headings on mobile, or different spacing for tablets, without writing a single line of CSS.

When you switch the editor preview to Tablet or Mobile, any style change you make applies only to that screen size.

WordPress also shows a small badge in the block settings panel, so you always know which screen size you are styling.

It works on two levels. Responsive styles set in Global Styles apply to every instance of a block across your site. Styles set on a single block apply only to that page.

The editor canvas is also more flexible. Instead of being limited to the Desktop, Tablet, and Mobile preview presets, you can drag the canvas to any width and watch your blocks respond in real time.

In our testing, this felt natural very quickly. Theme developers can even define their own breakpoints in theme.json, so the preview widths can match the theme you’re actually using.

If you style one block and then decide you want that look everywhere, applying the change to Global Styles brings up a quick review step. You can choose exactly which modified styles to apply globally and keep the rest as local overrides.

Style Hover and Focus States for Buttons

Alongside responsive styling, WordPress 7.1 will introduce interactive state styling. A new ‘States’ dropdown lets you visually style how blocks respond to interaction.

The most common use case is buttons: you can now set a different background color for hover, focus, or active states and preview the change live in the editor.

Until now, changing a button’s hover color meant writing custom CSS, even though it’s a tiny change. Now, it’s a built-in design option.

New Tabs Block

WordPress 7.1 will add a Tabs block that many users have been asking for.

Tabs let you organize content into clickable panels instead of showing everything at once. They are great for product specifications, FAQs, or comparing options without making a page feel long.

Previously, you had to add tabbed content using a plugin. Just keep in mind that tabs you already built with a plugin will not convert to this core block automatically.

New Playlist Block

The second new block in WordPress 7.1 will be the Playlist block. It lets you add a collection of audio files to any post or page. You can also show your track’s title, artist, and cover art, plus a waveform graphic of the audio.

This is most useful for musicians, churches, educators, and anyone else who publishes audio. If you run a podcast with WordPress, then you can add a set of episodes to one player on a page.

Block Improvements in WordPress 7.1

Several existing blocks will get meaningful upgrades in this release:

• Background gradients and images work together: You can now layer a gradient over a background image in the Group block (and several other blocks) without the two conflicting. This is handy for keeping text readable over hero images.
• Text shadows: Themes can now set a text shadow through theme.json, either globally, on specific blocks, or on elements like links. For now it only works in theme.json, so there is no setting in the editor yet.
• Editable content inside the HTML block: The HTML block now supports editable nested blocks. This is especially useful when working with AI-generated layouts, which often arrive as custom HTML.
• Mark images as decorative: A new toggle on the Image block lets you mark purely decorative images so that screen readers skip them. This is an easy accessibility win, because decorative images with meaningless alt text are one of the most common accessibility mistakes.

• Smarter shortcode handling: Pasting or converting an embed shortcode now creates a proper Embed block instead of leaving raw shortcode text behind.
• Grid transforms: Columns and Gallery blocks can now transform into Grid layouts while preserving their content.
• Icon block upgrades: The Icon block, added in WordPress 7.0, now lets you flip and rotate icons. It also starts with a default icon instead of an empty placeholder, and the picker groups icons into collections so you can browse them more easily. Plugins and themes can now register their own icon sets, so expect branded icon libraries from your favorite plugins.

A New Image Editor in WordPress 7.1

WordPress 7.1 will replace the old inline cropping tool with a dedicated Media Editor modal.

The entry point stays familiar. You still click the Crop button on an Image block.

But instead of the cramped inline controls, a full editing modal opens with freeform cropping, aspect-ratio presets, flip and rotate controls, and metadata editing in one place.

The new editor also works with the Cover block, so you can crop a background image right where you use it.

This won’t replace a full photo editor. However, for the basic image editing most site owners actually do, it is a big usability win.

Smoother and Smarter Media Handling

 In WordPress 7.1, your web browser does most of the work of processing images before they are uploaded to your server. It resizes, compresses, and converts them, and creates the smaller thumbnail sizes that WordPress needs.

There are two benefits. Your server does much less work, which means fewer failed uploads on limited hosting plans. And WordPress can now handle more image formats, including HEIC, which is the default format on iPhones, plus UltraHDR, AVIF, and WebP. It can also convert animated GIFs into more efficient videos.

HEIC is the biggest change here. Until now, HEIC photos have been converted on the server, but only if your web host runs a recent enough version of ImageMagick, the software WordPress uses to process images. Some iPhone users had to convert HEIC to JPG before uploading.

With 7.1, your browser does the converting instead. This works fully in Chrome and Edge. Safari can convert iPhone photos, but the resizing and thumbnail creation still happen on your server. In Firefox, WordPress passes the whole job back to your server.

Uploads are also more reliable. If your internet connection drops mid-upload, the queue pauses and resumes automatically when you are back online. A progress indicator keeps you informed for batch uploads.

There are smaller everyday improvements too:

• Smarter galleries: A new dynamic Gallery mode can automatically pull in and sort media already attached to the current post.
• Attached images in the inserter: After you upload images to a post, they appear in a new ‘Attached images’ section, so you don’t have to dig through the whole Media Library.
• Infinite scrolling: The Media Library grid now loads more items automatically as you scroll. You can turn this off in your user profile.

Together, these changes mean fewer upload errors and less load on your server. That’s especially good news if you’re on a budget WordPress hosting plan.

The Admin Toolbar Now Stays Visible When Editing

WordPress 7.1 will make the admin toolbar stay visible in the Site Editor and the Block Editor, instead of disappearing when you start editing.

The toolbar itself is also getting a design cleanup as part of this change:

• A clear back button (chevron) replaces the confusing W logo that used to double as a back button.
• Your site icon now appears in the toolbar, and your profile avatar is a circle instead of a square.
• The old Dashicons icons are replaced with modern SVG icons.

The toolbar stays hidden in Distraction Free mode, so you still get a clean writing canvas.

A More Personal, More Navigable Admin

Beyond the toolbar, WordPress 7.1 will include a set of smaller admin improvements that add up.

Command Palette improvements: The Command Palette (Ctrl+K on Windows, Command+K on Mac) now groups results into Recent, matching, and Suggestions sections. Your recently used commands are saved to your preferences, so they persist across sessions.

Your admin color scheme in the Site Editor: The Site Editor now reflects your chosen admin color scheme instead of always using a fixed dark sidebar. This is a small thing, but it makes the whole admin area feel consistent.

A dedicated Identity section: Site identity settings like your title, tagline, logo, and site icon now live in their own clearly labeled Design » Identity section in the Site Editor. You no longer need to hunt through Settings and templates to update these basics.

On This Day widget: A new dashboard widget resurfaces what you published on this date in past years. It’s a fun nudge for long-running blogs, and useful for finding old content worth updating.

Change a comment’s parent: The Edit Comment screen will add an editable ‘In reply to’ control, so you can finally re-thread a comment that ended up under the wrong reply. It works within a single post, not across posts.

What Didn’t Make It Into WordPress 7.1?

We want to be upfront: real-time collaboration will not ship in WordPress 7.1. If you followed our WordPress 7.0 coverage, then you may remember that Google Docs-style real-time collaboration has been in development for a while.

The feature is enabled in the Gutenberg plugin, where multiple people can already edit the same post together.

However, the core team is still working through big decisions, including how collaboration data should be stored and whether to ship the full feature or just the underlying architecture first.

There is a dedicated community testing effort that will continue beyond the 7.1 cycle to get collaborative editing ready. Until it lands in core, you can add collaboration to the block editor with a plugin.

We think that caution is the right call. A collaboration feature that loses someone’s work would be far worse than a delayed one.

Similarly, support for Unicode (non-Latin) email addresses was originally planned for 7.1 but was pulled during beta testing. That work will continue in a community plugin for broader compatibility and security testing before it lands in core.

Under the Hood (Developer & Performance Updates)

WordPress 7.1 will also ship several technical improvements for developers and site performance:

• The post editor is always iframed: In WordPress 7.1, the editing area always runs inside an iframe. Until now, WordPress turned this off if the page contained a block built on an older version of the Block API This means the editing canvas is isolated from admin styles in every case. Blocks using Block API v2 or lower should be updated to v3 for compatibility, and until a third-party block’s developer does that, it may not look or behave the same inside the editor. (Details)
• Icons API goes public: New functions like wp_register_icon_collection(), wp_register_icon(), and wp_get_icon() let plugins and themes register custom icon sets with server-side rendering and REST API endpoints. SVGs are sanitized against a strict allowlist. (Dev note)
• Design system maturity: The wordpress/theme package introduces design tokens and a stable React ThemeProvider for consistent UI theming. (Details)
• Connectors authentication: The Connectors framework will support username and application-password login in addition to API keys. (Details)

We are looking forward to the release of WordPress 7.1. It may not have a single blockbuster feature, but it fixes a long list of everyday annoyances, and that matters more for most website owners.

Our favorite additions are the upgraded Notes and responsive styling. The ability to tag a teammate on an exact sentence brings WordPress much closer to a modern editorial tool.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post What’s Coming in WordPress 7.1? (Features & Screenshots) first appeared on WPBeginner.

Inspired by Om I’ve been getting back into my DSLR photography. I learned a lot about how ISO settings work from this delightful physics YouTube channel MinutePhysics.

Hi,

After a few month dealing with a bad knee and a bad back, I enjoy moving again. As long as the weather is nice, I will be biking, swimming and walking the city with all the tourists that populate downtown Munich.

From an SEO veteran’s surprisingly upbeat take on WordPress market share to a one-file answer to “what makes a block theme,” this week’s finds dig a little deeper than the usual headlines. There’s also plenty of hands-on material, whether you want to test 7.1 Beta 3, try the new Playground UI, or get your store ready for agentic commerce.

Enjoy your weekend!

Yours,
Birgit

WCUS 2026 has a dedicated AI track

The AI in Action sessions are built around the questions site builders are actually sitting with right now. How do you set guardrails for AI-assisted development without losing client trust? How do you build sites that serve AI agents as visitors, not just humans? What are the legal and ethical boundaries when you put AI tools in front of clients?

They’re practical sessions for developers navigating a workspace that changed faster than anyone planned for. The full schedule is live. If you’re figuring out how AI changes your pricing, your workflow, or your service model, this is a rare room to be in.

August 16–19, Phoenix Convention Center. $100 includes four days, all sessions, lunch, and the community social.
 us.wordcamp.org/2026/tickets

Developing Gutenberg and WordPress

WordPress 7.1 Beta 3 is now available for testing.

Rae Morey, The Repository, has the news WordPress 7.1 Beta 3 Now Available, Punts Unicode Email Support Over Security Concerns

Contribute by Help Test WordPress 7.1 and learn deeply how the new features and blocks work. It’s a very impactful way to contribute to the open-source project that powers hundreds of millions of websites.

Quite a few Dev notes made it out of the publishing queue this week:

• Text Shadow Support in Global Styles
• Editor components updates in WordPress 7.1
• Editable blocks inside the Custom HTML block
• React 19: punted beyond WordPress 7.1, experiment in Gutenberg
• Registering and rendering SVG icons in WordPress 7.1

The latest episode is Gutenberg Changelog #132 – Proposals for Core, Calls for Testing, WordPress 7.1 and Gutenberg 23.4 and 23.5

Plugins, Themes, and Tools for #nocode site builders and owners

On the WordPress.com blog, Joe Fylan explains what agentic commerce means for your store. AI assistants that discover, compare, and buy products on a shopper’s behalf. You’ll get an overview of where the big AI tools stand on in-chat checkout, plus reassurance that small stores can win with verifiable facts. Fylan’s checklist for getting ready: clear product descriptions, structured data, and making sure your robots.txt isn’t blocking the agents you want.

Dave Smith, core committer and Gutenberg contributor, thinks WordPress has a homepage problem — and he built a better version to prove it. In his video, he walks you through why setting a static homepage trips up so many beginners, then demos a prototype exploring a simpler, clearer approach. You can try the live demo yourself in the browser. Smith wants to know if the direction resonates, so drop your homepage struggles in the video’s comments.

Theme Development for Full Site Editing and Blocks

In episode 226 of the WP Tavern Jukebox podcast, Nathan Wrigley talks with Jessica Lyschik about why accessibility in WordPress themes is easier than you think. Fresh from her WordCamp Europe 2026 talk, Lyschik walks you through the recently updated accessibility-ready requirements, quick wins like correct HTML tags, alt text, and skip links, and why block themes make much of this effortless because Core handles it. The insight: AI agents navigate your site like screen readers do.

Ryan Welcher digs into how WordPress decides a theme is a “block theme” — and the answer might surprise you. It all comes down to one file: templates/index.html exists, or it doesn’t. Neither theme.json nor patterns flip the switch, which is why Astra, Kadence, and Blocksy all still test classic.

Building Blocks and Tools for the Block editor

In episode 477 of the WP Builds podcast, Nathan Wrigley talks with Olly Campion and Tommy Rockett about lessons from their WordPress plugin business and their block-based plugin Slidey Panel, which slides customizable side panels into any site. You’ll hear how years of client work revealed a gap in both classic themes and the block editor, the philosophy behind their “page as panel” approach, and their candid take on AI, market share shifts, and the future of bespoke agency work.

Ryan Welcher walks you through What’s New for WordPress Developers for July 2026 in his monthly video roundup. You’ll learn why WordPress 7.0.2 is a must-install security release, how to test React 19 via a runtime flag in Gutenberg 23.4, and what the now-enforced iframed editor means for your themes. He also covers responsive styling, Block Bindings for list items, and MCP support in Playground. Prefer reading? There’s a companion post on the Developer Blog.

What’s new with Playground

The Playground team wants your help testing the new WordPress Playground UI before it officially launches. Fellyph Cintra shares four testing modules you can pick from: creating and managing Playgrounds, the Blueprint experience, developer tools like Files and Logs, and import/export workflows. Five minutes on desktop or mobile is enough, and the post walks you through each step. Feedback on text clarity, mechanics, and design goes into the GitHub issue #4092.

Elliott Richmond shares how he uses WordPress Playground and Blueprints to train clients on block themes, inspired by WordCamp Europe. For a client migrating from a classic theme, he trimmed a gigabyte-plus database to a 50MB export, then built a Blueprint that loads their actual theme, plugin, and content into a disposable in-browser site. You send one link, the client can safely break things, and a refresh resets everything — no hosting or credentials needed.

WordPress and AI

On the Kinsta blog, Carlo Daniele takes a deep dive into the WordPress AI integration architecture that arrived with WordPress 7.0. You’ll learn how the three layers — Connectors, AI Client, and Providers — replace bundled SDKs and provider-specific code with the unified wp_ai_client_prompt() function. Daniele then walks you through building a real plugin, available on GitHub, that transcribes an audio note and converts it into structured Gutenberg blocks via two AI passes.

An interesting take: On the MemberPress blog, SEO veteran Curt Noble argues that WordPress lost market share and got stronger. Drawing on twenty years in SEO, including his own private blog network (PBN) days, Noble contends the dip mostly reflects Google demolishing the spam economy that ran on WordPress. Meanwhile, search interest hit a five-year high, WordPress dominates the top 10,000 sites, and the vibe-coding security hangover is sending founders back to proven platforms. Noble’s bigger point: with the AI Client, Abilities API, and MCP Adapter, WordPress became the platform AI agents can natively and safely operate.

Jeff Paul announced what’s new in AI 1.2.0, the latest release of the canonical AI plugin. You’ll find a new Suggest Reply experiment that drafts contextual comment responses for moderators to review, bulk Content Summary generation for existing content libraries, and two read-only Abilities: core/read-content and core/read-users. The settings screen got simpler, too, with advanced controls now tucked behind an opt-in Developer Tools option. Content Translations and C2PA (Coalition for Content Provenance and Authenticity) tracking are on the 1.3.0 roadmap.

Need a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.

Now also available via WordPress Playground. There is no need for a test site locally or on a server. Have you been using it? Email me with your experience.

Questions? Suggestions? Ideas?
Don’t hesitate to send them via email or
send me a message on WordPress Slack or Twitter @bph.

For questions to be answered on the Gutenberg Changelog,
send them to changelog@gutenbergtimes.com