Aditya Sharma

Bitwarden Chrome Extension Setup: Install, Autofill, Defaults

On this page, 8 sections

To set up the Bitwarden extension in Chrome: install it from the Chrome Web Store or from Bitwarden’s Downloads page, log in, pin it to the toolbar, then switch Chrome’s own password saving off so the two do not fight over the same login form.

Autofill after that is one click: open the extension on a login page and pick the item listed under Autofill suggestions. The rest of this post is the order I would do it in, and four defaults worth checking afterwards.

I did not install the extension for this write-up. The steps follow Bitwarden’s help pages, which I read on 11 October 2026, and each setting name below is quoted from them.

Install and log in

Bitwarden’s browser extension page says to download the extension from your browser’s marketplace or from the Bitwarden Downloads page. In Chrome that means the Chrome Web Store listing.

Check the publisher name on the listing before you press Add to Chrome. A password manager extension can read every page you visit, so a look-alike listing is the one mistake that matters here.

  1. Open the Bitwarden Downloads page and follow the Chrome link, so you land on the real listing.
  2. Select Add to Chrome, then confirm the permission prompt.
  3. Log in with your email and master password. If you have two-step login on, finish it here.

Pin it right away. Bitwarden’s docs: select the Extensions icon next to the address bar and select the Pin icon next to Bitwarden. An unpinned extension hides in the puzzle-piece menu, and you will stop using it within a week.

Do this on the computer you use most, and expect it to take ten minutes, most of it spent saving that first login. Bitwarden also offers extensions for other browsers, but this post only covers Chrome.

If you use several Chrome profiles, the extension is installed per profile, so repeat the pin and the login in each profile you actually browse in. That per-profile point is my reading of how Chrome profiles work, not a line from Bitwarden’s page.

Make Bitwarden Chrome’s default and switch Chrome’s saver off

This is the step most set-up guides skip, and it is the one that decides whether autofill feels clean. Bitwarden’s autofill page puts it plainly: for best performance, check Make Bitwarden your default password manager and deactivate your browser’s password manager, which stops the browser’s tool interfering with Bitwarden autofill.

On first install the extension prompts you. Bitwarden’s page says that once you select Continue, a dialogue appears and you select Allow, which gives Bitwarden permission to change browser settings. If you skipped the prompt, it is in the extension under Settings, then Autofill, as the toggle Make Bitwarden your default password manager.

If neither works, do it by hand. Bitwarden’s page for this gives the Chrome route:

  1. Type chrome://password-manager/settings in the address bar.
  2. Turn off Offer to save passwords and passkeys.
  3. Turn off Sign in automatically.

Do not delete what Chrome already saved yet. Switching the toggles off stops new saves; the old ones stay until you remove them. Moving them across is its own job, and I will cover the export and import steps in a separate post on moving Chrome passwords to Bitwarden.

Save your first login, then autofill it

Bitwarden’s getting-started page walks you through it, and it is a good order because you practise autofill on a site you already use.

  1. In the extension, open the Vault tab and select the New icon, then choose Login.
  2. Give it an item name, the current password, an optional folder, and in the Website (URI) field the address of the login page.
  3. Select Save.
  4. Go to that site’s login page, open the extension, and click the item under Autofill suggestions.

When at least one saved item matches the site, Bitwarden’s autofill page says the number of matches shows on top of the extension icon. That count is the quickest check that the URI you saved matches the page you are on.

Replace the old password with a generated one

The same getting-started page suggests doing this on the first login: copy the old password from the item, change it on the site’s change-password form, then edit the item, select Generate, tweak the settings and select Use this password. Their example moves a short guessable password to a long random one.

One habit helps here. After you save the first login, use the extension for the next five logins you meet instead of typing them. Bitwarden’s getting-started page describes a banner that appears when you enter a login in a form, with a Save button to add a new or updated login item.

Using it for new logins is one way to build the vault over a week. If you already have a long list in Chrome, move it in one go instead of waiting for the habit to catch up.

Four defaults worth a look

These come from Bitwarden’s autofill page, read on 11 October 2026. I am reporting what the page says the default is, not what your account shows today, because an organisation can change defaults.

SettingDefault per the docsWhy you might change it
Default URI match detectionBase domainControls how a saved item is matched to a site. Tighten it for sites that share a base domain with something else.
Clear clipboardFive minutesControls how long a copied value stays on the clipboard. Shorten it if you copy passwords often.
Inline autofill menuOpt in, in SettingsShows logins, passkeys, SSH public keys and TOTP codes inside the page’s field instead of the toolbar popup.
Quick copy actionsOffAdds copy buttons on the Vault list. Turn on in Settings, then Appearance.

I have not opened the separate Bitwarden page that explains each URI match option, so I am not describing how Base domain behaves beyond the docs’ own label. Read that page before you change it.

Two accounts in one browser

Bitwarden’s getting-started page says the extension can be logged in to five accounts at once, and you add another from the account menu at the top right of the extension. It also says account switching is not available on Safari. This matters if you keep a personal and a work vault apart.

When it does not autofill

  • Two prompts appear. Chrome’s saver is still on. Repeat the toggle step above.
  • No match count on the icon. The saved URI does not match the page. Edit the item and check the Website (URI) field.
  • Nothing happens on a login form. Open the extension manually and pick the item. The popup works on pages where inline suggestions do not appear.

These three are my reading of how the settings interact, not lines from Bitwarden’s docs. Treat them as the first things to check, not as documented failure modes.

How this was checked

I read Bitwarden’s Browser Extensions getting-started page, the Auto-fill page and the page on deactivating a browser’s built-in password manager on 11 October 2026. I did not install the extension, so I cannot tell you how the interface looks in your Chrome version today. I did not verify the Chrome Web Store listing’s publisher, version or user count.

Do this today

Install the extension, pin it, accept the make-default prompt, and save one login you use daily. Do not export or delete anything from Chrome until that login autofills. If you are still deciding between the two, read why I choose Bitwarden over Chrome’s manager and the wider comparison in password manager vs browser password manager.

If you are thinking of running both, should you use multiple password managers covers it.

Resources

Tell me where I am wrong

Your email is not published and I do not add it to any list. Corrections with a source are the ones I act on fastest.

More in Cyber Security

Every piece in Cyber Security

  1. WordPress File Permissions That Actually Matter Core does not read 644 or 755 to decide if it can update itself. It compares file owners. Plus the three permission mistakes that… Cyber Security 8 min
  2. What a WordPress Backup Has to Contain Before a Restore Will Work UpdraftPlus free does not archive wp-config.php. Read from three plugins' source: what is in the archive, what is not, and the restore rehearsal that… Cyber Security 9 min
  3. Hardening wp-admin: What Actually Costs an Attacker Something Six standard hardening measures ranked by whether they change an attacker's work. Two are real, two depend on implementation, two are mostly noise reduction. Cyber Security 11 min
  4. WordPress Capabilities and Roles, Read From the Source Administrator holds 61 capabilities, editor 34, subscriber 2. And edit_post is not stored anywhere, because map_meta_cap computes it per post at check time. Cyber Security 11 min
  5. WordPress Plugin Supply Chain: What Actually Happened in the Documented Incidents Five incidents with primary sources and dates. In four of them the code was fine and the delivery channel was compromised. Cyber Security 11 min
  6. Why WordPress Malware Scanners Miss Cloaked Spam, and How to Actually Check A scanner reads files on disk. Cloaked spam is a decision made at request time. Here is the mechanism, and the check that settles… Cyber Security 11 min