Bitwarden browser extension vault (Chrome, Firefox, Opera, Edge, Safari, & more).
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Daniel James Smith 8192a5e47b
Merge pull request #2135 from bitwarden/update-year-in-copyright
3 days ago
.github Merge pull request #2159 from bitwarden/feature/crowdin-push 3 weeks ago
jslib@b4f475251a Pull in jslib 7 days ago
src Merge pull request #2135 from bitwarden/update-year-in-copyright 3 days ago
store Autosync the updated translations 2 weeks ago
.editorconfig https link to (#1385) 1 year ago
.gitignore ignore dist-safari 1 year ago
.gitmodules convert to jslib submodule 4 years ago expand contributing guide 1 year ago
LICENSE.txt license 5 years ago Update 2 months ago Uppercase Bitwarden 4 years ago
crowdin.yml Updating the Crowdin update process 3 weeks ago
gulpfile.js Use webfonts from jslib instead of downloading them using gulp 2 months ago
karma.conf.js Add jslib as a "real" dependency (#1876) 6 months ago
package-lock.json Merge branch 'master' of into reduce-binking-of-notificationBar 1 month ago
package.json Use webfonts from jslib instead of downloading them using gulp 2 months ago
tsconfig.json Merge remote-tracking branch 'origin' into cdk-virtual-scroll 6 months ago
tslint.json Remove empty catch blocks and remove allow-empty-catch tslint rule (#2136) 1 month ago
webpack.config.js Add new context menu item: Copy Custom Field Name (#2045) 3 months ago

Github Workflow build on master Crowdin Join the chat at

Bitwarden Browser Extension

The Bitwarden browser extension is written using the Web Extension API and Angular.



  • Node.js v14.17 or greater
  • NPM v7
  • Gulp (npm install --global gulp-cli)
  • Chrome (preferred), Opera, or Firefox browser

Run the app

npm install
npm run build:watch

You can now load the extension into your browser through the browser's extension tools page:

  • Chrome/Opera:
    1. Type chrome://extensions in your address bar to bring up the extensions page.
    2. Enable developer mode (toggle switch)
    3. Click the "Load unpacked extension" button, navigate to the build folder of your local extension instance, and click "Ok".
  • Firefox
    1. Type about:debugging in your address bar to bring up the add-ons page.
    2. Click the Load Temporary Add-on button, navigate to the build/manifest.json file, and "Open".

Desktop communication

Native Messaging (communication between the desktop application and browser extension) works by having the browser start a lightweight proxy baked into our desktop application.

Out of the box, the desktop application can only communicate with the production browser extension. When you enable browser integration in the desktop application, the application generates manifests which contain the production IDs of the browser extensions. To enable communication between the desktop application and development versions of browser extensions, add the development IDs to the allowed_extensions section of the corresponding manifests.

Manifests are located in the browser subdirectory of the Bitwarden configuration directory. For instance, on Windows the manifests are located at C:\Users\<user>\AppData\Roaming\Bitwarden\browsers and on macOS these are in Application Support for various browsers (for example). Note that disabling the desktop integration will delete the manifests, and the files will need to be updated again.


Code contributions are welcome! Please commit any pull requests against the master branch. Learn more about how to contribute by reading the file.

Security audits and feedback are welcome. Please open an issue or email us privately if the report is sensitive in nature. You can read our security policy in the file.