Shared extensions

Import once and use in every project profile

Manage commonly used Chromium extensions centrally and eliminate repeated installs and version differences.

Import unpacked extension folders, ZIP archives, and CRX packages.

Control extension status centrally so new profiles load enabled extensions automatically.

Temporarily disable a shared extension in advanced profile settings for a special project.

Search by name, description, version, or source and open the extension folder directly.

Central extension management with automatic loading

Import, enable, and configure profile exceptions in the desktop app.

The app keeps extension names, versions, sources, and enabled states together, while allowing a small number of profile-specific exceptions.

Extension library

Imported extensions enter a local global list that can be searched by name or description and opened directly in the file system.

Import a folder
Choose an unpacked Chromium extension directory and import it directly.
Import ZIP or CRX
Import an archive or CRX package and let the app unpack and register it.
Extension search
Find extensions by name, description, version, or source.
Version and source
Keep the extension ID, version, description, and import source with every record.
Folder management
Open the global extension directory or the folder for an individual extension.

Load control

Enabled extensions load the next time a profile starts. Running windows remain stable, and individual projects can disable an extension when needed.

Global enable and disable
Set the default load behavior for profiles launched later.
Effective on next launch
Apply status changes when the profile starts again without interrupting active work.
Profile-specific disable
Turn off an incompatible or unneeded global extension in advanced profile settings.
Stable running windows
Current browser windows are not forced to reload when the global state changes.
Removal and cleanup
Remove an unused extension so later profile launches no longer load it.

Configure once and every profile launched later can use it.

Choose an extension folder, ZIP file, or CRX package to import.

Enable common team extensions and remove those no longer needed.

The profile loads all currently enabled extensions on its next launch.

Download the desktop app and start with one project profile.