Howdy,

It has been another evenful week for sure! WordCamp US came to an end and WordPress 7.1 was released.

Your WordPress profile now has a shortcut w.org/@[yourusername]. If you want to check out mine w.org/@bph (don’t forget the @ sign) . Mullenweg mentioned in his closing fire side chat that this could actually work without the redirect in the future. Now that would be cool, right?

Another cool and rather weird thing Mullenweg mentioned are Piplets. One self-contained PHP-file for your notes, no database, no hosting needed, for tinkerers who live in the Terminal window. If that’s you, grab the file from the GitHub repo and try it out. (64-bit PHP 8.1 or newer is required.) There will be . To be honest, it’s not my idea of simplicity, though. I am firm in the Obsidian camp.

Apropo WordCamp US: All Talks are already available in the Playlist on YouTube  for your on-demand viewing pleasure. Or you organize a viewing party with your local WordPress Meetup. Just a thought.

Have a great weekend!

Yours,
Birgit

Nicholas Garofalo’s recap of WordCamp US 2026 in Phoenix covers four days, 1,100 attendees, 111°F, and a Contributor Day where 425 people formed 26 teams around goals they could finish by evening. You’ll get the Showcase Day migrations of The Ankler and Daily Kos, keynotes from Bo English-Wiczling and Loyal Pyczynski on judgment in the age of AI, and Matt Mullenweg’s closing pitch for simplicity, including Piplets, a single self-modifying PHP file with no database.

WordPress 7.1 is out!

WordPress 7.1 “Mary Lou”, names after Mary Lou Williams an American jazz pianist, arranger, and composer who recorded hundreds of records.

The release video is fabulous. WordPress 7.1 Highlights Video

The WordPress 7.1 micro site with the featurettes, tiny videos highlighting the main features is definitely a beauty! What a pleasure to read and experience the most important updates!

Release lead Anne McCarthy kept a WordPress 7.1 release lead decision log, and it reads like the other half of the release notes. You’ll see why real-time collaboration, React 19, inherited-style display, and the Classic block removal were punted, why responsive styling got an opt-out rather than a pause, and how she decided to publish the announcement when auto-updates had already reached 300K sites while Matt Mullenweg was on the WordCamp US stage. Each entry links to the thread where the call was made.

On the WordPress Developer Blog, Justin Tadlock goes hands-on with the WordPress 7.1 Icon Registration API and builds a restaurant icon collection from scratch. You’ll register a collection with wp_register_icon_collection(), add 13 food icons via wp_register_icon(), and see why he prefers a string-backed PHP enum over arrays for naming them. He also lists what 7.1 still strips: only svg, path, and polygon elements survive, and stroke attributes are removed, so stick with fill-based icons for now.

If Justin Tadlock’s walkthrough is more than you need right now, Ryan Welcher covers the same API in five minutes in his video on custom icons in WordPress 7.1. He registers a collection and a single icon in PHP, loads a folder of SVGs from disk the way core does, and renders one in a template with wp_get_icon(). The gotchas matter most: the sanitizer strips fill="currentColor", and a function_exists() check keeps 7.0 sites from fatal-erroring.

The block editor’s single biggest frustration is finally addressed, Jackson argues in his tour of the new features in WordPress 7.1, and he means responsive block styles. Over twenty minutes you’ll see thirteen features in action: hover and active states for buttons and navigation, the Tabs block, the Icon block with Aki Hamano’s custom icon plugin, the Playlist block’s waveform, the in-browser media editor, and a Query Loop checkbox that stops your related posts from recommending the post you’re reading.

Gutenberg 23.8 released

Selecting all blocks in a 1,000-paragraph post used to take 16.8 seconds; in Gutenberg 23.8 it takes 0.4. Release lead Jon Surrell’s post on what’s new in Gutenberg 23.8 covers that List View speed-up alongside the shareable revision URLs and in-editor code diff, and email notifications when someone @-mentions you in a note. You also get a real default block on the empty canvas, Audio-to-Playlist transforms, and, for developers, inner block templates declared in registerBlockType() and public Calendar components in @wordpress/ui.

For the Gutenberg Changelog 134 episode, Jessica Lyschik, senior developer at Greyd, joined me to discuss Gutenberg versions 23.7 and 23.8. We also chatted about WordPress 7.1 and what comes next for the December release of WordPress 7.2 As always the episode with its show notes will come to your favorite podcast app over the weekend.

The latest episode is Gutenberg Changelog #133 – Gutenberg 23.6 Release and WordPress 7.1 with special guest Faith Imokol, webdeveloper from Uganda.

Plugins and Tools for #nocode site builders and owners

If you build with the Ollie block theme, Gina Lucia‘s WordPress 7.1 walkthrough shows where the new core features meet Ollie’s tools. Responsive styling now lives in core, so Ollie Pro’s Responsive Controls shift to handling column and grid stacking, while its Class Manager picks up where the new hover and focus states for Button and Navigation Link leave off. You’ll also see how the Tabs and Playlist blocks, gradient-over-image backgrounds, and the persistent admin bar fit your Ollie site.

Merging cells is still missing from the core Table block, and Aki Hamano‘s Flexible Table Block plugin fills that gap on 40,000+ sites. Version 3.9.0 adds WordPress 7.1 support and announces row and column selection to screen readers. You can merge and split cells, style the table, cells, and caption separately, and set your own breakpoint for horizontal scrolling or stacking cells on mobile. It also converts to and from the core Table block with rowspan and colspan intact. Aki Hamano is a major contributor to the Gutenberg project from Japan and co-tech lead for WordPress 7.1. There is a lot of crediblity attached to this plugin. And hat tip to Daniel Kossmann, editor of the Portuguese WordPress newsletter PainelWP 374.

The new Tabs block in WordPress 7.1 swaps panels abruptly, since the Interactivity API toggles the hidden attribute. Elliott Richmond‘s Tabs Animation plugin softens that with a fade or a slide from any of four directions, plus a duration up to 3000ms and five easing options under Settings → Tabs Animation. It’s one small inline stylesheet with no JavaScript and no theme changes, and it switches itself off for visitors who prefer reduced motion. One setting applies site-wide for now.

Building Blocks and Tools for the Block editor.

On his livestream, Ryan Welcher got back on his son’s hockey team site with WordPress Studio Code, this time handing over the single post template. The first pass got close, then navigation broke, the header came in too tall, and the content width wouldn’t match the homepage, so you’ll watch him go several rounds with Annotate, clicking and describing what’s wrong. Two hours used 2.5 percent of his monthly limit. He also covers the 7.1 iframe change and a twenty-minute custom fields tangent.

WordPress Studio the agentic local development app is still in beta. Help make it perfect!

	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

WordCamp US (WCUS) 2026 just wrapped up after 4 days at the Phoenix Convention Center in Phoenix, Arizona. Over 1,100 people from around the world registered to attend, and thousands more watched online through livestreams. Contributor Day and Showcase Day opened the week before two main conference days, featuring over 50 speaker-led sessions across 4 tracks, including multiple workshops.

The temperature reached 111°F (44°C), but golf carts ferried travelers between the Sheraton Phoenix Downtown and the convention center. Inside, attendees moved between session rooms, the Sponsor Hall, and the Happiness Bar.

It’s hot, but it’s not Florida hot.

– Loyal Pyczynski

Sessions covered artificial intelligence (AI), accessibility, publishing, business, site ownership, and the open web. Speakers in different rooms often found common ground, noting the importance of good judgment and trust-building in the age of AI.

Real Artists Ship

Contributor Day followed the motto “Real artists ship,” and a new format to match. The 425 participants, including 29 first-time contributors, formed 26 teams around goals they could complete that day. Experienced contributors moved between groups and helped newer participants shape goals. Then, goal owners gave 30-second pitches, and contributors could move between teams when that work caught their interest.

By day’s end, contributors had closed tickets, opened and shipped pull requests, and reviewed themes for accessibility. One team created description-list blocks for glossaries and product details, and another added email settings, a test tool, and checks for account, password-reset, and recovery messages.

Other teams built a Photo Directory importer and updated Notes in the WordPress dashboard and Multisite documentation. More work covered PHP, PHPUnit testing, and guidelines for AI work within the project. New contribution pathways became a course on Learn WordPress, open to people who could not be in Phoenix.

Every team ended the day with a 30-second presentation of what it had made, tested, fixed, or moved closer to release.

Showcase Day Put Real Sites First

If Contributor Day was about shipping in a day, Monday’s Showcase Day was about what happens after the shipping. Sites have to keep working smoothly for the people who publish, maintain, and depend on them. The case studies came from public services, independent publishers, community platforms, training systems, and large content operations.

Manny Costa covered the first of those: civic websites where residents find services, apply for programs, read emergency information, and report problems. In that work, accessibility, governance, and editor workflows are part of the service rather than a final check box.

Two of the case studies were about publishers taking back ownership of their content. Both sites now appear in the WordPress Showcase.

Nicola Catton’s session described how The Ankler moved 15 newsletters to WordPress and took direct control of its content, subscriber data, revenue rules, and reader experience. Nicola detailed the massive migration, the thousands of rebuilt paywall boundaries, and the site’s brand-new block theme.

The Daily Kos migration was a similarly large-scale move. Ben Greeley and Allison McHenry centered their session on a community that writes as well as reads: 1.5 million posts, 88 million comments, and 2.7 million users, with a public beta that involved more than 500 community members.

Other sessions dealt with the people who do the publishing once a site is live. In Aviral Mittal’s session, an AI agent built a page from a Google Doc using patterns the team had already defined. Andrew Adam described a library of about 100 written and video guides, with accessibility guidance included. Shared foundations covered repeat questions, while project-specific help and tips inside the editor handled the rest.

Human Judgment in the Loop

Early on, Bo English-Wiczling had opened Showcase Day by addressing the gap between rapid AI adoption and trust. Her keynote covered the move in developer work toward setting intent and supplying context.

AI doesn’t remove your work. It moves it.

– Bo English-Wiczling

A first draft can now arrive in seconds, but an almost-right block of code may still miss keyboard navigation, use the wrong theme styles, or bring an unsafe dependency into a project.

The importance of good judgment is familiar to the WordPress community. Bo tied it to habits WordPress contributors already have: reading other people’s code, submitting small changes, reviewing pull requests, and accepting critique in the open.

The next morning, Loyal Pyczynski drew on his work at Disney and Meta for a keynote about tests, time, and creative confidence. His talk returned to a phrase from an Imagineering colleague.

We need to make sure that we make better mistakes tomorrow. Success is an iterative endeavor, and time is our most precious resource.

– Loyal Pyczynski

Loyal described Disney teams that paired creative and technical leads early, then brought in experts for work another team could do better or faster. The goal was not to know everything but to know what the team should own.

Design and publishing sessions drew similar conclusions as the keynotes. Michelle Hunt framed design systems as living feedback systems that need to preserve intent as production gets faster.

K Adam White’s session centered on moving large stores of content into block patterns, with editors staying involved where automatic conversion still needed judgment. Nik McLaughlin’s Abilities API session looked beyond AI integrations to the broader structure the API gives WordPress developers. Brian Coords made a related case through block themes: approved patterns, templates, and real content offer a starting point, and design tokens add guidance that a blank-page prompt cannot provide.

Machine translation got the same treatment. In a multilingual WordPress multisite case study of AI translation for technical content, native-speaking colleagues found output that was correct word by word and could still miss the intended meaning. Human review covered the gap between translating language and translating intent.

The judgment question even reached hiring. The Making of a WordPress Certification introduced a standards-based certification and covered how the credential was created, checked, governed, and delivered.

Trust Becomes a Product Practice

Wednesday morning took the trust question outside the WordPress world. The day opened with a fireside chat between Amanda Ventura of Waymo and David Levine on what it takes for people to trust technology that moves through their streets.

Ventura described trust as repeated work. Teams can publish safety data and listen before arriving in a new city, and they need a path for product teams to act on feedback. Her example came from accessibility testing. Screen-reader support helped blind and low-vision riders use the Waymo app, but it did not solve the physical problem of finding the right car. Feedback led to step-by-step directions and a horn control with a distinct musical tone that was easier to identify on busy city streets.

Other sessions applied that standard to WordPress sites. WordPress Core committer Jonathan Desrosiers focused on supply-chain safety while Robert Abela’s session explored login security. AI tools can find security flaws faster than ever. That speed raises the need for careful checks.

The rest of Wednesday’s schedule included sessions on security, accessibility, design, AI tools, and work for site owners.

• Kathy Zant’s session proposed an audit for AI use, covering plugins, themes, content pipelines, and client sites, and it named consent, data location, disclosure, and legal review as questions teams should settle before launch.
• Another case-based session compared two responses to navigation problems: one client received an AI search tool, and another received a predictable interface that editors could control. The planned lesson was simple. AI can be the right choice without being the automatic choice.
• Joseph LoPreste’s session explored accessibility work no single plugin can complete: navigation, forms, headings, images, content, and interactive elements.

Learning With Your Laptop Open

WordPress beginner workshops ran throughout the event for first-time builders, with no hosting account or prior WordPress experience required. Participants made pages, posts, logos, and menus, and each person left with a WordPress site, a year of hosting, and a domain. These sessions laid groundwork to work with plugins, styles, and additional features. The beginner program, office hours, and Happiness Bar gave people several places to ask questions and get hands-on experience.

More advanced technical workshops offered even experts the chance to hone their skills.

• Łukasz Wilczak focused on reusable WP-CLI commands. They handled bulk content changes, block and shortcode migrations, link cleanup, and safe batch processing.
• Vedanshu Jain designed a workshop around roles and review paths for AI-only teams. The planned outputs included a plugin stub, publishable content, or another real result.
• Rob Ruiz built his workshop around WP Rig and automatic checks for preparing block-ready themes for the Theme Directory.

Like all WordCamps, these sessions gave attendees skills and tools to bring home to their own projects.

Simplicity Gets the Last Word

The closing session started with city business. Michael Hammett, Phoenix’s first Chief Innovation Officer, read a proclamation from Mayor Kate Gallego declaring August 19 Phoenix WordPress Day, and then presented the signed document to WordPress Cofounder, Matt Mullenweg. The proclamation credited WordPress with supporting the small businesses, developers, designers, educators, and creators in the city’s growing digital and creative economy.

What followed was a dynamic presentation and conversation between Mullenweg and Robert Jacobi, ending with a traditional Q&A. Matt’s thesis was simple: Tech needs to be simpler.

I want WordPress to be known for simplicity, not just complexity.

– Matt Mullenweg

After a detour through why AI models now prefer simple, self-contained HTML files, the argument became tangible with WordPress Piplets, a 2007 idea built around a single self-modifying PHP file that stores its own data, with no database and no third-party packages. One file can hold up to 25 megabytes, about four million words, and load in about 50 milliseconds. For Mullenweg, it extends the experiments that took WordPress from MySQL to SQLite to Playground, and he floated the idea of a WordPress.org directory where people could publish, fork, and remix.

Speaking of WordPress.org, it was announced that profile links are getting shorter, with w.org/username redirects like w.org/@matt already live, with full support just a few days away.

Midway through, release leads were called up to press the button on the WordPress 7.1 release, and were awarded with applause as “Mary Lou” received hundreds of thousands of downloads.

On contribution, Mullenweg expressed his desire to reward impact instead of pledges. The Five for the Future directory shows two million self-sponsored hours pledged each week from 150,000 contributors, and he questioned whether that reflects reality. The project already records what actually happened (commits, posts, tickets closed, WordCamps organized), and he wants recognition built on that record. He asked the same of the plugin directory, suggesting a focus on fewer better-working things.

Audience questions covered AI licensing, data centers, and why open source communities compete more than they collaborate. On that last one, Mullenweg invited other open source leaders to speak at WordCamp, and encouraged working together. Copying good code between projects, he said, is the entire point of open source.

Jacobi closed by asking who was at their first WordCamp; he had met more first-timers here, he said, than in the past ten years. One of them found the event by asking an AI chatbot for the coolest thing happening in Phoenix, came to Contributor Day, and left with one of its awards.

Beyond the Session Rooms

So much happens outside the session rooms. At the WCUS Happiness Bar, volunteers sat with attendees and worked through plugin questions, CSS problems, ecommerce setup, and new-site questions. An AFK (Away From Keyboard) room offered a quiet place away from the crowds. In the Sponsor Hall, people painted Wapuus with a local Phoenix artist, watched screen-printing, and talked between product demonstrations.

The Connect art installation used photographs from the WordPress Photo Directory. Forty postcards paired images by contributors who may never have met. Color, composition, or subject linked each pair. Attendees could take several cards and a blank one, then add a connection of their own.

Lunch did something simpler. People changed tables, picked up open seats, and started conversations with one question: “What do you do with WordPress?”

Organizers and volunteers kept four days of rooms, shuttles, meals, and livestreams moving. Thank you to them, and to the speakers, sponsors, contributors, attendees in Phoenix, and everyone watching online.

What Comes Next

If you missed this year’s WordCamp US, you can find recordings of sessions on us.WordCamp.org/2026/. Be sure to sign up for email notifications, so you don’t miss out next year. Next stop, State of the Word, followed by WordCamp Asia 2027 in Penang, Malaysia, and WordCamp Europe 2027 in Málaga, Spain.

Photo credits: Jaron Quach, Emily Chan, Wini Lao, Kendra Stowe, and
Jennifer Swisher

WordPress 7.1 is finally here 🥳, 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 run a small blog or a large multi-author site, WordPress 7.1 has changes that will affect how you work every day.

ℹ️ Important: As always, please don’t forget to create a complete WordPress backup before updating to the new release. If you are not using managed WordPress hosting, then you will need to run the update yourself.

Here is everything that’s new in WordPress 7.1:

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 turns it into a proper feedback system.

The most useful addition is @mentions. You can type ‘@’ inside a note to bring up a searchable list of collaborators and tag someone directly.

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.

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.

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.

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.

Other Notes improvements include:

• Multiple threads: You can start more than one conversation on the same block.
• 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.
• Private by design: WordPress stores notes as a special comment type, and 7.1 now excludes them from your public comment feeds.

These changes make Notes genuinely useful for teams, agencies, and multi-author blogs. It is a solid step toward a better editorial workflow inside WordPress itself.

Share a Link to Any Revision

Visual revisions, which were introduced in WordPress 7.0 have been improved as well. They now include a new feature to share links to individual revisions.

For example, let’s 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.

You can then share that link and when opened, the link will take users to the exact revision with changes highlighted.

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.

Responsive Styling Without Writing CSS

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.

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.

Here is how it works: Click the device preview icon in the editor’s top toolbar and turn on the new ‘Responsive styles’ option.

Now, switch the preview to Tablet or Mobile. From this point, any style change you make applies only to that screen size.

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.

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.

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.

Theme developers can even define their own breakpoints in theme.json. That way, the preview widths match the theme you are actually using.

Style Hover and Focus States for Buttons

Alongside responsive styling, WordPress 7.1 introduces interactive state styling.

A new ‘State’ dropdown lets you visually style how blocks respond to interaction. For example, you can set a different background color for a button’s hover, focus, or active state and preview the change live in the editor.

Previously, changing a button’s hover color required adding a custom CSS snippet. Now, it can be easily done inside the editor itself.

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.

New Tabs Block

WordPress 7.1 adds 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.

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, so it’s great to see this functionality now available as a core WordPress block.

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.

New Playlist Block

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.

This is a nice upgrade for musicians, churches, educators, and anyone who publishes audio. If you run a podcast with WordPress, you can now list recent episodes in a clean player without a separate plugin.

A New Image Editor in WordPress 7.1

WordPress 7.1 replaces 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 now a full editing modal opens with freeform cropping, aspect-ratio presets, flip and rotate controls, and metadata editing in one place.

In our testing, the magnified crop view was the standout. It makes fine adjustments much easier, and the crop handles snap cleanly to pixels.

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

This will not replace a full photo editor. However, for the basic image editing most site owners need, being able to make them directly in the editor is a big usability win.

Smoother and Smarter Media Handling

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.

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.

Until now, iPhone users often needed a HEIC to JPG conversion plugin just to upload their photos. With 7.1, that friction mostly disappears.

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.

There are also several tiny improvements that make everyday WordPress tasks a little easier:

• 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 do not have to dig through the whole Media Library.
• Infinite scrolling: The Media Library grid now loads more items automatically as you scroll. WordPress turns this on by default, and you can bring back the old page-by-page view from your user settings if you prefer it.

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 plan.

The Admin Toolbar Now Stays Visible When Editing

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.

The toolbar itself has also gotten 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.
• Modern SVG icons replace the old Dashicons.

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.

The ‘Howdy’ greeting survived another release. The core team discussed removing it during this cycle, but the change did not make it into 7.1.

If you prefer a clean writing canvas, then don’t worry. The toolbar stays hidden in Distraction Free mode.

A More Personal And Easily Navigable Admin

Beyond the toolbar, WordPress 7.1 includes 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. WordPress saves your recently used commands to your preferences, so they persist across sessions.

Your admin color scheme in the Site Editor. 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.

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

Excerpts in the Posts list. The Posts list view now shows a short excerpt for each entry, making it easier to tell similar posts apart.

Select many items at once. In the Site Editor’s 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.

Change a comment’s parent. The Edit Comment screen adds an editable ‘In reply to’ control, so you can finally fix comments that ended up as replies in the wrong place.

Block Improvements in WordPress 7.1

Several existing blocks get meaningful upgrades in this release:

• Background gradients and images work together. You can now layer a gradient over a background image on the Group block and several other blocks. This is handy for keeping text readable over hero images.
• Text shadows in Global Styles. Themes and users can now configure text shadows through theme.json and Global Styles.
• Editable content inside the HTML block. The HTML block 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. Decorative images with meaningless alt text are one of the most common accessibility mistakes, and this makes the fix easy.

• Smarter shortcode handling. Pasting or converting an embed shortcode now creates a proper Embed block instead of leaving raw shortcode text behind.
• Icon block upgrades. The Icon block now includes controls to flip or rotate icons, starts with a sample icon instead of an empty placeholder, and includes an icon picker organized by collections. Plugins and themes can now register their own icon sets, so expect branded icon libraries from your favorite plugins.

• Grid transforms. Columns and Gallery blocks can now transform into Grid layouts while preserving their content.
• Query Loop exclusion. The Query Loop block gets an option to exclude the current post, so your “related posts” section never recommends the post the visitor is already reading.

Changes to Look Out for Before the Update

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.

The editor is now always iframed. 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.

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.

Most users won’t notice the iframe itself. Instead, you’ll mainly benefit from a more predictable editing experience.

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.

WordPress 7.1 updates jQuery UI to version 1.14.2. 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.

WordPress now enforces multisite upload limits everywhere. On WordPress multisite networks, 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.

Our advise remains the same: always create a complete backup of your website before hitting update.

What Didn’t Make It Into WordPress 7.1?

A few features we covered during the beta cycle did not ship in the final release.

The core team cut the ‘On This Day’ widget. We previewed this dashboard widget in our beta coverage, and we liked it. The team decided it needs more work, so it may return in a future release.

Real-time collaboration is still in development. 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.

The Classic block stays in the inserter. 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.

The team also pulled Unicode email address support during beta testing. That work continues in a community plugin for broader compatibility and security testing before it lands in core.

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

Under the Hood (Developer & Performance Updates)

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

• Faster editor startup: WordPress now preloads the REST API requests the editor needs on load, so the editor opens faster, especially on content-heavy sites. (#65636)
• 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. WordPress sanitizes SVGs against a strict allowlist. (Dev note)
• Abilities API expansion: The machine-readable registry of WordPress capabilities, introduced in WordPress 6.9, gains filtering for wp_get_abilities(), 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)
• Block Bindings for List Items: Block Bindings now extend to the List Item block, so more content can connect to dynamic data sources like custom fields. (Details)
• Speculative loading configuration: Hosts and developers can now configure speculative loading defaults (loading pages in the background before a visitor clicks) through environment variables and constants. (#65624)
• Accessible tooltips: Core introduces a shared mechanism for accessible tooltips, replacing pointer-only title attributes in several screens. It is part of a 46-ticket accessibility push in this release. (Dev note)
• Design system maturity: The wordpress/theme package introduces design tokens and a stable React ThemeProvider for consistent UI theming. (Dev note)
• Author notification control: The notify_post_author filter now has the final say on post author notifications, which makes custom editorial notification setups more predictable. (Dev note)

For the complete list of developer changes, see the official WordPress 7.1 Field Guide.

Final Thoughts on WordPress 7.1

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.

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.

And styling blocks for mobile without touching CSS removes one of the last big reasons beginners needed custom code.

If you haven’t updated yet, then we recommend backing up your WordPress site 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.

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 New in WordPress 7.1? (Features & Screenshots) first appeared on WPBeginner.

Each WordPress release celebrates an artist who has made an indelible mark on the world of music. WordPress 7.1, code-named “Mary Lou,” honors pioneering jazz pianist, arranger, and composer Mary Lou Williams.

A child prodigy who began playing publicly at six, her influence and work cut across nearly every major era of jazz, moving through swing, bebop, and sacred jazz. Through all of it, she kept reinventing her own sound. In the 1940s, she turned her Harlem apartment into a nightly workshop where Thelonious Monk, Dizzy Gillespie, and Bud Powell came to trade ideas and shape bebop itself. That combination of reinvention and collaboration inspired WordPress 7.1.

Let the range of Mary Lou’s music carry you through everything 7.1 offers.

Welcome to WordPress 7.1!

WordPress 7.1 is built around how you work: navigating the admin, controlling your designs, collaborating with others, and building what you want. The admin bar now follows you across the entire admin experience, putting the tools you need within reach, whether you’re writing a post or editing your site’s design. Built-in responsive styling, added to the current show/hide options for blocks, means you can ensure your site looks exactly how you want across screen sizes, without custom CSS. A new media editor keeps the familiar Crop button entry point, and brings freeform and aspect-ratio cropping, horizontal and vertical flipping, fine-grained and snap rotation, and metadata editing into one dedicated workflow. Leave Notes anywhere in your content—no longer limited to the block level. Rich text support and @mentions make it easier to collaborate with others as you write. Two new blocks, Playlist and Tabs, as well as a new API to register your own set of icons for the Icon block, give you even more flexibility to build what you want without additional plugins. These are just the highlights! Read on to see everything WordPress 7.1 has to offer.

What’s inside

There’s a lot packed into WordPress 7.1 across new styling tools, updated media flows, added Notes functionality, and more. Some changes add new capabilities, while others refine existing tools and workflows.

Here’s a closer look at what’s new in this release, starting with the release video:

Apply responsive styles

Style your content your way, on every screen.

WordPress 7.1 brings more responsive controls directly into the Site Editor. Style how a block looks at different screen sizes from Global Styles or in individual block settings, without custom CSS. You can also preview your changes at different viewport sizes as you work, making it straightforward to build layouts that adapt to the way people browse the web.

Admin bar, now in every editor

Consistent navigation, from dashboard to editor.

The WordPress admin bar now stays with you as you move across all editors, so you always know where you are and have easy access to familiar tools. The admin bar also features some small visual updates to more fully polish the experience.

A new way to crop

One dedicated workflow for editing your images.

A new media editor modal replaces the previous inline cropping tool, bringing together freeform and aspect-ratio cropping, horizontal and vertical flipping, precise rotation control, and metadata editing together in one place. The familiar Crop button still gets you there.

Inline notes with mentions and rich text

More ways to leave feedback.

Notes now support rich text and mentions, making it easier to leave clear feedback and loop in the right people. Format your Notes with bold, italic, and code, add links, or type @ to mention a collaborator and notify them.

You can also leave a note on a specific piece of text instead of just an entire block, keep multiple conversations going on the same block, and collapse longer notes to keep the margin tidy. It’s built for the back-and-forth that happens when people review content together.

Improved media handling

Faster, more flexible image processing.

Image compression, resizing, and thumbnail generation now happen in the browser, reducing server load and producing smaller files — without hitting PHP memory limits or upload timeouts.

Media handling in 7.1 also includes native support for AVIF, HEIC, and HDR gain maps, adding native support for the image formats modern cameras and phones already produce.

Enhanced details and new blocks

WordPress 7.1 also adds two new blocks, along with more ways to customize how content looks and behaves.

Create playlists

Bring multiple audio tracks together in one playlist, with an optional waveform that gives listeners a visual sense of each track as it plays.

Customize responsive breakpoints

Block themes can now define their own mobile and tablet breakpoints in theme.json, overriding the defaults for responsive styles and block visibility.

Organize with tabs

Organize content into tabbed panels instead of showing everything at once—a cleaner way to present related information without crowding your content.

Add custom icons

Developers can extend WordPress’s icon library with their own collections, making custom icons available throughout the editor alongside the built-in library.

Set interactive styles

Give Button blocks distinct styles for hover, focus, and active states directly in the editor’s style controls. Set the styles for just one button or all buttons.

A more consistent editing experience

The post editor is now fully iframed for all themes, matching the Site Editor.

The editing canvas runs separately from the WordPress admin interface, so admin styles don’t interfere with your content. Viewport-relative units and media queries now target the editing canvas directly, so responsive layouts behave more predictably as you build. The change is mostly invisible, but the result is a more reliable and consistent editor.

Developer’s toolbox

Advanced tools for building your way.

WordPress 7.1 expands several of the APIs and tools developers use to build on WordPress, with new options for icons, automation, admin interfaces, and responsive styling.

The SVG Icon API is now a public API, allowing developers to register their own icon collections and icons and use them throughout the editor with functions such as wp_register_icon_collection(), wp_register_icon(), and wp_get_icon().

The Abilities API builds on the infrastructure introduced in WordPress 6.9 with a filterable execution lifecycle, custom validation, and shared discovery. These additions make it easier to build integrations and automation on top of WordPress, including AI-powered tooling.

A new Design System provides foundational support for theming WordPress admin interfaces, including color, roundness, and cursor styles. Developers can use semantic design tokens and the ThemeProvider React component to bring more consistency to custom admin interfaces while still feeling at home in WordPress.

Theme authors also get responsive styling and pseudo-state styling for hover, focus, focus-visible, and active states through theme.json, along with new filters for configuring the DataViews and DataForm screens that power Pages, Templates, Parts, and Patterns in the Site Editor.

Accessibility

WordPress 7.1 continues to improve accessibility across WordPress Core and the editor. New wp_get_tooltip() and wp_get_toggletip() functions bring accessible tooltips to more areas of the WordPress admin, including post meta boxes and the login screen.

Screen reader support also improves across admin interfaces, with clearer labeling and more predictable navigation in post list tables. The new Tab and Playlist blocks, along with improvements to editor navigation and interaction, add to the broader accessibility work included in this release.

Together, these changes continue to make WordPress easier to navigate and use for more people.

Performance improvements

Image compression, resizing, and thumbnail generation now run in the browser (via a WebAssembly build of libvips), reducing the processing load on your server and helping avoid memory limits and timeouts with larger uploads.

Opt-in GIF-to-video conversion produces typically smaller files, while upload progress indicators and automatic retries make uploads more resilient when connections drop.

The Media Library now uses infinite scrolling by default, with a per-user option to return to pagination. Speculative loading defaults can now be set through environment variables or constants, so hosts and site owners can configure how WordPress prefetches pages without writing a plugin.

And much more!

For a comprehensive overview of everything new and improved in WordPress 7.1, visit the feature showcase website.

Learn more about WordPress 7.1

Learn WordPress is a free resource for new and experienced WordPress users. Learn is stocked with how-to videos on using various features in WordPress, interactive workshops for exploring topics in-depth, and lesson plans for diving deep into specific areas of WordPress.

Read the WordPress 7.1 Release Notes for information on installation, enhancements, fixed issues, release contributors, learning resources, and the list of file changes.

Explore the WordPress 7.1 Field Guide. Learn about the changes in this release with detailed developer notes to help you build with WordPress.

The 7.1 release squad

Every release comes to you from a dedicated team of enthusiastic contributors who help keep things on track and moving smoothly. The team that has led 7.1 is a cross-functional group of contributors who are always ready to champion ideas, remove blockers, and resolve issues.

• Release Lead: Anne McCarthy
• Release Coordination: Benjamin Zekavica, Krupa Nanda
• Tech Leads: Aki Hamano, Joe Dolson
• Triage Leads: Adrian Duffell, Sajjad Hossain Sagor, Sergey Biryukov
• Test Leads: Huzaifa Al Mesbah, Nikunj Hatkar

Thank you, contributors

The mission of WordPress is to democratize publishing and embody the freedoms that come with open source. A global and diverse community of people collaborating to strengthen the software supports this effort.

WordPress 7.1 reflects the tireless efforts and passion of more than 800 contributors from all over the world. This release also welcomed over 170 first-time contributors! 

Together, their work delivered more than 1500 enhancements and fixes, helping make WordPress 7.1 a stable and polished release for everyone. It’s another great example of what the WordPress open source community can accomplish when people come together to build, test, and improve the software

1shiharaT · Aagam Shah · Aakash Verma · Aaron D. Campbell · Aaron Jorbin · Aaron Robertshaw · Abdalsalaam Halawa · Abdullah Ramzan · Abdur Rahman Emon · Abhishek Kumar · Achal Jain · Adam Silverstein · Adam Wood · Adam Zieliński · Adi Moldovan · adithyanaik · Aditya Singh · Adrian Duffell · adrmf25 · agulbra · Ahmed · Ahmed Kabir Chaion · ahuseyn · Aki Hamano · Akshat Kakkad · Alain Schlesser · Alan Jacob Mathew · Albert Juhé Lluveras · Alec Geatches · Alex Concha · Alex Cuadra · Alex Kirk · Alex Stine · alhrath · allilevine · Alvaro Gómez · Amber Hinds · Aminul Islam Alvi · Amit Joel · Amit Raj · Amjad Ali · Amy Kamala · Anastis Sourgoutsidis · Anders Norén · Andrea Fercia · Andrea Grassi · Andrea Roenning · Andrei Draganescu · Andrej Mernik · Andrew Duthie · Andrew Matia · Andrew Ozz · Andrew Serong · André Maneiro · Andy Fragen · Andy Meerwaldt · Anh Tran · Ankit K Gupta · Ankit Kumar Shah · Ankit Panchal · Ankit Patel · Anne McCarthy · Anne-Mieke Bovelett · Anthony Hortin · Anukasha Singh · Anup Kankale · Anveshika Srivastava · aperto · arcangelini · Ari Stathopoulos · Arischvaran Puvanesvaran · Arkaprabha Chowdhury · Armand MD · Arshid · Arthur Chu · Artur Piszek · Ashar Fuadi · aslushnikov · aswasif007 · atomiks · Aurooba Ahmed · avcascade · ayaz ahmed · ayushhoff · Azhar Ali · Azhar Deraiya · Azragh · BackuPs · Baikare Sandip · Barry · Bart Kalisz · Bayejid Ahmed · Ben Dwyer · Benedikt Ledl · Benjamin Grolleau · Benjamin Zekavica · Benoit Chantre · Bernie Reiter · Bero · bigdigital · Bigul Malayi · Birgir Erlendsson (birgire) · Birgit Pauli-Haack · Blake Bertuccelli-Booth · bluefuton · bobbingwide · Boro Sitnikovski · brad hogan · Brad Jorsch · bradshawtm · brajdas0022 · Brandon Hubbard · Brandon Kraft · Brandon Payton · brbrr · Brian Alexander · Brian Coords · Brian Gardner · Brian Haas · Brian Henry · Brian Hogg · Bridget Willard · brnhrst · Burhan Nasir · burnuser · Béryl de La Grandière · C83 · Camila Rayza Mendoza Vargas · Carlos Bravo · Carolina Nymark · CAT the Tech · cbirdsong · ccprog · cgastrell · Chad Chadbourne · Charalampos Papazoglou · Chillifish · Chouby · Chris David Miles · Chris Gresham-Britt · Chris Huber · Chris Lilitsas · Chris M. – a11n · Chris Zarate · chriscct7 · Christoph Daum · Chuck Grimmett · Ciprian Popescu · Clément Polito · Code Amp · codesmith32 · Cody · cogdesign · ColinD · collinr3 · Corey Worrell · Courtney Robertson · Cris Busquets · csabarakasz · cweiske · Dakota Chichester · Damianne P (a11n) · Damon Cook · Dan Luu · Dan Zakirov · Dani Guardiola · Daniel Bachhuber · Daniel Richards · dannyreaktiv · Darin Kotter · Darren Ethier (nerrad) · Darshit Rajyaguru · Dave Whitley · David Aguilera · David Arenas · David Baumwald · David Biňovec · David Bowman · David Cavins · David Levine · David Shanske · David Smith · David Stone · Dean Sas · Deepak Gupta · Deepak Kumar · Deepak Prajapati · Deepak Rohilla · Denis Žoljom · Dennis Heiden · Dennis Ploetner · Dennis Snell · deoladev · Deryck · Devanshi Joshi · Devasheesh Kaul · Dharmesh Patel · Dhaval Kapadane · Dhrumil Kumbhani · Dhruvang21 · Dhruvik Malaviya · diegogarciarodrigues · Dion Hulse · dlind1 · Dominik Schilling · Douglas Henri · Drew Jaynes · Drivingralle · Dávid Szabó · eclev91 · Edith Allison · efc · Ehtisham Siddiqui · eishanoor · ekaterina92 · elfu98 · Eliot Akira · elizaan36 · Ella van Durpe · Ellen Bauer · Emmanuel Atsé · Enej Bajgorić · Eoin Savage · Eric · Eric Michel · Erick Wambua · Eshaan Dabasiya · Esteban · Estela Rueda · eurello · Evan Herman · Fabian Kaegy · Faisal Ahammad · Fakhri Azzouz · Felipe Velzani · Felix Arntz · Fernando Perrella · Fernando Tellado · Filippo Di Trapani · firdaus666 · Florence ANDROLUS · Francisco Leiton · Francisco Vera · Ga Satrya · Gabor Lippert · Gajendra Singh · galaxor · galois44 · Gareth Elwell · Garrett Hyder · Gary Jones · Gary Pendergast · Gaurang Sondagar · Gautam Garg · Gautam Mehta · Gaël Bonithon · Generosus · George Mamadashvili · Germán · gierand · gilmoursa · Glen Davies · Gopal Krishnan · Greg Ziółkowski · gregbenz · griffithchen · gschoppe · gubser · Guillaume G. · Gulamdastgir Momin · gusgomezpg · Gustavo Hilario · H. Adam Lenz · Habibur Rahman · hanneslsm · Hans-Gerd Gerhards · Hareesh S · Harish Tewari · harshbhonsle08 · Hasmukh Khemchandbhai Mistry · Hasnain Ashfaq · Haz · Henrique Iamarino · Hidekazu Ishikawa · Hilay Trivedi · Himanshu Pathak · Hit Bhalodia · Hrohh · Hugo · humanify · Huzaifa Al Mesbah · Héctor Prieto · iamchughmayank · iamraju · ianmjones · Ibrahim Riaz · iflairwebtechnologies · Iqbal Hossain · irozum · Isabel Brison · Ishika Bansal · Ishita · itsdavidmorgan · Jacob Smith · Jacopo Marrone (@tresorama) · Jadav Sanjay · jakeparis · jakub300 · James · James Giroux · James Koster · James LePage · James Monroe · Jamie Burchell · janpaulkleijn · Jarda Snajdr · jarekmorawski · jarodortegaaraya · Jason Adams · Jason Kenison · Jason Kytros · Jason LeMahieu (MadtownLems) · Javier Arce · Javier Casares · javorszky · Jay McPartland · Jaydip · Jean-Baptiste Audras · Jean-Sébastien Mansart · Jeff Chi · Jeffrey Carandang · Jeffrey de Wit · Jeffrey Paul · jeflopo · Jenny Dupuy · Jeremy Felt · Jeremy Herve · Jeremy Ward · jeryj · Jessica Lyschik · jigangz · Jigar Bhanushali · Jigar Kahar · Jigar Panchal · Jignesh Bhavani · jillq · jimgrey · Jina Parekh · JiveDig · jjlmoya · jnbg · Job a11n · Joe Dolson · Joe Fusco · Joe Hoyle · Joe Maller · Joe McGill · Joen Asmussen · Johannes Jülg · John · John Blackbourn · John Hooks · John James Jacoby · John Parris · John Watkins · Jon Surrell · Jonathan Bossenger · Jonathan Desrosiers · Jonny Harris · Joost de Valk · jordesign · Jorge Costa · Jos Velasco · Jose Varghese · Joseph Scott · Joshua Dwire · Joshua Wold · joshualipstone · Juanfra Aldasoro · JuanMa Garrido · Julie Moynat · Juliette Reinders Folmer · Justin Tadlock · K. Adam White · Kamran Abdul Aziz · Kamrul Hasan · kannanravi · Kapil Paul · Karan Makani · Karthick · Karthikeya Bethu · katag9k · Kathryn Presner · Kausar Alam · Kaushik Domadiya · Kavit Trivedi · Kavya Gokul · Kelly Choyce-Dwan · Kelly Hoffman · keoshi · Kerry Liu · Kevin Fodness · Kevin Robles Gamboa · Khokan Sardar · Khokan Sardar · Khushal Sain S · Khushi Patel · Kim Coleman · Kira Schroder · KJ Roelke · Kjell Reigstad · Kleis Auke Wolthuizen · Knut Sparhell · Koen Van den Wijngaert · KokkieH · Konstantin Obenland · Kostas Vrouvas · Krupa Nanda · Krystian · kuber8821 · kubiq · Kushagra Goyal · Kyle Mott · Lakshyajeet Singh Goyal · Lance Willett · landwire · leemon · Lena Morita · levinmedia · liaison · Lisa Canini · Lisa Schuyler · LOOS · Louis Wolmarans · Lucas Mendes · lucasbustamante · Lucian R. · Ludwig You · Luigi Teschio · Luis Martins · luisdavid01 · luisherranz · luismulinari · Luke Carbis · mabdelbari · Madhavi Shah · madhazelnut · Madhu Dollu · Maggie Cabrera · Mahammad Darvishov · MahdiAli Khanusiya · Mahesh Patel · Mainul Hassan · Mainul Kabir Aion · Makarand Mane · maksymmamontov · Malay Ladu · manfcarlo · Manhar Barot · Manish Dhorepatil · Manuel Camargo · Manzoor Wani · Marc · Marco Ciampini · Marcus · Marcus Kazmierczak · Marin Atanasov · Mario Santos · Marius L. J. · Mariusz Szatkowski · Mark Howells-Mead · Mark Uraine · Marko Ivanovic · Marty Helmick · Mary Hubbard · Maryam Sultana · Mateus Machado Luna · Matheus Zimmermann Galdino · mathijsvdbeek · Matias Benedetto · Matias Ventura · Matt Mullenweg · Matt Shaw · mattbolt · Matthew Boynes · Max Schmeling · maximebj · Mayank Tripathi · Md Abul Bashar · MD ISMAIL · Md Rashedul Islam Chowdhury (Ric) · Md. Aminul Islam · mdviralsampat · Mehraz Morshed · mehtadev · Mehul Gohil · mgol · Micha? Dudak · Michael Adams (mdawaffe) · Michael Etokakpan · Michael Iseard · Michael James Ilett · Michal Iwanow · Miguel Fonseca · Miguel Lezama · Miguel Torres · Mikael Korpela · Mike Jolley · Mike Selander · Mikey Binns · Mikin Chauhan · Milana Cap · Milind More · mimi · Minal Diwan · Mir Monoarul Alam · Miroku · Mitchell Austin · Mohammad Jangda · Mohammad Risad · Mohammad Rockeybul Alam · Mohammed Kateregga · Mohammed Noumaan Ahamed · Mohd Salman · Mohit Sharma · Moksha Shah · Monzur Alam · Moses Cursor Ssebunya · mrwweb · Mukesh Panchal · Mukesh Parihar · Mustafa Bharmal · mutuajose · MythThrazz · Nabhishek Singh · nadabulija · Naman Khare · NANI SAMIREDDY · Naresh Bheda · Nate Finch · Nathan Rodrigues · Nazmul Asif · Nazmul Hosen · Nebojša Jurčić · Ned Zimmerman · nendeb · Nick Diego · Nick Halsey · Nick Murray · nickpagz · nickthegeek · nicolasalarconrapela · nicsevic · Nik Tsekouras · Nikul Valani · Nikunj Hatkar · Nilambar Sharma · Nilesh Shiragave · Niluthpal Purkayastha · Nimesh · Nirav Sherasiya · Noah Allen · Noelle Ackermann · Noruzzaman · notnownikki · obliviousharmony · oldenwilde · Olga Gleckler · OllieJones · Omar Alshaker · onetrev · Ov3rfly · Ozgur Sar · Paal Joachim Romdahl · Pablo Honey · Pamela Ribeiro · pankaj.sakaria · Parin Panjari · Parth vataliya · Pascal Birchler · Patrick Lumumba · patrickwclanden · Paul Bearne · Paul Biron · Paul Kevan · paulgibbs · Paulo Trentin · Pavan Patil · pavelevap · pavloborysenko · Pedro Figueroa · Peter Wilson · petermolnar · petitphp · Phil Johnston · philhoyt · physalis · Pieterjan Deneys · Piyush Patel · poligilad · pontocinza · Pooja Kakkad · porg · postphotos · Prachi Garg · Pradeep Pasam · Praful Patel · prajapatvishnu · Pranjal Pratap Singh · pranjal4804 · Prasad Karmalkar · Prashant Baldha · Prathamesh Bhagat · Pratik Jain · Pratik Nawkar · Pravin Karmur · Prem Tiwari · Presskopp · Priyanka Gusani · ProjektIsle · Q · Rachel · Rafael Della · Rafael Funchal · Rafał Gazda · Rahul Kumar · Rahul Tank · Rajdip Tank · Rajesh C · Rajin Sharwar · Rakeesh Falke · Rami Yushuvaev · Ramon Corrales · Ramon James · Ravi Chudasama · Ravi Gadhiya · Ravi Khadka · Rejaul Alom Khan · Renatho · reneyap · retrofox · Rezwan Shiblu · Riad Benguella · Rian Rietveld · Rich Tabor · Rinkal Pagdar · Rishabh Gupta · Rishit Gupta · RITHESH S · Ritoban · Robeen · Robert Anderson · Robert Ghetau · Robert Jolly · robertabela · Roberto Aranda · Rodrigo Primo · Rohit Mathur · Rolf Allard van Hagen · Rolle Laukkarinen · Rolly Bueno · ronakganatra9 · Roshni Ahuja · Rushikesh More · Rutvik Savsani · Ruud · Ryan · Ryan Welcher · Saad Ur Rehman · Sabbir Ahmed · Sabbir Hossain · SACHINRAJ CP · Sagar Deshmukh · Sagar Jadhav · SAHIL NAZIR · Sainath Poojary · Sajjad Hossain Sagor · Saksham Sharma · Sam · Sampat Viral · Sana Yasir · Sandip Sinh · sandipmaurya2611 · SAndrew · Sanket Parmar · Sanyogg Shelar · Sarah Norris · Sarath E · Sarosh Aga · Sarthak Nagoshe · Saul Fougnier · saulirajala · Saulius Vikerta · Saulo Padilha · Saxon Fletcher · Scott Kingsley Clark · Scott Reilly · Sergey Biryukov · Seth Rubenstein · Shail Mehta · Shailesh Gajare · Shane Muirhead · Shashank Shekhar · Shatrughan Myatra · shaunandrews · Shazzad Hossain Khan · shekharnwagh · Sheri Grey · Shreya Shrivastava · Shreyas Ikhar · Sidhant Tomar · siliconforks · Simon Duduica · Simon Wämmerfors · simonhammes · slackticus · slywy · smerriman · Sneha Patil · snehal Kashid · Soham Patel · Sonali Prajapati · Sorin · Sourav Pahwa · Soyeb Salar · spacergif · speedwheel · Sphere Plugins · sruthi89 · SteelWagstaff · Stefan Pasch · Stefan Velthuys · Stephen Bernhardt · Steve Dufresne · Steve Jones · Steven Lin · Steven Ryan · strarsis · styankov · Sukhendu Sekhar Guria · Sumit Bagthariya · Sumit Singh · Suryakant Upadhyay · Swanand M · swapnil1010 · Sybre Waaijer · Synchro · szandman · Sérgio Gomes · Sören Wünsch · Taco Verdonschot · tainacan · Taisa – Raquel García Arévalo · Takashi Irie · Takashi Kitajima · Takshil Kunadia · Tammie Lister · tbclark3 · Terence Eden · Tetsuya Imamura · thelmachido a11n · thinkaquamarine · This Is My URL · threadi · Thrive Engine · tibi.buzdugan · Tim Nicholson · Timi Wahalahti · Timothy Jacobs · Tobias Bäthge · Tobias Zimpel · tobifjellner (Tor-Bjorn “Tobi” Fjellner) · Tom Rhodes · Tomoki Shimomura · Tonya Mork · Toro_Unit (Hiroshi Urabe) · TorontoDigits · tpaw · tratnikm · Troy Chaplin · Tung Du · Tushar Bharti · Tushar Patel · Ugyen Dorji · Umesh Nevase · up1512001 · upadalavipul · Utsav Ladani · Vara Rahul Rajana · Vedansh Mishra · Vedant Ere · Vedant Gandhi · Velda · vgnavada · Vicente Canales · Viktor Szépe · Vincent Bodart · Vinit · Vishit Shah · vishnu prajapat · vivekawsm · vortfu · Vraja Das · Vrishabh Jasani · WebMan Design | Oliver Juhas · webVerts · Weston Ruter · whaze · Will Skora · williampatton · wongjn · WPExplorer · wpsoul · xate · Xavier Borderie · xavilc · xerpa43 · Xristopher Anderton · Yan · Yash Jawale · Yogesh Bhutkar · Yui · Yuliyan Slavchev · Yusuf Mudagal · Zebulan Stanphill · Znuff

More than 20 locales have fully translated WordPress 7.1 into their language making this one of the most translated releases ever on day one. Community translators are working hard to ensure more translations are on their way. Thank you to everyone who helps make WordPress available in 200+ languages.

Last but not least, thanks to the volunteers who contribute to the support forums by answering questions from WordPress users worldwide.

Get involved

Participation in WordPress goes far beyond coding. And learning more and getting involved is easy. Discover the teams that come together to Make WordPress and use this interactive tool to help you decide which is right for you.