GNOME’s official Extensions app manages what you already have installed, but browsing and adding new extensions still means a trip to extensions.gnome.org and a browser add-on.
GNOME Extension Manager fixes that by building a Browse tab straight into a native desktop app. You get to find, install and manage GNOME Shell extensions without touching a web browser.
What Extension Manager does
Extension Manager is a native GTK4 and libadwaita app built by developer Matthew Jakeman as a companion to GNOME’s Extensions app. It gives you two tabs: Installed, listing every extension on your system, and Browse, which searches the same catalog as extensions.gnome.org from inside the app.
That second tab is the real difference. GNOME’s built-in Extensions app toggles and configures extensions you already have, but it cannot find new ones. Extension Manager searches, installs, updates and removes extensions end to end, no browser required.
GNOME Extension Manager vs GNOME Extensions
GNOME ships an Extensions app by default on most distros, so it is fair to ask why bother installing a second tool. The two overlap on core management, both enable, disable, configure and remove extensions you already have. Extension Manager adds the ability to search and install from the same catalog the website uses, all inside the app window.
It also lets you toggle a light, dark or system-matched theme, while the stock Extensions app just follows your system theme. GNOME 40 folded extension settings out of GNOME Tweaks and into Extensions on its own, which is part of why Extension Manager exists, since browsing and installing stayed the one gap the official app never filled.
GNOME’s own Extensions app is still the one that handles background update checks reliably on older GNOME versions, so keeping both installed is common advice rather than a compromise. Pick Extension Manager if you install extensions often and want to skip the browser step. Pick the stock app if you rarely touch extensions and just need occasional toggles.
| Feature | GNOME Extensions | Extension Manager |
|---|---|---|
| Enable or disable installed extensions | Yes | Yes |
| Browse and search new extensions | No, needs a browser | Yes, built in |
| Install extensions without a browser | No | Yes |
| Theme control (light, dark, system) | Follows system only | Toggleable |
| Background update checks on GNOME 40 to 42 | Yes | Needs Extensions app installed too |
| Installed by default | On most distros | No, separate install |
Install Extension Manager on Ubuntu and Debian
Ubuntu has shipped Extension Manager in its official repositories since 22.04, and Debian testing and unstable currently carry version 0.6.5. Open a terminal, update your package index and install the app with apt.
sudo apt update
sudo apt install gnome-shell-extension-manager
This pulls the gnome-shell-extension-manager package, the same app whether you get it through apt, Flathub or Fedora’s dnf, just packaged natively instead of sandboxed. Debian’s stable release currently carries the slightly older 0.6.3.
If you want the newest release on Debian stable, Flatpak is the faster route (see below). Once installed, launch it from the Activities overview by searching “Extension Manager”, or run extension-manager directly from a terminal.
Install Extension Manager on Fedora
Extension Manager sits directly in Fedora’s own repositories now, not just on Flathub, so dnf installs it with no extra setup.
sudo dnf install gnome-shell-extension-manager
If you would rather use a graphical route, open the Software app, search for Extension Manager and click Install. This pulls the Flathub build if you already have Flathub enabled, or the RPM build otherwise.
Fedora also ships a separate gnome-extensions-app package for GNOME’s own built-in Extensions tool, and the two coexist without conflict, the same as on Ubuntu.
Install Extension Manager on Arch Linux
Extension Manager lives in the Arch User Repository (AUR, the community package repo for software not in Arch’s official repos) under the package name extension-manager, so you need an AUR helper such as yay or paru to build it.
yay -S extension-manager
There is also an extension-manager-git package for anyone who wants the latest commits rather than a tagged release, though it depends on libadwaita 1.5 or newer and is more likely to break between updates.
If you are still choosing between AUR helpers, our guide to Paru covers the newer Rust-based alternative to yay. Once built, the app appears in your launcher as Extension Manager.
Install Extension Manager with Flatpak
Flatpak (a sandboxed, distro-independent package format) works on any distro that supports Flathub, which makes it the most reliable option if your distro’s repos carry an old version or none at all.
Add Flathub first if you have not already. Our Flatpak setup guide walks through enabling it on Ubuntu, Fedora and Arch. Then install the app with a single command.
flatpak install flathub com.mattjakeman.ExtensionManager
The Flathub build stays close to upstream, so this is usually the fastest way to reach a new release, often within days of it landing on GitHub.
Flathub currently lists the app pulling more than 66,000 downloads a month, one of the more actively used GNOME desktop tools on the platform.
Browse and install extensions
Open Extension Manager and switch to the Browse tab to search the same catalog as extensions.gnome.org.
- Type a keyword or extension name into the search box. Extension Manager matches on the extension’s name and author, so if a search term returns nothing, try the developer’s name instead.
- Click a result to open its details pane, which shows a description, screenshots when the developer supplied them and a compatibility badge for your GNOME Shell version.
- Click Install and confirm in the dialog. The extension activates immediately, no restart or browser reload needed.
Extension Manager automatically filters results to builds made for your installed GNOME Shell, the same version check the website performs, so you should not run into broken extensions unless you deliberately turn that check off. Listings can also show screenshots and ratings when the developer has supplied them, details GNOME’s own Extensions app does not surface. Popular picks like Tiling Shell or GSConnect install through the same Browse flow.
Manage installed extensions
Switch to the Installed tab to see every extension on your system, including ones your distro pre-installs such as Ubuntu’s Dash to Dock or Ubuntu AppIndicators.
- Toggle the switch next to any extension to enable or disable it instantly, no logout required for most extensions.
- Click the gear icon on an extension that has one to open its own settings panel, such as the audio device renamer covered in our quick settings guide.
- Click an extension’s name to see its version, GNOME Shell compatibility range and a remove option for anything you installed yourself.
- System extensions bundled by your distro show a lock icon and cannot be removed here, only disabled.
Extension Manager separates system and user extensions clearly, which helps when you need to tell your distro’s defaults apart from anything you added yourself while troubleshooting. If you would rather hide an app from your grid than remove an extension, our App Hider guide covers a related use case.
Use unsupported extensions with Extension Manager
Some extensions lag behind the newest GNOME Shell release, and GNOME Shell blocks any extension not explicitly marked compatible with your version. Extension Manager respects this check by default, but you can turn it off if you want to try an extension anyway.
gsettings set org.gnome.shell disable-extension-version-validation true
Unsupported extensions will likely behave oddly and can introduce real instability, so only disable the check for extensions you trust and plan to remove if something breaks. Reset the setting once you are done testing.
gsettings reset org.gnome.shell disable-extension-version-validation
Turn the check back on before filing a bug report against GNOME Shell itself, since a disabled version check is a common cause of reports that turn out not to be real bugs.
Fix common Extension Manager issues
Most problems trace back to one of three causes: browser integration, a GNOME Shell version mismatch or update behavior on older releases.
- Extensions install from the app but not from extensions.gnome.org in a browser. Install the browser connector package,
gnome-browser-connectoron current distros or the olderchrome-gnome-shellon legacy releases, then reload the website. - Updates never appear even though a newer version exists on the website. On GNOME 40 through early 42, Extension Manager relies on the official Extensions app for background update checks. Keep
gnome-shell-extensionsorgnome-extensions-appinstalled alongside it. - Search returns nothing for an extension you know exists. Try the author’s username instead of the extension name, since Extension Manager’s search index sometimes misses partial name matches.
- An extension installs but never shows up. Log out and back in on Wayland sessions. The Alt+F2 then r shell restart only works on X11.
If none of these fix it, the project’s GitHub discussions page covers less common cases and active bug reports.
Key takeaways
- Extension Manager adds a Browse tab so you can find and install extensions without a browser.
- Ubuntu, Debian and Fedora carry it in their repos as gnome-shell-extension-manager.
- Arch users need the AUR, the package is extension-manager not gnome-shell-extension-manager.
- Flatpak (com.mattjakeman.ExtensionManager) gets the newest release fastest on any distro.
- Keep GNOME’s own Extensions app installed too, it still handles updates on older GNOME.
- The Installed tab locks system extensions from removal, only disabling is allowed.
- Search by developer name if an extension’s own name returns nothing.
- Wayland sessions need a full logout, not Alt+F2, for new extensions to load.
Frequently asked questions
Is GNOME Extension Manager official?
No. It is a community-built app by developer Matthew Jakeman, distributed on Flathub and packaged separately by Ubuntu, Debian, Fedora and the AUR. GNOME’s own official tool is called Extensions.
Do I still need GNOME’s Extensions app if I install Extension Manager?
On GNOME 40 through early 42, yes, since Extension Manager relies on it for background update checks. Newer GNOME versions handle updates fine on their own.
Why can’t Extension Manager find an extension by name?
Its search index sometimes misses partial name matches. Try the developer’s username instead, or search on extensions.gnome.org directly and copy the exact extension name.
What is the Arch package name for Extension Manager?
extension-manager, available only through the AUR. Install it with an AUR helper like yay or paru, since Arch’s official repositories do not carry it.
Does Extension Manager work on Wayland?
Yes, fully. New extensions may need a full logout and login to activate, since Wayland sessions cannot reload GNOME Shell with the Alt+F2 shortcut that works on X11.
Can I still install extensions from the GNOME Extensions website instead?
Yes, once you install the gnome-browser-connector package (or chrome-gnome-shell on older distros) and the matching browser add-on for Firefox or Chrome.
Is Extension Manager safe to use?
It only installs extensions from the same official catalog as extensions.gnome.org and does not host separate packages, so its safety profile matches GNOME’s own website.
Can Extension Manager update all my extensions at once?
Yes. Extensions with an available update show an update button in the Installed tab, and the app checks the catalog for new versions each time you open it.
Conclusion
Extension Manager will not replace GNOME’s own Extensions app on every GNOME version, but for browsing and installing new extensions without a browser tab open, it is the more direct tool.
Install it through your distro’s package manager first, and reach for Flatpak only if your repos are stuck on an old release.