On 13 August 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.
This is not a plugin. Nothing gets installed on your site, nothing runs on your server, and there is no performance cost to your visitors. It sits in your browser and changes how you work on WordPress sites rather than how those sites behave. That distinction is the whole point, and it is why a few things in it are possible that a plugin could never do.
The problem it was built to solve
The admin bar is genuinely useful and genuinely in the way. 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.
What you actually get
- Admin bar control per site or globally. Hide it everywhere, or only on the sites where it causes problems.
- WordPress detection at a glance. The toolbar icon tells you whether the site you are on runs WordPress and whether you are signed in to it. Useful when you are looking at a prospect’s site and want to know what you would be inheriting.
- Context-aware editor shortcuts. 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. It remembers the sites you sign in to and keeps them one click away from anywhere, stored locally in your browser.
The developer tools are the part worth installing for
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.
- Block boundary outlines drawn over the rendered page, so you can see the block structure on the front end instead of guessing from the editor.
- A phone-sized preview window that opens as a real window, not a devtools emulation.
- Reload with cache busting — the one we reach for most. If you have ever appended
?nc=123to a URL by hand while chasing a stale stylesheet, this replaces that habit. - 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: everything stays on your device
Worth stating plainly, because browser extensions have earned their bad reputation. The extension reads the page in front of it to work out what it is looking at, and asks the site directly when it needs more than the page can tell it. Your preferences and your list of signed-in sites stay in your browser. There is no tracking and no analytics of any kind, and the source is on GitHub if you want to verify that rather than take it on trust.
That is a meaningfully better posture than most of the third-party WordPress toolbar extensions people have been installing for years, several of which phone home with every site you visit.
Who should install it, and who should not bother
Install it if you build or maintain WordPress sites. If you are moving between five or fifty client sites, the launcher and the context-aware editor links save real minutes every day, and the cache-busting reload alone justifies the install.
It is useful but optional for content editors. If you write on one site and never leave the dashboard, you are not the target user. The admin bar is not hurting you.
Two honest limitations. First, block outlines only tell you something on block-based content. If your site is built in Elementor or another page builder — which covers most of what we hand over — that feature does nothing for you, and the rest of the extension still does. Second, Firefox is not supported at launch. It is Chrome, Chromium browsers, and Safari on macOS for now.
It is also worth saying what this is not. It is a convenience layer, not a testing environment. It does not replace a staging site, and a cache-busting reload is not proof that an update is safe. The things that actually protect a client site are still a real maintenance routine and testing changes somewhere that is not production.
How we are using it
Two things changed in our workflow in the first day. Sticky-header and scroll-animation QA got faster, because we are now checking layouts without an admin bar shifting everything down by 32 pixels. And the WordPress detection indicator has quietly become an audit tool — when a prospect sends a URL, we know within a second whether we are looking at a WordPress build before opening anything else.
It is a small tool. It does not change what WordPress can do. But it removes friction from things we do forty times a day, and that is usually where the real time goes.
Frequently asked questions
What is the WordPress browser extension?
It is an official, open source browser extension released by WordPress on 13 August 2026. It hides the WordPress admin bar while keeping its shortcuts available in the browser toolbar, shows whether the site you are viewing runs WordPress, gives quick access to your own sites, and adds a small set of developer tools such as block outlines and cache-busting reload.
Which browsers does it support?
Chrome and other Chromium-based browsers through the Chrome Web Store, and Safari on macOS through the Mac App Store. Firefox is not supported at launch.
Does it slow down my website?
No. It is a browser extension, not a plugin. Nothing is installed on your site and nothing runs on your server, so there is no effect on your visitors or on your page speed scores.
Does the extension collect my data?
No. According to the official announcement it works on your device, your preferences and signed-in site list stay in your browser, and there is no tracking or analytics of any kind. The source code is published on GitHub.
Is it useful if my site is built with Elementor?
Mostly yes. The admin bar control, site launcher, editor shortcuts, cache-busting reload and storage clearing all work regardless of how the site is built. The block boundary outlines are the exception, since they only describe block-based content.