Does it send the list of my extensions anywhere?

No. The extension makes no network request at all — its security policy allows it to connect only to itself, and the build fails if that ever changes. The list is read from Chrome each time you open it and never stored.

Why does it need permission to manage my apps, extensions and themes?

That permission is the whole product: it is how the extension lists what is installed, turns extensions on or off when you ask, and removes one when you choose Remove. Chrome asks you to confirm every removal in its own dialog, so nothing can be removed silently — and it never changes another extension's own settings.

What does 'Only this group' do to extensions that are in no group?

It turns them off, along with everything else outside the group — except the ones you locked. Lock the extensions you always want on, like a password manager, and every group action leaves them alone. Undo puts everything back.

Will my groups be on my other computer?

If you have Chrome sync on, yes: groups and locks are kept in Chrome's own sync storage. Extensions from the Chrome Web Store have the same id everywhere, so they line up; an unpacked build only matches on another computer if it lives at the same path or its manifest pins a key.

Why would a site rule need to read my browsing history?

That is Chrome's wording for the tabs permission, which lets an extension see the addresses of your open tabs. A rule needs exactly that to know when one of its sites is open. It is asked for only when you create your first rule, the addresses are compared with your rules on your computer and never stored or sent, and deleting your last rule gives the permission back.

Why does chrome://extensions say an extension was disabled by this one?

Since Chrome 155, an extension switched off by another one is labelled with the name of the one that did it. That is Chrome being transparent about who switched it — turn it back on from the popup or from chrome://extensions as usual.

Chrome extensionManifest V3In development

Extgroups

Group your extensions. Switch a whole group on or off.

Chrome lists your extensions one at a time and switches them one at a time. Extgroups sorts them into groups you define — plus four it works out by itself, like your developer builds — and turns a whole group on or off in one click, with undo. The list of what you have installed never leaves your browser: the extension makes no network requests at all.

It isn't on the Chrome Web Store yet. Leave an address and you'll hear once — the day it is.

Price: Free
Account: None
Chrome permissions: 3
Leaves your browser: 1 thing
Surfaces: 6
Policy updated: 2026-09-24

How it works

Open it
The popup lists every extension in this Chrome profile, with a switch each, and the cursor already in the search box. Type a word, press ↓, press Space.
Group them
In the manage page, make groups — Work, Research, the ones you are testing — and tick which extensions belong. One extension can be in several groups.
Switch a whole group
Pick a group in the popup: turn it on, turn it off, or keep only that group on. Every group action can be undone, and locked extensions are never touched.

What it does

All of this is the free tier. No account needed for any of it.

Every installed extension in one searchable list, each with its own switch
Groups you define, an extension in as many as you like, kept in Chrome's own sync
Turn a group on, turn it off, or keep only that group on
Lock the extensions no group action should ever touch
Undo for the last ten group actions
Four groups it works out by itself: developer builds, everything that is off, what needs your attention, and what can read every site
Reload every unpacked developer build in one click
A menu on every extension: remove it (Chrome asks you first), or go straight to Chrome's own switches for pinning it to the toolbar and allowing it in Incognito
Site rules: while a tab is open on sites you choose, a group stays on — and only what the rule turned on goes back off
No account and no network requests — the list stays in your browser

See each of these in detail

Who it's for

Install it if

You have a few dozen extensions and switch the same handful on and off by hand in chrome://extensions
You build extensions and keep unpacked developer builds next to the ones from the store
You want a clean browser for a task — only this group on — and everything back afterwards
You would rather a manager of your extensions never talked to a server

Skip it if

You use Firefox — it does not let one extension switch another on or off
You want an extension kept off on one website only — Chrome's own site access settings do that precisely, per site
You have three extensions and never switch them

What leaves your browser

The whole shelf is local-first, so this is the same figure on every sheet: what the extension holds, the line at the edge of your browser, and everything that gets across it.

Inside your browser

The list of what you have installed
Which extensions are on
Your undo history
Everything the popup shows
Your groups, on this computer
The extensions you locked
The addresses of your open tabs, if you use site rules

One thing crosses

Leaves your browser

Your groups, rules and locks→ Chrome sync: Only if Chrome sync is on: Chrome itself carries them to your other computers, the way it carries your bookmarks. The extension makes no network request of its own.

The exact version, clause by clause, is the privacy policy.

What it costs

Everything above is free, and there is no paid tier. All of it runs in your browser and costs nothing to run — and on this shelf, what costs nothing to run is not sold.

What it can't do

The boundaries worth knowing before you install, rather than after.

Chrome decides what can be switched: An extension installed by your organization cannot be turned off, and Chrome keeps some off for good (old Manifest V2 ones, unpacked builds while Developer mode is off). They are shown, greyed, with the reason.
Reloading a developer build reloads its code, not its manifest: Changes to manifest.json — permissions, content security policy, name — still need the reload button in chrome://extensions.
Pinning and Incognito are Chrome's switches: No extension can pin another one to the toolbar or allow it in Incognito, so the row's menu takes you to Chrome's own page for that extension, where both switches are.
Chrome, Edge and Brave only: Firefox lets an extension switch another one on or off only for themes.

Questions

Does it send the list of my extensions anywhere?: No. The extension makes no network request at all — its security policy allows it to connect only to itself, and the build fails if that ever changes. The list is read from Chrome each time you open it and never stored.
Why does it need permission to manage my apps, extensions and themes?: That permission is the whole product: it is how the extension lists what is installed, turns extensions on or off when you ask, and removes one when you choose Remove. Chrome asks you to confirm every removal in its own dialog, so nothing can be removed silently — and it never changes another extension's own settings.
What does 'Only this group' do to extensions that are in no group?: It turns them off, along with everything else outside the group — except the ones you locked. Lock the extensions you always want on, like a password manager, and every group action leaves them alone. Undo puts everything back.
Will my groups be on my other computer?: If you have Chrome sync on, yes: groups and locks are kept in Chrome's own sync storage. Extensions from the Chrome Web Store have the same id everywhere, so they line up; an unpacked build only matches on another computer if it lives at the same path or its manifest pins a key.
Why would a site rule need to read my browsing history?: That is Chrome's wording for the tabs permission, which lets an extension see the addresses of your open tabs. A rule needs exactly that to know when one of its sites is open. It is asked for only when you create your first rule, the addresses are compared with your rules on your computer and never stored or sent, and deleting your last rule gives the permission back.
Why does chrome://extensions say an extension was disabled by this one?: Since Chrome 155, an extension switched off by another one is labelled with the name of the one that did it. That is Chrome being transparent about who switched it — turn it back on from the popup or from chrome://extensions as usual.

Something else? Write to support — it is one person and a real inbox.

What it can reach

Every permission the extension asks Chrome for, and why. This is the same list a Chrome Web Store reviewer sees beside the manifest.

management: The whole product: reads the list of extensions installed in this Chrome profile, turns them on or off when you ask, and removes one when you choose Remove on it — Chrome then asks you to confirm in its own dialog, so nothing is ever removed silently. It never changes another extension's settings or site access.
storage: Keeps your groups, the extensions you locked, your site rules and the undo history. Groups, locks and rules use Chrome's own sync storage, so they follow your Chrome profile to another computer; nothing is kept anywhere else.
tabs: Optional, and only for site rules: asked for when you create your first rule, handed back when you delete your last. It lets the extension see the addresses of your open tabs, so a rule can tell when one of its sites is open. The addresses are compared with your rules on your computer and are never stored or sent anywhere.