On August 13, 2026, WordPress released an official browser extension. Not a plugin. Not a theme feature. A browser extension, available on the Chrome Web Store and the Mac App Store for Safari, that changes how you interact with every WordPress site you visit without touching a single line of server code.

The announcement did not make as much noise as WordPress 7.1, which shipped six days later. That is a mistake. This extension solves problems that every WordPress developer and site manager hits daily, and it does it in a way that a plugin never could.

What it actually does

The core feature is admin bar control. You know the black bar that sits across the top of every page when you are logged into WordPress? It is useful for quick shortcuts, but it also shifts the entire page down by 32 pixels. On any site with a sticky header, a full-height hero section, or scroll-triggered animations, that offset creates visual artifacts that do not exist for your visitors. I have lost count of the number of times I have spent twenty minutes debugging a header alignment issue that only appeared because I was logged in.

The extension lets you hide the admin bar on specific sites or globally, while keeping every shortcut one click away in the browser toolbar. Two clicks to bring the full bar back. No trip to your profile settings, no toggling the "Show Toolbar" checkbox and waiting for a page reload.

That alone would be worth installing. But the extension goes further.

Site detection and management

The toolbar icon tells you whether the site you are currently viewing runs WordPress and whether you are signed in to it. If you manage multiple client sites, this eliminates the constant "wait, is this one on WordPress or Squarespace?" dance. The extension also remembers every site you sign into and keeps them accessible from a single dropdown, stored locally in your browser.

On a site you manage, the extension gives you direct shortcuts to the editor for the exact post, page, taxonomy, or template you are currently viewing. No more copying the URL, opening a new tab, navigating to the dashboard, finding the post in the list, and clicking Edit. One click from the toolbar takes you straight to the editor for what you are looking at. On block themes, template-backed pages open in the Site Editor instead of the post editor, which is the correct behavior.

The developer tools are the real reason to install

The site management features are convenient. The developer tools are where the extension earns its place in your daily workflow.

Block boundary outlines. The extension draws visible outlines over the rendered page showing where each block starts and ends. If you have ever tried to figure out which block is producing a particular piece of layout on the front end, you know how much time this saves. Instead of opening the editor, clicking through blocks, and guessing from the sidebar, you can see the structure directly on the page.

Phone-sized preview window. This opens as a real browser window at a phone width, not a DevTools responsive emulation. The difference matters because real windows behave differently from emulated viewports in subtle ways that affect layout testing.

Reload with cache busting. If you have ever appended ?nc=1234 to a URL by hand while chasing a stale stylesheet, this replaces that habit with a single click. The extension reloads the page with a cache-busting parameter, which forces the browser to fetch fresh assets. On sites running aggressive page caching or CDN rules, this is the fastest way to confirm whether a change actually deployed or whether you are looking at a cached version.

Clear cookies and local storage. Two clicks to wipe cookies and local storage for the site you are on, without opening DevTools or a private window. This pairs with the cache-busting reload for diagnosing stale CSS on builder-based sites. When an Elementor site is serving old styles after an edit, the fastest way to prove it is a cache problem rather than a code problem is a clean reload with storage cleared.

Privacy and open source

The extension runs entirely locally. No tracking, no data collection, no phone-home behavior. For an extension that signs into client sites through an agency account, that is not a minor detail. It is the difference between installing it and not installing it.

The project started as an independent side project and was adopted as an official WordPress project with support from Matt Mullenweg. Fabian Kägy, a core WordPress contributor at Fueled, shaped its design and architecture. The code is open source on GitHub and open to contributions.

Who should install this

If you manage one WordPress site and rarely open the editor, the extension is nice to have but not essential. The admin bar hiding and cache-busting reload are useful, but you can live without them.

If you manage multiple WordPress sites — as a freelancer, agency developer, or anyone with a personal site and a client site or two — install it today. The site launcher alone saves a few minutes every day. The block boundary outlines and cache-busting reload save a few more. The admin bar hiding eliminates an entire class of layout debugging false positives.

If you are an agency managing fifteen or twenty client sites, this is not optional. The combination of site detection, login status visibility, per-site admin bar control, and one-click editor access compresses the daily overhead of context-switching between sites in a way that no plugin can match, because the extension operates at the browser level rather than the site level.

What it does not do

The extension does not replace a proper development environment. It does not give you database access, file editing, or server-level tools. It does not work offline. It does not sync settings across devices (everything is stored locally in the browser). And it does not currently support Firefox, though the open-source codebase means a Firefox port is technically straightforward.

It also does not replace the need for a staging environment. The cache-busting reload is a diagnostic tool, not a deployment workflow. If you are still pushing changes directly to production and hoping the cache clears, the extension will help you catch problems faster, but it will not fix the underlying process.

The bottom line

This is a small tool that solves real problems. The admin bar has been a source of layout debugging headaches since the block editor shipped. The site management overhead of switching between multiple WordPress installs has been a tax on agency developers for years. The cache-busting reload has been a manual URL hack for as long as WordPress sites have used page caching.

The extension addresses all three in a single install, it runs locally with no privacy cost, and it is free and open source. Install it from the Chrome Web Store or the Mac App Store, give it a day, and you will wonder how you worked without the cache-busting reload.