Chrome Extensions Explained: How to Install, Manage, and Choose

Chrome extensions are the small programs that turn a plain browser into whatever you actually need: a grammar checker, an ad blocker, a translator, a tab manager. Chrome has more of them than any other browser, and that’s both the appeal and the catch — a Chrome extension you installed two years ago for one project can keep quietly running, using its permissions, long after you’ve forgotten it exists.

This guide covers what a Chrome extension is, how to install, manage, and remove one, why some extensions stopped working in 2025 and 2026, and how the same Chrome Web Store extensions behave on a Chromebook or inside Edge, Brave, and Opera. It also covers where Chrome’s own built-in tools already do the job, so you’re not adding an extension for something the browser handles on its own.

What Is a Chrome Extension?

A Chrome extension is a small program you install from the Chrome Web Store that changes what Chrome does or how it looks, without being a full standalone app. Chrome’s own developer documentation frames it plainly: extensions “enhance the browsing experience by customizing the user interface, observing browser events, and modifying the web.”

People search for this idea a dozen different ways — chrome extension, browser extension chrome, chrome extensions browser, chrome chrome extensions, chrome extensions extension — and they all land on the same thing: a small add-on that plugs into Chrome’s toolbar or background and does one specific job.

Every extension is built around a file called manifest.json, described as “the only required file that must have a specific file name.” It sits in the extension’s root folder and records its metadata, the resources it needs, and which files run in the background or on the page. Permissions are declared in that same manifest (things like access to your bookmarks, your open tabs, or a specific website) and Chrome only shows a warning for permissions it considers meaningful. For example, the “activeTab” permission grants temporary access to the current tab with no warning shown at all, while “bookmarks” triggers “Read and change your bookmarks,” and “geolocation” triggers “Detect your physical location.”

That permission model is the whole point: an extension for Chrome can’t just reach into anything it wants. It has to ask, in writing, in the manifest, and Chrome surfaces the meaningful asks to you before install.

Extensions vs. apps. An extension isn’t a separate app window. It lives inside Chrome, usually as a toolbar icon, a background script, or both. If you want something that behaves more like a full application with its own window, that’s a different category Chrome calls apps, which are increasingly rare compared to extensions.

How Do I Install a Chrome Extension?

You install a Chrome extension from the Chrome Web Store by finding it and clicking “Add to Chrome.” If the extension needs specific permissions, Chrome shows a dialog first, and you click “Add extension” to approve and finish.

That’s the entire flow for any extension for Chrome, whether it’s a password manager, an ad blocker, or a note-taking tool. There’s no separate download-and-run step like desktop software — the Store handles installation directly inside the browser.

If you’re building or testing your own extension rather than installing one from the Store, you’ll use Developer mode instead — covered in the next section, along with everything else on the management page.

How Do I Manage, Disable, or Remove Chrome Extensions?

You manage every installed Chrome extension from one page: chrome://extensions. Type that into the address bar, and you’ll see a card for each extension with a toggle to enable or disable it, a “Remove” button, and a “Details” link for permissions and settings.

The puzzle-piece icon in the toolbar is the faster route for day-to-day use. Click it to see everything installed, and click the pin icon next to any extension to keep its icon permanently visible in the toolbar instead of tucked inside that menu. Unpin the same way, or right-click the toolbar icon and choose “Unpin.”

To remove an extension entirely, right-click its toolbar icon and choose “Remove from Chrome,” or open chrome://extensions, find its card, and click “Remove.” Either way, Chrome asks you to confirm before deleting it. There’s no undo after that, so if the extension stored anything locally (saved data, settings, a session list), that’s gone with it.

If you’re developing your own extension rather than managing one from the Store, chrome://extensions has a Developer mode toggle in the top right that unlocks “Load unpacked,” letting you test a folder of code directly.

One more page worth knowing: chrome://extensions/shortcuts lets you view and customize keyboard shortcuts for any installed extension that supports them. A developer can suggest up to four shortcuts, but you can add or remap your own from that same page if the defaults don’t fit how you work.

Are Chrome Extension Permissions Safe?

Chrome extension permissions are generally safe if you read what’s being requested, since the dialog exists specifically to flag anything meaningful before install. As Chrome Web Store Help puts it directly, “The warning doesn’t mean the app is dangerous, just that it can be.”

Chrome groups these warnings into three tiers: high alert (access to all your computer’s data and every website), medium alert (access to specific or all websites), and low alert (things like bookmarks, history, tabs, or location). A password manager needing broad site access makes sense; a simple calculator extension asking for the same thing does not.

Chrome also has two built-in checks worth using. Enhanced Safe Browsing gives “warnings about potentially dangerous sites, downloads, and extensions, even ones Google didn’t previously know about.” And Safety Check, reachable at Settings > Privacy and security > Safety Check, can flag risky extensions already installed and walk you through what to do about each one.

The Chrome Web Store’s “Featured” badge is another signal, though not a guarantee. It’s awarded only after manual review by the Chrome team, based on adherence to platform best practices and a clear, detailed store listing — and it can’t be purchased. If you ever run into an extension that seems malicious, its Store listing has a “Flag Issue” link at the bottom you can fill out after signing in.

None of this means every extension needs deep scrutiny. It means the handful that ask for broad access (full site data, every website, your browsing activity) deserve a second look before you approve them.

What Happened to Manifest V2 Extensions?

Manifest V2 extensions no longer run in Chrome at all, because Google fully deprecated the format between 2024 and 2026. If an extension you relied on vanished or greyed out with no setting to fix it, this is almost certainly why.

The timeline matters because it happened in stages, not all at once. Warning banners for Manifest V2 extensions started appearing on June 3, 2024. Chrome began disabling installed MV2 extensions on stable in October 2024, and MV2 was off by default across all channels by March 31, 2025. As of Chrome 138, released July 24, 2025, MV2 extensions were disabled everywhere with no way to re-enable them. The final step came on August 31, 2026, when remaining MV2 listings were permanently removed from the Chrome Web Store.

There’s no bringing an MV2 extension back. As of September 2026, a Manifest V2 extension cannot run in current Chrome under any setting or flag. If you still depend on one, the only path forward is finding a Manifest V3 replacement that does the same job.

This transition is a useful reminder of something people don’t think about until it happens to them: an extension you rely on can disappear for reasons that have nothing to do with you. It might get discontinued, sold, or (like every Manifest V2 extension) simply stop being allowed to run.

Can I Use Extensions for Chromebook (ChromeOS)?

Yes — extensions for Chromebook come from the exact same Chrome Web Store you’d use on Windows or Mac, and they install and behave the same way. Chromebook extensions aren’t a separate category; they’re Chrome extensions running on ChromeOS, which is built around the Chrome browser itself.

That means everything covered above applies directly: you find an extension in the Store, click “Add to Chrome,” approve any permissions, and manage the result at chrome://extensions. Pinning, disabling, and removing all work identically to a Windows or Mac installation, because it’s the same browser codebase underneath.

Where Chromebook extensions can differ is around device management. A school- or work-issued Chromebook often runs under an organization’s policy, which can restrict which extensions are allowed, force-install certain ones, or block the Chrome Web Store entirely. If an extension you expect to see is missing or greyed out on a managed Chromebook, that’s usually a device policy rather than anything wrong with the extension itself, and there’s no user-side setting to override it.

For personal, unmanaged Chromebooks, chromebook extensions carry the same permission model, the same install dialog, and the same Manifest V2 restrictions described earlier — none of that changes based on the hardware. If you’re setting up a Chromebook for the first time and want a fuller walkthrough of adding, organizing, and removing extensions on ChromeOS specifically, the dedicated Chromebook extensions guide goes deeper on device-level quirks.

Same Store, same rules. If you already know how to manage an extension on a Windows PC, you already know how to manage extensions on a Chromebook. The only real differences show up on school- or work-managed devices, where an administrator controls what’s allowed.

Do Chrome Extensions Work on Android or iPhone?

No — Chrome on Android and Chrome on iPhone do not run extensions at all. This is a hard platform limit, not a setting you can toggle on.

If you open the Chrome Web Store from a phone, you won’t see an “Add to Chrome” button the way you would on a computer. Instead, the Store offers “Add to Desktop,” which queues the extension so it installs automatically the next time you sign into the same Google account on a computer. Nothing runs on the phone itself.

This trips people up because other mobile browsers handle extensions differently. Firefox for Android installs extensions directly from addons.mozilla.org, after Mozilla opened its full add-on catalogue to Android in December 2023. Samsung Internet supports extensions on Galaxy phones and tablets through the Galaxy Store. Kiwi Browser, an Android browser built specifically to run Chrome extensions, was a popular workaround for years — but it was discontinued and pulled from Google Play in early 2025, and there’s no official successor.

On iPhone, Safari is the browser that supports extensions, though through a completely different system: they come from the App Store, get enabled per-extension in Settings, and can be turned on or off for individual websites. Chrome for iPhone doesn’t tap into that system at all, since it’s not Safari’s WebKit-based extension model.

• Chrome (Android/iPhone). No extension support; Store offers “Add to Desktop” only.
• Firefox (Android). Installs extensions from addons.mozilla.org directly on the phone.
• Safari (iPhone). Extensions come from the App Store, enabled per-site in Settings.

If you want the fuller picture of what does and doesn’t work across every mobile browser, the Chrome extensions on mobile guide covers it in more depth, including what “Add to Desktop” queues up.

What Built-In Chrome Features Can Replace an Extension?

Several jobs people reach for an extension to solve are already built into Chrome, and skipping the extension means one less thing with permissions to manage. Reading mode, Reading list, and Memory Saver cover a surprising amount of ground on their own.

Reading mode lives in the side panel and strips a page down to text, with read-aloud built in — voice and speed selection, plus play, pause, rewind, and fast-forward controls. Open it by right-clicking the page and choosing “Open in reading mode,” from the Reading mode icon in the address bar, or via More > More tools > Reading mode. The keyboard shortcut is Cmd + Option + R on Mac or Alt + Shift + R on Windows, Linux, or ChromeOS.

Reading list saves a page for later without touching your bookmarks. Go to More > Bookmarks and lists > Reading list, and click “Add tab to reading list,” or right-click any tab and choose the same option. It shows up in a side panel alongside your bookmarks whenever you want it.

Memory Saver deactivates tabs you haven’t touched in a while to free up memory, reloading them automatically when you click back. Set its deactivation level (Moderate, Balanced, or Maximum) at Chrome menu > Settings > Performance, and exclude specific sites you always want kept active. It’s worth reading the Chrome Memory Saver guide if tabs feel sluggish, since it explains what Memory Saver does and doesn’t cover.

One gap worth flagging: Chrome has no native, general-purpose website blocker for everyday users. The only official mechanisms are the enterprise admin policy URLBlocklist on managed devices, and Google Family Link for a child’s account or Chromebook, which offers “Allow all sites,” “Try to block explicit sites,” or “Only allow approved sites.” Everyone else needs a third-party extension for that job.

How Do Extensions Work in Edge, Brave, Opera, and Other Browsers?

Chrome extensions mostly work in other Chromium-based browsers too, though each one handles the store and the install prompt a little differently. Firefox and Safari are the outliers, since they run their own extension formats entirely.

• Edge. Edge has its own Add-ons store, but installing a Chrome Web Store extension triggers a dialog with an “Allow extensions from other stores” toggle you turn on to proceed. See the Edge extensions guide for the full walkthrough.
• Brave. Brave’s own guidance states plainly that “Any extension found in the Chrome Web Store will also work in Brave.” Brave Shields, on by default, already blocks ads and trackers, and Brave says “you won’t need an extension-based ad blocker in Brave” as a result.
• Opera. Opera is Chromium-based and runs CRX (Chrome extension) files directly — installing from the Chrome Web Store is a single “Add to Opera” click, with no separate helper extension needed. Opera also has its own store at addons.opera.com.
• Firefox. Firefox extensions come only from addons.mozilla.org, a separate catalogue with its own review process. Firefox’s Manifest V3 notably kept the blocking webRequest API and event-page background scripts that Chrome’s version dropped.
• Safari. Safari extensions install through the Mac App Store, not a Chrome-style web store, and developers can convert Chrome or Firefox extensions to Safari’s format using Apple’s own Safari Web Extension Converter.

The practical upshot: if you switch from Chrome to Edge, Brave, or Opera, most of your extensions will follow you with a click or two. Switch to Firefox or Safari, and you’re starting over with each one’s own store, even if a compatible version happens to exist there.

Opera GX, the gaming-focused variant of Opera, adds its own extras beyond standard extension support — GX Control for RAM, CPU, and network limiting, a GX Corner news feed, and GX Mods for visual customization. Whether Opera GX has full parity with regular Opera’s Chrome-extension install flow isn’t something Opera documents clearly, so if that matters to you, check the current listing before assuming.

Which Chrome Extensions Are Actually Worth Installing?

The extensions worth keeping are the ones that solve a specific, recurring problem you have — not the ones with the flashiest listing. A handful of well-known examples show the range of what a Chrome extension can responsibly do.

Claude in Chrome, from Anthropic, lets an AI assistant “read, click, and navigate websites alongside you” from the Chrome side panel, with three permission modes ranging from manual approval of every action to skipping approvals entirely. It’s available on paid Claude plans only, not free, and Anthropic’s own safety guidance recommends avoiding it on pages with financial accounts or sensitive company data. Grammarly’s browser extension checks writing across “1 million+ apps and programs,” blocks itself from running in sensitive fields like payment forms and passwords, and says plainly it does “not record every keystroke on your device.” Dark Reader adds dark mode to sites that don’t support it natively and states it “doesn’t send user’s data anywhere.” Google Input Tools adds virtual keyboards and handwriting input for dozens of languages, though it can’t assist inside the address bar or the Chrome Web Store itself. The Zotero Connector saves research sources to your Zotero library “with the click of a button,” and will save directly to zotero.org’s servers even when the desktop app is closed.

Read the full guides for Claude in Chrome, Grammarly, or browse a broader shortlist in best Chrome extensions if you’re building out a fresh setup.

One category worth taking seriously, even though it rarely gets top billing on “best extensions” lists, is a tab or session manager. Chrome itself has no built-in way to save a whole window of tabs as a named, reusable session. That gap is entirely extension territory.

Fewer, well-chosen extensions beat a pile of them. Every enabled extension uses some memory and has standing permissions, whether you’re actively using it or not. It’s worth an occasional pass through chrome://extensions to disable or remove anything you installed once and never opened again.