Next-Gen App & Browser Testing Cloud
Trusted by 2 Mn+ QAs & Devs to accelerate their release cycles

"Find Chrome extensions" can mean two different things: discovering new extensions to install from the Chrome Web Store, or finding extensions that are already installed in your browser. The fastest way to see what is installed is to type chrome://extensions in the address bar; to find new ones, open the Chrome Web Store. This guide covers both, plus where extension files live on disk, how to find an extension's ID, the mobile situation, and how to choose safe extensions.
New to extensions and want to understand what they actually do? See What Are Chrome Extensions? first, then come back here to learn how to locate them.
If you search the official Web Store you will find thousands of extensions. You can streamline that search by browsing categories and filtering by ratings and badges. The current Chrome Web Store lives at chromewebstore.google.com (the old chrome.google.com/webstore address now redirects there). Follow these steps:



If you simply want to see what is already running in your browser, Chrome gives you two places to look: the full Manage Extensions page and the puzzle-piece toolbar menu.
The difference is scope: the puzzle-piece menu is a quick view of extensions that can act on the current page, while chrome://extensions is the complete inventory, including disabled extensions, that you use for detailed management.
Each installed extension lives in a folder named after its extension ID, with a sub-folder for each version. The parent Extensions folder sits inside your Chrome profile directory. The default paths per operating system are:
| OS | Default Extensions path |
|---|---|
| Windows | C:\Users\<You>\AppData\Local\Google\Chrome\User Data\Default\Extensions |
| macOS | ~/Library/Application Support/Google/Chrome/Default/Extensions |
| Linux | ~/.config/google-chrome/Default/Extensions (or chromium for Chromium) |
If you use more than one Chrome profile, replace Default with Profile 1, Profile 2, and so on. To confirm exactly which folder a profile uses and jump straight to it:
Standard Chrome on Android and iOS does not support extensions. There is no chrome://extensions page and no way to install from the Web Store on the mobile app, so if you go looking for an extensions menu on your phone you will not find one.
If you need extensions on a phone, use a Chromium-based browser that supports them: Microsoft Edge Canary on Android and Yandex Browser can install many Chrome extensions and manage them from their own extensions menu. (Kiwi Browser was a popular option for this but was discontinued in 2025, with its extension support folded into Edge Canary for Android.) Google has also been piloting extension support in Chrome for Android, so the situation may change. Verify the current status in your browser before assuming a feature is available.
Extensions can alter the DOM, inject scripts, block network requests, and change how a page renders, so a web app that works perfectly for users with no extensions may break for someone running an ad blocker, a password manager, or an accessibility tool. That is why QA teams verify how extensions affect behaviour and confirm pages render and work consistently across Chrome, Edge, Firefox, and Safari. You can run those checks at scale with Cross Browser Testing Cloud, which runs your app on 3,000+ real browser and OS environments and also offers its own Chrome extension for quick live testing.
Type chrome://extensions in the address bar and press Enter to open the Manage Extensions page, which lists every installed extension with its toggle, Details, and Remove options. For a quick view of just the active extensions, click the puzzle-piece icon at the top-right of the toolbar.
Inside your Chrome profile, in a folder named after each extension's ID. On Windows that path is C:\Users\<You>\AppData\Local\Google\Chrome\User Data\Default\Extensions, on macOS it is ~/Library/Application Support/Google/Chrome/Default/Extensions, and on Linux it is ~/.config/google-chrome/Default/Extensions. See the per-OS table above for details.
Open chrome://extensions, enable Developer mode in the top-right, and the 32-character ID appears under each extension. That same ID is the folder name Chrome uses to store the extension on disk, which makes it easy to match an extension to its files.
Not in standard mobile Chrome, which does not support extensions at all. Use a Chromium-based mobile browser such as Microsoft Edge Canary on Android or Yandex Browser, which can install and manage many Chrome extensions from their own menus. (Kiwi Browser, formerly popular for this, was discontinued in 2025 and its extension support moved into Edge Canary.)
Chrome does not keep an uninstall history, but you can reinstall from the Chrome Web Store. The listing URL contains the extension's ID in the form /detail/<name>/<id>, so searching the store for the name will take you back to the same extension.
It may be disabled, unpinned, or a hidden/component extension. Check the toggle on chrome://extensions, click the puzzle-piece icon to surface unpinned items, and open chrome://system and expand extensions to list component and hidden extensions that don't appear in the normal UI.
KaneAI - Testing Assistant
World’s first AI-Native E2E testing agent.

TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance