Connect requested access to a concrete feature before adding another extension to your browser.
Read the scope, not just the name
Mozilla’s extension-permission guide explains that extensions request access to perform particular functions. Some permissions can involve data on websites you visit. A friendly name or a useful description is not enough to explain why broad access is necessary. Identify the publisher and read the specific request before continuing.
Match access to the feature
Our decision framework is simple: what do you want the extension to do, what information must it read or change to do that, and is the requested scope wider than expected? A page-formatting feature and a download manager have different needs. When you cannot explain a permission in terms of the intended task, pause and read the developer’s documentation.
Consider where you browse
Think about the sites you use in the same browser, including work systems and private accounts. Broader access can matter more in that context than it would in a browser used only for public reading. Do not rely on a generic claim that an extension is completely safe. Publisher reputation, current documentation and the permissions all contribute to the decision.
Review extensions after installation
Keep the collection small enough to understand. If an extension asks for new permissions after an update, read that request as a new decision rather than automatically accepting it. Remove tools you no longer need using the browser’s normal controls. This article explains a review process; it is not an audit of any particular extension or permission prompt.
Go straight to the people who make it.
Mozilla: permission requests for Firefox extensionsSource check: 2026-09-22. General guidance; follow your device’s current instructions.