WordPress 7.2 Beta 1 arrived on October 20, 2026. This is the last major release of the year, with the final version scheduled for December 8. For agencies that build and maintain client sites, the next six weeks matter more than the launch day itself. Feedback during the beta window can still shape what ships. After Release Candidate 1 on November 17, the feature set is locked.
Turn Your Website Traffic Into More Leads
WordPress Development • SEO • Web Design • Performance • CRO • AI Search Visibility
This post covers the changes that affect real client work: theme development, plugin compatibility, HTML sanitization, design tools, and security processes. It is written for teams that manage multiple sites and need clear next steps rather than a full changelog.
If your agency handles WordPress development, redesigns, or ongoing maintenance, these are the items worth testing on staging first. At WebHivez we already run every major beta against our standard client stack so surprises stay off production sites.
The roadmap to 7.2 is out
The official roadmap lists security hardening, new design tools, block improvements, and a new default theme. Not everything on the list is guaranteed. The core team is clear that items still under active development can move to a later release if they are not ready by Beta 1.
Key areas for agencies include:
- Security work around Application Passwords, a tentative Secrets API (CLI only in this cycle), and related hardening.
- Expanded block supports and responsive style states.
- A Description List block and server side rendering for the Table of Contents block.
- Design tools such as form elements in Global Styles and better control over inherited styles.
- No real time collaborative editing. That work continues on a separate track.
The practical takeaway is simple. If your plugins or custom themes touch any of the listed systems, test them now while reports can still influence the final code.
Meet Ipsum, the new default theme
WordPress 7.2 ships with Ipsum, the first default theme in 16 years that does not use a year based name. The name comes from the familiar lorem ipsum placeholder text. The design is intentionally minimal: a quiet blog theme meant to act as a blank canvas rather than a finished look.
Ipsum is a block theme. Almost all of its styles live in theme.json and Global Styles. Style variations can recolor the entire page, including images. Every combination is built to meet WCAG AA contrast. Headers, heroes, and sidebars stay available when needed and stay out of the way when a writer simply wants to publish.
For agencies this matters in two ways. New client installs will start with Ipsum instead of the previous default. Existing sites keep their active theme, so no automatic switch occurs. If you build starter themes or white label solutions, Ipsum is worth studying for its minimal CSS approach and strong accessibility baseline. The theme is already available for testing on GitHub and in WordPress Playground.
wp_kses() is being rebuilt on the HTML API
One of the more technical changes is a rebuild of wp_kses(), the function that sanitizes HTML in posts, comments, and plugin output. The old version relied on regular expressions. The new version runs on the HTML API.
The new parser normalizes markup, strips the contents of script and style elements, and rejects certain malformed SVG, MathML, and comments. Output can look different even when the intent stays the same: tags in lowercase, attributes in double quotes, and adjusted entity encoding.
If any of your plugins or themes sanitize HTML and then compare, store, or test the result, run those code paths against the beta now. A temporary filter, wp_kses_force_legacy_parser, restores the old behavior. Treat it as a short term bridge, not a permanent solution. Report any breakage on the related Trac ticket so the team can address it before the final release.
This change is the kind of quiet update that surfaces weeks after launch if left untested. Agencies that maintain large numbers of client sites should add it to the standard beta checklist.
Block supports arrive on nearly every Core block
Gutenberg 24.1 focused heavily on design tool consistency. Roughly 140 pull requests added existing block supports to Core blocks that previously lacked them. Background images, gradients, shadows, link and button colors, borders, text columns, and text alignment are now available across a much wider set of blocks.
For theme authors this is useful. Custom CSS written to give a Code block a shadow or a Latest Posts block a background can often move into theme.json under styles.blocks. The result is cleaner code and fewer overrides.
One detail to watch: Accordion, Tabs, Tab Panel, and Post Template blocks now output has link color and related classes. If your theme styles links inside those blocks, check for specificity collisions before updating client sites.
Blocks can build responsive custom controls
Responsive style states arrived in WordPress 7.1, but the helpers were private. Only Core blocks could offer per breakpoint controls. Gutenberg 24.1 made those helpers public.
Third-party blocks can now use the same viewport state functions that Core blocks use. Position can also vary by viewport, so a header can be sticky on mobile and static on desktop without custom CSS.
Agencies that ship custom blocks should review any hard coded responsive logic. Moving that logic into the official API reduces maintenance and keeps the editor experience consistent for clients.
Plugin releases now get an automated security review
Plugin authors who publish to the WordPress.org directory face a new process. During the release cooldown, several AI models and Jetpack Scan score each new release. High risk releases are blocked automatically, and committers receive an email with the findings.
Make sure the email address on every committer account is monitored. A blocked release that sits unread can delay client updates. This change is not optional for directory plugins; it is part of the new pipeline.
Core icons now use strokes, not fills
The Core icon set was redrawn. Roughly 330 icons are now stroke based and set fill: none inline on the SVG. A CSS fill rule or fill prop no longer recolors them. Use the CSS color property instead.
If your agency themes or plugins include admin styles that target Core icons with svg { fill: … }, those rules will stop working. Update @wordpress/icons and @wordpress/components together to avoid mixed versions that drop styles.
Text shadow becomes a block support with presets
Text shadow moved from a Global Styles option into a full block support with theme defined presets. Paragraph and Heading blocks opt in by default. Custom blocks can enable it with a simple entry in block.json. Themes define presets in theme.json, which then generate custom properties and utility classes.
This is a small but useful addition for design systems that already rely on consistent typography treatments.
What agencies should do next
Here is a practical sequence for teams managing client sites:
- Update any sites still missing the latest security releases from September.
- Spin up a staging environment with WordPress 7.2 Beta 1 (or use Playground for quick checks).
- Test custom themes against the expanded block supports and the new icon set.
- Run any HTML sanitization logic through the new wp_kses() implementation.
- Check custom blocks for opportunities to use the public responsive style helpers.
- Review plugin release processes if you publish to the directory.
- Explore Ipsum if you maintain starter themes or onboarding flows for new clients.
The beta window is the cheapest time to find problems. After RC1 the focus shifts to verification rather than requests for changes.
WordPress 7.2 continues the platform’s move toward more consistent design tools, stronger sanitization, and clearer defaults. For agencies the value is in the practical details: fewer CSS overrides, better responsive controls, and earlier visibility into potential compatibility issues.
If you need help testing client sites against the beta or planning the December upgrade path, the team at WebHivez handles exactly this kind of work every release cycle.
Frequently Asked Questions
Do people still use WordPress in 2026?
Yes, very widely. WordPress still powers about 40.1–40.2% of all websites worldwide (W3Techs, October 2026). Among sites that use a known content management system, its share is around 58.7%.
It remains the most used CMS by a large margin. Shopify is second at roughly 5.4%. While the overall share has dipped slightly from its peak of about 43% in early 2025, hundreds of millions of sites still run on it, and new sites continue to be built every day.
What is the expected latest version of WordPress in 2026?
- Current stable version (as of October 20, 2026): WordPress 7.1.3 (released October 6, 2026).
- Next major version: WordPress 7.2.
- Beta 1 released today (October 20, 2026)
- Final release scheduled for December 8, 2026
By the end of 2026, the latest version will be 7.2.
What are the new features in the latest version of WordPress?
In the current stable version (7.1):
- Responsive style states (per breakpoint controls)
- Improved Notes (block level comments) with mentions
- Better media handling and image processing
- Icon Registration API
- Various editor and performance improvements
Coming in WordPress 7.2 (December 2026):
- New default theme called Ipsum (minimal, blank canvas design, first non year named default theme in 16 years)
- Suggestion mode + emoji reactions in Notes
- Expanded block supports across nearly every Core block
- Public API for responsive custom controls in third party blocks
- Rebuilt wp_kses() HTML sanitizer based on the HTML API
- Form elements stylable in Global Styles
- Description List block and stabilized Table of Contents block
- Security improvements (Application Passwords hardening, tentative Secrets API)
- Stroke based Core icons and other design tool updates
Real time collaborative editing and major AI features are not included in 7.2 (they remain in separate plugins or later cycles).
Is WordPress obsolete?
No. It is still the dominant CMS, actively developed, and used by businesses of every size. The platform continues to receive major releases (three in 2026 alone), security updates, and significant new features.
Some simpler marketing sites have moved to hosted builders (Wix, Squarespace, Shopify), which explains the modest share decline. However, for content heavy sites, membership sites, e commerce (WooCommerce), custom applications, and agency work, WordPress remains a strong, flexible, and widely supported choice.
