Browser Extension Setup and Versions

MaskPilot assigns extensions per browser profile. Each profile loads only the extensions selected for it, allowing different workflows to use different tools while reducing unnecessary changes to other environments.

Use a compatible version

The extension store records which browser-version range each extension version supports. Confirm compatibility before assigning or upgrading. When a combination is not verified, choose a compatible extension or browser version and validate it in a test profile. Download, verification, and extraction errors are installation failures; follow the failed or corrupted extension repair steps to clear old installation files before retrying instead of treating them as version incompatibility.

Control the extension set per profile

Installing an extension does not load it into every profile. Review the selection for the specific profile, then fully close and relaunch it after a change. Even when profiles select the same extension, their runtime data remains independent; see why extension settings differ by profile for that boundary. If an extension is downlisted or has an update notice, first confirm whether the current workflow depends on that version.

Treat local extensions carefully

Local Manifest V3 extensions can be imported from a folder or ZIP package, but they remain on the current device and do not sync with the profile. Confirm the source and contents, then use the local extension permission review to check website access, browser capabilities, and profile scope separately before testing page behavior in a disposable profile. If MaskPilot cannot find or validate the Manifest, use the local extension import error checklist to check the selected root, ZIP layout, required metadata, and compatibility without weakening the package.

Topic

In this topic

Follow the guides for setup, then use the matching answer when a message or problem appears.

Guides

Extensions · Guide Install and manage browser extensions

Select a compatible extension version, attach it to profiles, and handle update or removal notices safely.

Extensions · Guide Import a Local Browser Extension

Import a Manifest V3 extension from a folder or ZIP, review permissions and compatibility, and understand its device-only boundary.

Q&A

Extensions · Q&A Extension Disabled After Browser Update

Separate browser-level disabling, permission changes, and version incompatibility, then restore the extension safely in MaskPilot.

Extensions · Q&A Use an Extension in One Profile Only

Separate installation, default scope, per-profile overrides, and the local device switch so an extension starts only in the browser profiles that need it.

Extensions · Q&A Why Extension Settings Differ by Profile

Separate extension installation, profile selection, and runtime data to understand different settings and sign-in states across browser profiles.

Extensions · Q&A Fix a Failed or Corrupted Extension Install

Separate download, package verification, old installation data, and browser compatibility problems, then safely clear and redownload an extension in MaskPilot.

Extensions · Q&A Fix Local Extension Manifest Import Errors

Diagnose a failed local extension import by checking the folder or ZIP structure, manifest format, required metadata, permissions, and browser compatibility.

Extensions · Q&A How to Review Local Extension Permissions

Learn how MaskPilot separates website access, browser capabilities, minimum browser requirements, and newly added access when you import or replace a local extension.