Import a Local Browser Extension

MaskPilot can import a local Manifest V3 extension from its root folder or a ZIP package. Local import supports private tools and extensions that are not in the store, but you are responsible for confirming the source, permissions, and browser compatibility.

Prepare the package

1. Confirm that the root folder contains a valid manifest.json, or prepare its ZIP package.
2. Use code from a trusted source and remove unrelated files.
3. If the extension declares a minimum browser version, confirm that the target profile meets it.

Local import does not currently handle CRX packages or Manifest V2.

Review before importing

After choosing the folder or ZIP, review the name, version, website access, and browser capabilities. MaskPilot creates a local copy from the content you reviewed; later changes to the source folder do not silently replace that accepted version.

Select it for a specific profile

Importing does not load an extension into every profile. Open the target profile’s extension settings, explicitly select the local extension, then close and relaunch the profile. Test page behavior and permission impact in a disposable profile first.

Understand the device boundary

The local extension and its profile assignments remain on the current device. They are not uploaded or synced with a profile to another device. Import and select the extension again after moving devices. Deleting it also removes its profile assignments on the current device.