WordPress shipped its second major release of 2026 on August 19, and most business owners will never notice. That is the point of hiring a good WordPress web developer: the update happens, the site keeps running, and nobody has to think about it. But three or four things actually changed in version 7.1, and they are worth understanding before your next redesign conversation or maintenance renewal, because they shift what a fair quote should include.
WordPress 7.1, "Mary Lou," released August 19, 2026, with no-code styling for hover, focus and active states, a native Tabs block, a Playlist block with waveform visuals, and faster client-side media processing. None of it replaces your WordPress web developer. It does mean fewer custom CSS line items belong on your next invoice, and it is a fair question to ask why a builder would charge for something the editor now does natively.
What actually shipped in WordPress 7.1?
"Mary Lou" launched at WordCamp US in Phoenix, named for jazz pianist and composer Mary Lou Williams, seven weeks after WordPress 7.0 and its own run of 7.0.x security releases through early August. The headline feature is interactive-state styling: you can now set how a button or block looks on hover, focus and active states directly in the block editor, per screen size, without writing a line of CSS. Two new core blocks ship alongside it, and the media pipeline moved partly into the browser.
| Feature | What it used to require | What changed in 7.1 |
|---|---|---|
| Hover, focus and active styling | Custom CSS, a child theme, or a styling plugin | Set natively in the block editor, per screen size and per state |
| Tabs block | A third-party plugin such as Ultimate Tabs, or page-builder tabs | Native core block, no plugin dependency |
| Playlist block | A plugin or embed for podcast or course audio archives | Native block with waveform visualization |
| Media uploads and cropping | Server-side conversion, slower uploads on shared hosting | Browser-side conversion and resizing, plus a new crop and edit modal |
None of this is a redesign in a box. It closes small gaps that plugins and custom CSS used to fill, which matters more than it sounds like once you add up what those gaps used to cost.
Does this change what a WordPress web developer should charge you?
Somewhat, and mostly at the margins. If a developer previously billed a few hours to hand-code hover states on a services page, or installed and configured a tabs plugin for an FAQ section, that work is now a five-minute task inside the editor on a block theme. If your next quote still lists "custom hover interactions" or "tabbed content module" as a line item, ask whether it means a genuinely custom design or something 7.1 now does for free. This connects to the wider block themes versus page builders debate: every native block release narrows the gap that used to justify a page builder's higher price and slower page speed.
What has not changed is anything that actually requires a developer: information architecture, custom post types, integrations with your CRM or booking system, accessibility auditing, and the judgment to know when the native block is not good enough for your brand. A capable WordPress web developer should be telling you which parts of 7.1 replace billable work on your account, not staying quiet about it.
Should you upgrade now, or wait?
Core updates are generally safe, but "generally" is doing some work in that sentence if your site runs a page builder and a dozen plugins from different vendors.
| Your situation | Recommendation |
|---|---|
| Business site on a current block theme, small plugin list | Upgrade in the next scheduled maintenance window |
| Page builder site (Elementor, Divi) or many legacy plugins | Wait 2 to 4 weeks for plugin authors to confirm compatibility, then update in staging first |
| WooCommerce store with custom checkout work | Test in staging before touching production; checkout regressions are the most expensive kind to discover live |
| Site already behind on 7.0.x security releases | Apply the security updates first, then plan the 7.1 jump separately |
On our own maintenance accounts we hold major WordPress core updates for roughly two weeks after release and watch the plugin compatibility threads before pushing to production. 7.1 has been stable through its first ten days with no widespread breakage reports, which is a faster, cleaner rollout than 7.0 had in July. That is a data point, not a guarantee, so staging still comes first on anything that takes payments.
What should your developer actually build with the new blocks?
The Tabs block is a genuine fit for FAQ sections, product specification sheets and side-by-side service comparisons, all things a business site accumulates over time and previously handled with a plugin or a wall of headings. The Playlist block is narrower: it suits podcast archives, recorded webinars, and course audio, and is a poor fit for anything that needed video. Ask your developer to show you the native block version of whatever they are proposing before you agree to a custom build. Most business sites do not need a bespoke component here, though a site with a distinctive visual identity in its website design and development might still warrant one.
Is this part of a bigger AI push inside WordPress?
Loosely, yes. WordPress 7.0 shipped what the trade press covered as "AI foundations in core" back in July, alongside a modernized admin and new design tools. 7.1 continues in the same direction without being an AI release itself: less manual CSS, fewer server round-trips for media, and a smoother editing experience. The practical read for a business owner is not "WordPress writes your site now." It is that a shrinking share of a competent build's cost should go to boilerplate styling and plumbing, and a growing share should go to strategy, structure and copy, the parts a template still cannot do for you.
Questions to ask before your next project or update
- Which parts of 7.1 will they use natively rather than build custom, and why the difference matters for your budget.
- How they test plugin compatibility before pushing a core update to a live site.
- Whether your current theme is classic, hybrid or full block, since 7.1's styling controls only apply fully to block themes.
- What their rollback plan looks like if an update breaks something in production.
- Whether core updates are billed inside your maintenance retainer or as separate one-off work, and what triggers the difference.
Frequently asked questions
When did WordPress 7.1 release?
WordPress 7.1, code-named Mary Lou after jazz pianist and composer Mary Lou Williams, released on August 19, 2026 at WordCamp US in Phoenix. It followed 7.0 by about seven weeks and several 7.0.x security and maintenance releases through August.
Do I need a new WordPress web developer to use WordPress 7.1's features?
No. The new hover and focus styling, Tabs block and Playlist block work inside the standard block editor. Your current WordPress web developer can apply them during a normal update, provided your theme is a block theme rather than a classic or heavily customized page-builder theme.
Will WordPress 7.1 break my plugins or theme?
Classic themes, page builders like Elementor or Divi, and sites with many older plugins carry the most risk. Well-maintained block themes and a small, current plugin list have shown few reported issues in the release's first ten days. Test in staging before pushing to a live e-commerce or lead-gen site.
What is the Tabs block and do I need it?
The Tabs block organizes content into clickable panels natively, without a third-party plugin. It suits FAQ sections, product specs and service comparisons. If your site already uses a plugin for tabs, ask your developer whether switching to the native block is worth the migration effort.
Does WordPress 7.1 include AI features?
WordPress 7.1 itself is not an AI release. It builds on the AI foundations WordPress 7.0 introduced in core in July 2026 by cutting down the amount of manual CSS and server round-trips a site needs, which is a step in the same direction rather than a new AI feature.
How much should a WordPress web developer charge to apply a core update?
A routine core update with no plugin conflicts should be a small line item inside a $50 to $500 monthly maintenance retainer, not a standalone project. If a developer quotes a large one-off fee for a single point release, ask what remediation work is actually driving that number.
The takeaway
WordPress 7.1 is not a reason to rebuild anything. It is a reason to look at your next quote a little more closely, because the update quietly moved a handful of tasks from "billable custom work" to "built in." A good WordPress web developer will point that out to you unprompted. One who keeps quoting the old way, on the old blocks, is worth a direct question before you sign off.