On August 13, 2026, WordPress released an official browser extension. It is available for Chrome and Chromium-based browsers through the Chrome Web Store, and for Safari on macOS through the Mac App Store. It is open source, it was led by Jake Goldman with support from Matt Mullenweg, and it started life as an independent side project before being adopted as an official one. If you manage WordPress sites, this is worth ten minutes of your time.

The admin bar tradeoff, finally resolved

Every WordPress developer knows the admin bar problem. While you are signed in, it sits across the top of every page, which means the page you are looking at is never quite the page a visitor sees. On any site doing something interesting with the viewport — sticky headers, scroll-triggered animation, full-height hero sections — that offset introduces artifacts. We have all lost twenty minutes hunting a header bug that only existed because we were logged in.

Switching the admin bar off in your profile settings solves the layout problem and creates a new one, because the shortcuts leave with it. The extension is the answer to that tradeoff. It hides the bar on the sites you choose, or everywhere by default, and keeps the shortcuts one click away in the browser toolbar. Bringing the full bar back takes two clicks and no trip to the dashboard.

This is the kind of problem that sits in the background of your workflow for years. You either live with the visual noise or you turn off the bar and lose the convenience. The extension gives you both, and it does it without installing anything on your server.

What the extension actually does

The toolbar icon tells you whether the site you are on runs WordPress and whether you are signed in to it. That alone is useful when you are looking at a prospect's site and want to know what you would be inheriting. On a site you manage, the extension opens the editor for the exact post, page, taxonomy, or template currently in view. On block themes, template-backed pages open in the Site Editor.

A site launcher remembers the sites you sign in to and keeps them one click away from anywhere, stored locally in your browser. No cloud sync, no account, no external service. Your preferences and your site list stay on your device.

The developer tools are the real reason to install

A handful of the tools in here are a better fit for a browser than for a plugin, and they work on every WordPress site you visit rather than only the ones where you can install something.

The extension can draw block boundaries over the rendered page, so you can see the block structure on the front end instead of guessing from the editor. It can open a phone-sized preview window as a real window, not a devtools emulation. It can reload with cache busting — if you have ever appended ?nc=123 to a URL by hand while chasing a stale stylesheet, this replaces that habit. And it can clear cookies and local storage for the site you are on, without opening devtools or a private window.

That last pair matters more than it sounds on builder-based sites. When an Elementor site is serving stale CSS 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. Doing that in two clicks instead of six changes how quickly you diagnose things.

Privacy: nothing leaves your browser

Browser extensions have earned their bad reputation. This one reads the page in front of it to work out what it is looking at, and when it needs more than the page can tell it, it asks the site. Your preferences and the list of sites you sign in to stay in your browser. Nothing is sent anywhere else, and there is no tracking or analytics of any kind.

That is worth stating plainly because it is increasingly rare. An official WordPress tool that does not phone home, does not require an account, and does not collect usage data is a refreshing change from the direction most developer tools have taken.

Who should install it

If you manage even one WordPress site, the admin bar control and the cache-busting reload alone justify the install. If you do client work and regularly need to inspect sites you do not own, the WordPress detection and block boundary outlines will save you time on every new project. If you build with block themes, the context-aware editor shortcuts that open the Site Editor for the exact template in view are genuinely useful.

The extension is not going to change how you build WordPress sites. It is going to change how you interact with them from the browser, which is where most of us spend the day anyway. It is a small tool that solves a real problem, and it does so without adding weight to your site or your workflow.

Install it from the Chrome Web Store or the Mac App Store. The source is on GitHub if you want to see what it does before you trust it.

Sources: