Chrome’s extension ecosystem is one of its biggest strengths and one of its most common sources of problems. Extensions add genuine capability — ad blocking, grammar assistance, password management, developer tools — but each one also adds background activity, memory overhead, and permissions access that compound with every additional extension you install. We go deeper on the whole subject in our How to Manage Google Chrome.
Most Chrome performance problems, many privacy concerns, and a surprising number of browser crashes trace back to extension issues. The practical implication: managing extensions isn’t optional housekeeping. It’s directly tied to how well Chrome performs on a day-to-day basis.
The extension management hub
chrome://extensions is where you manage everything: install, remove, enable, disable, and configure extensions. Each extension card shows:
- The extension name and icon
- A brief description of what it does
- The on/off toggle (disable without removing)
- Developer mode information (in developer mode)
- A “Details” button that shows permissions, source, and additional options
- A “Remove” button
The “Details” page for each extension is more important than the main card. It shows: which sites the extension can access, whether it was installed from the Web Store or side-loaded, and options like allowing in Incognito mode or restricting to specific sites.
Finding extensions that are causing problems
Chrome’s Task Manager (Shift+Esc) lists every extension as a separate process with its memory and CPU usage. Sort by Memory descending — an extension using 200MB or more is worth investigating. Sort by CPU — an extension consistently above 5% CPU while you’re just reading text is running something heavy in the background.
For identifying which extension is causing crashes or slowness without the Task Manager: Incognito mode (Ctrl+Shift+N) disables all extensions by default. If Chrome is fast and stable in Incognito but slow or unstable normally: an extension is the cause. Go to chrome://extensions → disable all → re-enable one at a time, testing Chrome between each. The extension that restores the problem is the culprit.
Extension permissions — what to look for
When you install an extension, Chrome shows what permissions it requires. After installation: chrome://extensions → Details on any extension → “Permissions” section shows the current permission scope. The relevant categories:
- “Read and change all your data on all websites”: the broadest permission. The extension can see and modify the content of every page you visit. Ad blockers and password managers legitimately need this. A calculator extension or colour picker doesn’t.
- “Read browsing history”: the extension can see every URL you’ve visited. Very few extensions need this.
- “Manage downloads”: can see and control your downloads.
- “Read and change data on [specific sites]”: narrower than “all sites” — acceptable for site-specific tools.
Extensions with broader permissions than their function requires are worth scrutinising. An extension that claims to change your toolbar colours shouldn’t need access to all your browsing data.
Extension access modes — the underused control
Right-click any extension icon in the Chrome toolbar → “This can read and change site data” → three options:
- On all sites: the extension runs on every page (default for many extensions)
- On specific sites: you manually list which sites the extension can access
- When you click the extension: only activates when you click the icon — no background activity on pages you don’t actively trigger it on
“When you click the extension” is the right setting for extensions you use occasionally rather than constantly. A screenshot tool doesn’t need to run on every page; it only needs to run when you click it. Switching these extensions to on-click mode reduces background activity without removing any functionality.
Extension groups and Chrome’s toolbar management
Extensions appear in the Chrome toolbar as icons (or hidden in the puzzle-piece menu). The puzzle-piece icon (⊞) at the top right shows all installed extensions, with a pin option to add frequently-used ones to the visible toolbar.
For organisations managing Chrome across many machines: the Chrome Web Store has a curated review process, but extensions can still be removed from the Store after installation. Chrome periodically scans installed extensions and will disable or remove ones that violate updated policies. If an extension disappeared from your installation: it was likely removed by the Store for policy violation — a signal that extension was worth removing anyway.
Our guide on Chrome performance troubleshooting covers how extensions contribute to slowness in the context of broader performance diagnosis, and our Chrome privacy settings covers extension permissions as part of the broader privacy picture. For extension security reviews and the Web Store review process, the Chrome Web Store shows ratings, review counts, and developer information that help evaluate extensions before installing.
Installing extensions safely
The Chrome Web Store is the only safe source for Chrome extensions. Side-loading (installing from outside the Web Store, typically as a .crx file downloaded from a website) bypasses Google’s review process and is a common vector for malicious extensions. Chrome limits what side-loaded extensions can do, but “limited” isn’t “safe.”
When evaluating a Web Store extension:
- Check the user count — extensions with fewer than a few thousand users have less community scrutiny
- Check the last update date — an extension unmaintained for 2+ years may have compatibility or security issues with current Chrome versions
- Read the reviews specifically for recent negative experiences — look for patterns, not just overall star rating
- Check who the developer is — established companies and reputable developers are lower risk than anonymous developers
- Review the permissions requested — reject extensions that request far more than their stated function requires
Extension updates
Chrome updates extensions automatically in the background. This is generally good, but occasionally an extension update introduces a regression — something that worked yesterday breaks after an update. If Chrome’s behaviour changed suddenly without you doing anything: an extension auto-updating is often the cause.
You can check update timing by enabling Developer mode in chrome://extensions → “Update” button at the top forces an immediate update check. For diagnosing which extension updated and may have caused a problem: there’s no built-in update history. Third-party extension management tools like Extension Manager can show update timestamps. Without these tools: disable extensions one at a time until the problem stops to identify the recently-updated culprit.
| Extension problem | Best approach |
| Slow Chrome after installing an extension | Shift+Esc → check extension’s memory/CPU; disable and test |
| Chrome stable in Incognito, not normally | Disable all extensions → re-enable one at a time |
| Extension requesting excessive permissions | Check if function justifies the permission; find alternative if not |
| Extension you don’t actively use daily | Disable (not remove) to reduce background activity |
| Extension no longer in Chrome Web Store | Remove it — likely removed for policy violation |
| Specific extension only needed on some sites | Right-click icon → restrict to “When you click the extension” |
A good mental model for extensions: every one you install is software running inside your browser with varying levels of access to your web activity. The question isn’t “does this extension have a feature I want” but “does the benefit of this feature outweigh the access I’m granting and the background activity it adds?” That framing makes the periodic audit of your extension list straightforward — keep what adds more than it costs, remove what doesn’t.
The practical extension limit
There’s no hard limit on how many Chrome extensions you can install, but there’s a practical one. Each extension adds to Chrome’s memory footprint and startup time. Extensions with content scripts run code on every page you load. On machines with 8GB RAM running Chrome alongside other applications: the cumulative overhead of 15-20 active extensions becomes measurable. On 16GB+: less of a concern, but still visible in Shift+Esc.
A reasonable target for most users: 5-10 active extensions covering your actual needs (ad blocking, password manager, 2-3 productivity tools, developer tools if relevant). Extensions installed for a specific one-time task and forgotten afterward are pure overhead. An annual cleanup of the extension list — removing anything you haven’t consciously used in the past three months — keeps Chrome running cleanly without giving up useful tools.
Manifest V3 and what it means for extensions
Chrome’s extension platform is transitioning from Manifest V2 to Manifest V3. This technical change affects how extensions can operate in the background. Manifest V3 extensions are more constrained in what background activity they can perform, which in theory means less resource consumption but in practice means some extensions that relied on background capabilities need to redesign their approach.
If an extension you use shows a warning in chrome://extensions about being “deprecated” or “no longer supported”: it hasn’t been updated to Manifest V3. These extensions continue to work for now but Chrome may eventually stop supporting them. Check the extension developer’s page or the Web Store listing for a Manifest V3 version or update status. For popular extensions: developers have generally updated or are in the process of updating; for unmaintained extensions: a replacement may be necessary.
Syncing extensions across devices
With Chrome Sync enabled: your extension list syncs across devices. When you install an extension on your laptop, Chrome on your phone downloads it from the Web Store automatically (mobile Chrome supports many but not all desktop extensions). This is convenient for maintaining a consistent toolset across devices, but it means a problematic extension installed on one device propagates to all of them.
If you want different extension sets on different devices (a full development toolkit on desktop, minimal extensions on mobile): turn off extension sync for specific devices. chrome://settings/syncAndGoogleServices → Manage what you sync → Customize → “Extensions” → off for the device where you want independent extension control. The extensions already installed on that device stay; they just no longer sync from or to the account.
Enterprise extension management
Google Admin Console lets IT departments manage extensions across a Chrome fleet: force-installing required extensions, blocking extensions by ID or by category, pinning specific extensions to the toolbar. Managed Chrome installations may show extensions that can’t be removed (force-installed by policy) alongside user-installed ones.
From an end-user perspective: if an extension appears in chrome://extensions with a building icon rather than the standard remove option: it’s policy-managed and can’t be removed. If an extension you need isn’t installable because it’s blocked by policy: IT can add it to the allowlist. Both situations require IT involvement rather than user-level configuration changes.
Extensions represent an important layer of Chrome’s extensibility — the reason Chrome became the dominant browser is partly its extension ecosystem, which genuinely expands what the browser can do. Managing that ecosystem thoughtfully means getting the capability benefits without the performance and privacy costs that come from accumulating extensions without review. The discipline of “install intentionally, review regularly, remove anything that’s not actively useful” keeps Chrome’s extension layer working for you rather than against you.
Malicious extensions — signs and removal
Extensions that behave maliciously tend to show specific patterns: pages are modified in unexpected ways (ads appear on sites that shouldn’t have them, content is altered, or text is replaced with sponsored links), searches redirect through an intermediate page, or Chrome opens new tabs without you doing anything. These are signs of extension-based adware or hijacking.
If you suspect a malicious extension: run Chrome’s cleanup tool (chrome://settings/cleanup on Windows), then go to chrome://extensions and look for any extension you don’t recognise or didn’t deliberately install. Remove it immediately. Then run a full settings reset (chrome://settings/reset) to clear any configuration changes the extension made, and check chrome://settings/searchEngines to ensure the default search engine hasn’t been changed to an unfamiliar one.
Prevention: never install extensions from links in emails, pop-up ads, or social media posts telling you to “install this extension to access content.” These are consistently malicious. Extensions should always be installed from the Chrome Web Store by searching for them directly, not by following external links that redirect to the Store. The extra 30 seconds to search properly versus clicking a link prevents the most common vector for malicious extension installation. Related: How to Manage Chrome Site Permissions.
Finally: if you want a quick extension health check without doing a full audit, open Shift+Esc → look for extension processes consuming memory or CPU that seem disproportionate to what those extensions do. A small utility extension using 150MB of RAM is a red flag. A comprehensive ad blocker using 80MB is expected. This sanity check, done occasionally, keeps extension resource usage within reasonable bounds and often catches problems before they become noticeable slowdowns. If this sounds familiar, How to Manage Chrome Downloads is worth a look.
