![\"Overview](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/08\/whats-new-in-wordpress-7-1-in-post.png\")
<\/figure>\n\u2139\ufe0f Important:<\/strong> As always, please don\u2019t forget to create a complete WordPress backup<\/a> before updating to the new release. If you are not using managed WordPress hosting<\/a>, then you will need to run the update yourself.<\/p>\n Here is everything that\u2019s new in WordPress 7.1:<\/p>\n The Notes feature arrived in WordPress 6.9<\/a> as a simple way to leave comments on blocks. WordPress 7.1 turns it into a proper feedback system.<\/p>\n The most useful addition is @mentions. You can type \u2018@\u2019 inside a note to bring up a searchable list of collaborators and tag someone directly.<\/p>\n Even better, WordPress now sends an email notification to the person you tagged. This addition landed late in the release cycle, and it completes the feature.<\/p>\n Your teammate no longer needs to keep the editor open to know that feedback is waiting. The email brings them straight back to the right post.<\/p>\n You can also leave inline notes. Instead of attaching a comment to an entire block, simply select a specific sentence or phrase and leave a note on just that text.<\/p>\n The selection stays highlighted, so everyone can see exactly which words the note refers to. In our testing, this removed a lot of guesswork from editorial feedback.<\/p>\n Other Notes improvements include:<\/p>\n These changes make Notes genuinely useful for teams, agencies, and multi-author blogs. It is a solid step toward a better editorial workflow<\/a> inside WordPress itself.<\/p>\n Visual revisions, which were introduced in WordPress 7.0<\/a> have been improved as well. They now include a new feature to share links to individual revisions.<\/p>\n For example, let\u2019s say that you want to show a team member which changes were made to an article. You can now open the revisions screen, pick the exact version, and copy the link from your browser toolbar.<\/p>\n You can then share that link and when opened, the link will take users to the exact revision with changes highlighted.<\/p>\n Visual revisions also get a new picker layout in this release. It makes browsing your edit history easier, with color-coded changes carried over from WordPress 7.0.<\/p>\n This is the feature we are most excited about. Responsive styling has been one of the longest-standing requests in the block editor, and WordPress 7.1 finally delivers a first version.<\/p>\n You can now define how a block looks at different screen sizes directly in the editor. For example, you can set a smaller font size for headings on mobile without writing a single line of CSS<\/a>. <\/p>\n Here is how it works: Click the device preview icon in the editor\u2019s top toolbar and turn on the new \u2018Responsive styles\u2019 option.<\/p>\n Now, switch the preview to Tablet or Mobile. From this point, any style change you make applies only to that screen size.<\/p>\n During testing, we selected a smaller font size for a button in the Tablet view, and the desktop design stayed untouched. WordPress also shows a small badge in the block settings panel, so you always know which viewport you are styling.<\/p>\n It works on two levels. You can set responsive styles in Global Styles, which apply to every instance of a block across your site, or you can style an individual block on a specific page.<\/p>\n The editor canvas is also more flexible. Instead of being limited to the Desktop, Tablet, and Mobile presets, you can drag the canvas to any width and watch your blocks respond in real time.<\/p>\n Theme developers can even define their own breakpoints in Alongside responsive styling, WordPress 7.1 introduces interactive state styling.<\/p>\n A new \u2018State\u2019 dropdown lets you visually style how blocks respond to interaction. For example, you can set a different background color for a button\u2019s hover, focus, or active state and preview the change live in the editor.<\/p>\n Previously, changing a button\u2019s hover color required adding a custom CSS snippet. Now, it can be easily done inside the editor itself. <\/p>\n There is also a thoughtful refinement when you apply local style changes globally. WordPress now shows a quick review step, so you can choose exactly which modified styles to apply across your site and keep the rest as local overrides.<\/p>\n WordPress 7.1 adds a Tabs block that many users have been asking for.<\/p>\n Tabs let you organize content into clickable panels instead of showing everything at once. They are great for product specifications, FAQs<\/a>, or comparing options without making a page feel long.<\/p>\n The final release has also added toolbar buttons for reordering tabs, which was a rough edge we noticed during the beta. Previously, you had to add tabbed content using a plugin<\/a>, so it\u2019s great to see this functionality now available as a core WordPress block.<\/p>\n We also like that accessibility was not an afterthought here. The block follows the W3C ARIA Authoring Practices Guide, which means it works properly with keyboards and screen readers out of the box.<\/p>\n The second new block in WordPress 7.1 is the Playlist block. It lets you add a collection of audio files to any post or page, complete with track metadata, artwork, and a waveform visualization.<\/p>\n This is a nice upgrade for musicians, churches, educators, and anyone who publishes audio. If you run a podcast with WordPress<\/a>, you can now list recent episodes in a clean player without a separate plugin.<\/p>\n WordPress 7.1 replaces the old inline cropping tool with a dedicated Media Editor modal.<\/p>\n The entry point stays familiar. You still click the Crop button on an Image block, but now a full editing modal opens with freeform cropping, aspect-ratio presets, flip and rotate controls, and metadata editing in one place.<\/p>\n In our testing, the magnified crop view was the standout. It makes fine adjustments much easier, and the crop handles snap cleanly to pixels.<\/p>\n The new editor also works with the Cover block<\/a>, so you can crop a background image right where you use it.<\/p>\n This will not replace a full photo editor. However, for the basic image editing<\/a> most site owners need, being able to make them directly in the editor is a big usability win.<\/p>\n WordPress 7.1 continues the client-side media processing work that started in WordPress 7.0. In simple terms, your web browser does the heavy lifting of processing images before they reach your server.<\/p>\n This release expands format support in a meaningful way. WordPress can now handle HEIC photos, which is the default format on iPhones, along with UltraHDR, AVIF, and WebP.<\/p>\n Until now, iPhone users often needed a HEIC to JPG conversion plugin<\/a> just to upload their photos. With 7.1, that friction mostly disappears.<\/p>\n Uploads are also more resilient. If your internet connection drops mid-upload, then the upload queue pauses and automatically resumes when you are back online.<\/p>\n There are also several tiny improvements that make everyday WordPress tasks a little easier:<\/p>\n Together, these changes mean fewer upload errors and less load on your server. That is especially good news if you are on a budget WordPress hosting<\/a> plan.<\/p>\n WordPress 7.1 makes the admin toolbar persistent. It now remains visible in the Site Editor and the Block Editor, instead of disappearing when you start editing.<\/p>\n The toolbar itself has also gotten a design cleanup as part of this change:<\/p>\n In our testing, this made moving between the editor and the rest of the admin feel much more predictable. Each icon now means one thing everywhere.<\/p>\n The \u2018Howdy\u2019 greeting<\/a> survived another release. The core team discussed removing it during this cycle, but the change did not make it into 7.1.<\/p>\n If you prefer a clean writing canvas, then don\u2019t worry. The toolbar stays hidden in Distraction Free mode<\/a>.<\/p>\n Beyond the toolbar, WordPress 7.1 includes a set of smaller admin improvements that add up.<\/p>\n Command palette improvements.<\/strong> The Command Palette (Ctrl+K on Windows, Command+K on Mac) now groups results into Recent, Matching, and Suggestions sections. WordPress saves your recently used commands to your preferences, so they persist across sessions.<\/p>\n Your admin color scheme in the Site Editor. <\/strong>The Site Editor reflects your chosen admin color scheme instead of always using a fixed dark sidebar. It is a small thing, but it makes the whole admin feel consistent.<\/p>\n A dedicated Identity section<\/strong>. Site identity settings like your title, tagline, logo, and site icon now live in their own Design \u00bb Identity<\/strong> section in the Site Editor<\/a>. You no longer need to hunt through Settings and templates to update these basics.<\/p>\n Excerpts in the Posts list.<\/strong> The Posts list view now shows a short excerpt for each entry, making it easier to tell similar posts apart.<\/p>\n Select many items at once.<\/strong> In the Site Editor\u2019s list views, you can now click one item, hold Shift, and click another to select the whole range. If you manage hundreds of pages or media files, then this saves you time on bulk actions.<\/p>\n Change a comment\u2019s parent.<\/strong> The Edit Comment screen adds an editable \u2018In reply to\u2019 control, so you can finally fix comments that ended up as replies in the wrong place.<\/p>\n Several existing blocks get meaningful upgrades in this release:<\/p>\n Most sites can update to WordPress 7.1 without drama. However, if you run a large site with many plugins, then a few under-the-hood changes deserve your attention before you click update.<\/p>\n The editor is now always iframed.<\/strong> WordPress 7.1 completes a multi-year effort to place the editing canvas inside an iframe, and this now applies even when plugins register older-style meta boxes.<\/p>\n In simple terms, the editor content is loaded in a separate frame from the rest of the WordPress admin screen. This keeps admin styles and scripts from affecting the editing canvas as easily, which can make the editor more consistent and stable.<\/p>\n Most users won\u2019t notice the iframe itself. Instead, you\u2019ll mainly benefit from a more predictable editing experience.<\/p>\n There is a compatibility consideration, though. Older plugins that add custom scripts or styles to the editor may not work as expected with the iframe. Blocks also need to use Block API version 3 to render correctly inside the iframe.<\/p>\n WordPress 7.1 updates jQuery UI to version 1.14.2.<\/strong> jQuery UI is a JavaScript library that many older admin plugins use for things like date pickers and drag-and-drop screens. If a plugin on your site has not seen an update in years, then test it on staging first.<\/p>\n WordPress now enforces multisite upload limits everywhere.<\/strong> On WordPress multisite networks<\/a>, space quotas now also apply when a plugin imports media from a URL (a process called sideloading). Previously, this route quietly bypassed the per-site storage limit, so network admins can expect quotas to hold from now on.<\/p>\n Our advise remains the same: always create a complete backup of your website before hitting update.<\/p>\n A few features we covered during the beta cycle did not ship in the final release.<\/p>\n The core team cut the \u2018On This Day\u2019 widget.<\/strong> We previewed this dashboard widget in our beta coverage<\/a>, and we liked it. The team decided it needs more work, so it may return in a future release.<\/p>\n Real-time collaboration is still in development.<\/strong> Google Docs-style co-editing received a lot of testing during the 7.1 cycle, but the team held it back to keep working on conflict handling and compatibility. You can try an early version in the Gutenberg plugin<\/a>.<\/p>\n The Classic block stays in the inserter.<\/strong> The team originally planned to hide the Classic block from the block inserter in this release. After community feedback, they reverted the change, so nothing changes for sites that still rely on it.<\/p>\n The team also pulled Unicode email address<\/strong> support during beta testing. That work continues in a community plugin for broader compatibility and security testing before it lands in core.<\/p>\n We think this caution is the right call. A collaboration feature that loses someone\u2019s work would be far worse than a delayed one.<\/p>\n WordPress 7.1 also ships several technical improvements for developers and site performance:<\/p>\n For the complete list of developer changes, see the official WordPress 7.1 Field Guide<\/a>.<\/p>\n We have been following WordPress 7.1 from development to the final release. 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.<\/p>\n Our favorite additions are the upgraded Notes and responsive styling. Tagging a teammate on an exact sentence, and knowing they will get an email about it, makes WordPress modern collaboration tool. <\/p>\n And styling blocks for mobile without touching CSS removes one of the last big reasons beginners needed custom code.<\/p>\n If you haven\u2019t updated yet, then we recommend backing up your WordPress site<\/a> first. Once you are in, set aside a few minutes to explore Notes, the revisions sharing, and the responsive styling options. They are easy to miss but genuinely useful.<\/p>\n If you liked this article, then please subscribe to our\u00a0YouTube Channel<\/a>\u00a0for WordPress video tutorials. You can also find us on\u00a0Twitter<\/a>\u00a0and Facebook<\/a>.<\/p>\n The post What\u2019s New in WordPress 7.1? (Features & Screenshots)<\/a> first appeared on WPBeginner<\/a>.<\/p>","protected":false},"excerpt":{"rendered":" WordPress 7.1 is finally here \ud83e\udd73, and we have been closely following its development. The new version launched on August 19, 2026, timed with WordCamp US. Its focus is on how you collaborate, style, and manage media on your WordPress website, and it fixes a long list of everyday annoyances along the way. Whether you […]<\/p>\n","protected":false},"author":1,"featured_media":6284,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"advanced_seo_description":"","jetpack_seo_html_title":"","jetpack_seo_noindex":false,"jetpack_seo_schema_type":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[1],"tags":[],"class_list":["post-6283","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-latest-news"],"jetpack_likes_enabled":true,"jetpack-related-posts":[],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/frontlinenewsng.org\/wp-content\/uploads\/2026\/08\/whats-new-in-wordpress-7-1-in-post-Hn3Gsr.png","_links":{"self":[{"href":"https:\/\/frontlinenewsng.org\/index.php?rest_route=\/wp\/v2\/posts\/6283","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/frontlinenewsng.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/frontlinenewsng.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/frontlinenewsng.org\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/frontlinenewsng.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=6283"}],"version-history":[{"count":0,"href":"https:\/\/frontlinenewsng.org\/index.php?rest_route=\/wp\/v2\/posts\/6283\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/frontlinenewsng.org\/index.php?rest_route=\/wp\/v2\/media\/6284"}],"wp:attachment":[{"href":"https:\/\/frontlinenewsng.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=6283"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/frontlinenewsng.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=6283"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/frontlinenewsng.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=6283"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
Collaborate Better With the Upgraded Notes<\/h4>\n
![\"Tag](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/07\/note-mentions.jpg\")
<\/figure>\n\n
Share a Link to Any Revision<\/h4>\n
![\"Sharebale](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/08\/share-revision-link-wp71.jpg\")
<\/figure>\nResponsive Styling Without Writing CSS<\/h4>\n
![\"Responsive](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/07\/responsive-styles-site-editor.jpg\")
<\/figure>\n![\"Responsive](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/07\/responsive-design-device-indicatiors.jpg\")
<\/figure>\n![\"Drag](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/07\/device-break-points-1.gif\")
<\/figure>\ntheme.json<\/code>. That way, the preview widths match the theme you are actually using.<\/p>\nStyle Hover and Focus States for Buttons<\/h4>\n
![\"Interaction](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/07\/interaction-states.jpg\")
<\/figure>\nNew Tabs Block<\/h4>\n
![\"The](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/07\/new-tab-block.jpg\")
<\/figure>\nNew Playlist Block<\/h4>\n
![\"New](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/07\/playlist-block.jpg\")
<\/figure>\nA New Image Editor in WordPress 7.1<\/h4>\n
![\"New](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/07\/new-image-editor.jpg\")
<\/figure>\nSmoother and Smarter Media Handling<\/h4>\n
\n
![\"Use](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/07\/use-attached-images.jpg\")
<\/figure>\nThe Admin Toolbar Now Stays Visible When Editing<\/h4>\n
![\"Consistent](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/07\/consistent-admin-bar.jpg\")
<\/figure>\n\n
A More Personal And Easily Navigable Admin<\/h4>\n
![\"Command](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/07\/command-palette-suggestions.jpg\")
<\/figure>\n![\"Site](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/08\/site-editor-matches-admin-color-scheme.jpg\")
<\/figure>\n![\"New](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/07\/identity-tab-site-editor.jpg\")
<\/figure>\nBlock Improvements in WordPress 7.1<\/h4>\n
\n
![\"Mark](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/07\/mark-image-decorative.jpg\")
<\/figure>\n\n
![\"Icon](\"https:\/\/www.wpbeginner.com\/wp-content\/uploads\/2026\/07\/icon-block-options.jpg\"){kind=icon}
<\/figure>\n\n
Changes to Look Out for Before the Update<\/h4>\n
What Didn\u2019t Make It Into WordPress 7.1?<\/h4>\n
Under the Hood (Developer & Performance Updates)<\/h4>\n
\n
wp_register_icon_collection()<\/code>, wp_register_icon()<\/code>, and wp_get_icon()<\/code> let plugins and themes register custom icon sets with server-side rendering and REST API endpoints. WordPress sanitizes SVGs against a strict allowlist. (Dev note<\/a>)<\/li>\nwp_get_abilities()<\/code>, execution lifecycle hooks, a unified public exposure flag, and client-compatible JSON Schema output. These are the plumbing that AI agents and external tools use to work with your site safely. (Dev note<\/a>)<\/li>\nwordpress\/theme<\/code> package introduces design tokens and a stable React ThemeProvider for consistent UI theming. (Dev note<\/a>)<\/li>\nnotify_post_author<\/code> filter now has the final say on post author notifications, which makes custom editorial notification setups more predictable. (Dev note<\/a>)<\/li>\n<\/ul>\nFinal Thoughts on WordPress 7.1<\/h4>\n