SVG icons are replacing Dashicons across WordPress 7.2’s admin bar and menu, changing how some custom styles appear. The WordPress Core team says most plugins and themes will continue working without changes, but color schemes and customizations that alter core icons may need updates. The shift is documented in the WordPress 7.2 SVG icon update.
The change affects how icons are drawn, not how site owners register menu pages or admin bar nodes. Existing registration continues to work, including when developers use Dashicons. The main adjustment falls on code that targets the old CSS-generated glyphs.
Where WordPress SVG Icons Affect Existing Styles
Styles that set icon colors through the ::before pseudo-element no longer reach the new inline SVG itself. The Core team says color schemes should apply the color to the containing menu or icon element as well, allowing the SVG to inherit it. Developers should account for hover, focus, current and open states, along with mobile rules.
Hiding or replacing an icon also requires revised selectors. A rule that hides only ::before may leave the SVG visible, while a background image placed on a glyph may need its own content and dimensions. Admin bar customizations that previously replaced an icon on .ab-item::before may now need to target .ab-icon::before.
For developers reviewing the wider release, WordPress 7.2 Beta 1 design tools covers other changes in the same release. The Core note says the menu data and REST API continue to use existing Dashicons values. Plugins that do not modify core admin or menu icons generally need no changes.
WordPress Adds a Registered SVG Icon API
WordPress 7.2 also lets developers use registered icon names when adding menu pages, post types and admin bar nodes. The new admin bar icon argument accepts a namespaced icon name. Developers can register their own icon collections and icons, or use an icon in the core-admin collection. A name that is not registered displays no icon; with WP_DEBUG enabled, WordPress also triggers a _doing_it_wrong() notice.
The new icon-name support does not work in earlier versions for menu pages and post types. The Core team recommends checking whether wp_is_valid_icon_name() exists before passing an icon name there. For admin bar nodes, developers can provide both an earlier-version Dashicon and the new SVG icon argument.
That compatibility detail matters for teams supporting multiple WordPress releases. A recent WordPress core update shows why release changes can also carry security implications, while this WordPress performance guide addresses other maintenance work site owners may plan.
Developers whose code changes core icons should review their color, hiding and replacement rules against the new markup. Those using standard menu registration or leaving core icons untouched can continue with the existing approach, according to the Core team.
