Submit an extension

↑↓ move · ↵ open · Tab filter · Esc close

Chrome extension glossary

Chrome extensions come with their own vocabulary, from Manifest V3 to host permissions to sideloading, and most of it is written for developers rather than everyday users. This glossary explains the terms you'll actually run into while installing, reviewing, or troubleshooting an extension, in plain English, with links to deeper permission guides where it helps.

Last updated

Basics

Extension
A small program you add to Chrome to change or extend what your browser can do, such as blocking ads, checking grammar, or managing tabs.
Chrome Web Store
Google's official marketplace for browsing, installing, and reviewing Chrome extensions and themes.
Toolbar icon
The small icon an extension places next to your address bar, usually the way you open its popup or see its current status.
Popup
The small window that opens when you click an extension's toolbar icon, typically showing its main controls or a quick summary.
Options page
A full settings page an extension provides for detailed configuration, separate from its smaller popup.
Content script
Code an extension injects into the web pages you visit so it can read or change what's on the page, like inserting a button or fixing text.
Background script
Code that runs behind the scenes to handle events, such as a new tab opening, without needing a visible window open.
Browser action vs. page action
Older terms for whether an extension's icon is always active (browser action) or only active on certain pages (page action); both are unified under one model in Manifest V3.
Pinning an extension
Choosing to keep an extension's icon visible in the toolbar instead of tucking it away in the extensions menu.
Incognito access
A separate permission toggle that lets an extension run in Incognito windows, off by default for most extensions.

Permissions

Permission
A specific capability an extension asks Chrome for, such as reading page content or seeing your browsing history, shown to you before or during install.
Host permission
Permission to read or change data on specific websites, ranging from one site to all sites you visit.
activeTab permission
A narrower alternative to broad host access that only lets an extension act on the current tab, and only after you click it.
tabs permission
Access to information about your open browser tabs, such as URLs and titles, beyond what a single active tab shows.
history permission
Access to your browsing history, letting an extension read the list of sites you've visited.
cookies permission
Access to read or change cookies stored by websites, which can include session and login data.
storage permission
Lets an extension save its own settings and data locally using Chrome's storage APIs, separate from your browsing data.
downloads permission
Lets an extension start, monitor, or manage your browser's downloads, such as saving a file automatically.
clipboard permission
Access to read from or write to your system clipboard, used by tools that copy or paste text and images for you.
notifications permission
Lets an extension show desktop notifications outside the browser window, similar to alerts from a website.
declarativeNetRequest permission
A Manifest V3 API that lets an extension block or modify network requests using pre-declared rules, used heavily by ad and content blockers.
scripting permission
The Manifest V3 permission that lets an extension inject or run JavaScript on pages you visit, replacing older script-injection methods.
Optional permissions
Permissions an extension can request only when you use a specific feature, instead of asking for everything up front at install.
Broad host access
Shorthand for an extension requesting access to all or most websites, which we flag explicitly on every listing's Listing Health section.

Manifest V3 and APIs

Manifest
The configuration file, manifest.json, that declares an extension's name, permissions, and behavior to Chrome.
Manifest V3
Chrome's current extension platform, which replaced background pages with service workers and changed how network-blocking and scripting permissions work.
Manifest V2
The older extension platform that Chrome has phased out; extensions still running on it may lose support or stop working.
Service worker
A short-lived background process Manifest V3 extensions use instead of a persistent background page, which can shut down when idle to save resources.
Chrome extension API
The set of programming interfaces, like chrome.tabs or chrome.storage, that let an extension interact with your browser in specific, permission-gated ways.
Web accessible resources
Files inside an extension, such as images or scripts, that it explicitly allows web pages to load directly.
Cross-origin request
A request an extension makes to a website different from the one currently open, which host permissions control access to.

Chrome Web Store

Developer
The person or company that built and publishes an extension, listed on its Chrome Web Store page along with contact or support details.
Listing
An extension's page on the Chrome Web Store, showing its description, screenshots, permissions, and reviews.
Featured badge
A label the Chrome Web Store gives to extensions that meet its technical and policy quality guidelines, though it isn't a guarantee of trustworthiness.
Verified publisher
A developer who has completed Google's identity verification process for publishing extensions, shown on their store profile.
Sideloading
Installing an extension from outside the Chrome Web Store, such as loading unpacked code, which Chrome restricts more heavily than store installs.
Update channel
How an extension receives new versions after install, usually automatically through the Chrome Web Store in the background.
Ownership transfer
When an extension changes hands to a new developer or company, which can also change its behavior, data practices, or permissions over time.

Safety

Privacy policy
A document a developer publishes explaining what data their extension collects and how it's used; we check that it's present and reviewable on every listing.
Data collection disclosure
A Chrome Web Store section where developers declare what categories of user data their extension collects, such as browsing activity or personal info.
Malware or malicious extension
An extension that behaves deceptively or harmfully, such as stealing data or injecting unwanted ads, and that Chrome or Google may remove from the store.
Extension removed from the store
A listing that no longer appears on the Chrome Web Store, often due to a policy violation, abandonment, or a developer's own decision to pull it.
Permission creep
When an update adds new, broader permissions to an extension that weren't part of its original request, worth rechecking after any major update.
Listing Health
A set of freshness and transparency signals we check on every review, such as recent updates and a linked privacy policy; it's not a security audit.
Two-factor authentication (extension context)
An extra login step some extensions, especially password managers, support to protect your account even if your password is exposed.

Chrome extension glossary: FAQs

What's the difference between a permission and an API?

A permission is what an extension is allowed to do, granted by you at install or first use. An API is the actual programming interface, like chrome.tabs, that the extension calls once it holds that permission to carry out the action.

What does host permission actually let an extension do?

Host permission lets an extension read or change data on the websites it's granted access to, from a single domain up to every site you visit, which is why broad host access gets flagged separately on every listing.

Is Manifest V3 safer than Manifest V2?

Manifest V3 generally limits some of the more powerful, less controllable capabilities Manifest V2 allowed, particularly around network blocking and background scripts, though it isn't a guarantee that every Manifest V3 extension is automatically trustworthy.

What does sideloading an extension mean, and is it risky?

Sideloading means installing an extension from outside the Chrome Web Store, such as loading unpacked developer code. It skips the store's review process, so it carries more risk and is mainly used by developers testing their own work.

Why does an extension need the tabs permission just to work?

Some extensions, like tab managers or session savers, genuinely need to see your open tabs' titles and URLs to function. It's worth checking that a request matches the extension's stated purpose rather than assuming every request is necessary.

What is declarativeNetRequest and why do ad blockers use it?

It's a Manifest V3 API that lets an extension block or modify network requests using rules declared in advance, rather than inspecting every request in real time. Ad and content blockers rely on it to filter traffic under the newer platform.

Does a Featured badge mean an extension is safe?

No. A Featured badge shows an extension meets the Chrome Web Store's technical and policy guidelines, which covers things like quality and user experience, not a full security guarantee or endorsement of the developer's data practices.

What should I check in an extension's data collection disclosure?

Look at which categories of data it claims to collect, such as browsing activity or personal information, and compare that against what the extension actually needs to do its job before deciding whether the request feels proportionate.

What happens to an extension when its ownership changes hands?

A new owner can change permissions, monetization, or how data is handled, sometimes without users noticing right away. We flag ownership changes on Listing Health so you know to recheck a familiar extension after one occurs.

Why do extensions ask for optional permissions instead of everything up front?

Optional permissions let an extension request access only when you use a feature that needs it, rather than demanding everything at install. It's generally a sign of a more considered, minimal-access approach to permissions.

What does it mean if an extension is removed from the Chrome Web Store?

It usually means the extension violated store policy, was abandoned by its developer, or was voluntarily pulled. We flag listings that appear removed rather than leaving the page looking current and installable.

Where can I read more about a specific permission in depth?

Our permissions guide covers individual permissions such as host access, tabs, history, cookies, storage, downloads, clipboard, notifications, declarativeNetRequest, and scripting in plain-English, page-by-page detail, including what each one is used for.