Bitwarden Autofill Not Working: 9 Causes, in Order

The inline prompt missing on one site or everywhere. The nine real causes in order — URI match rules, site access, the Never list, and mobile autofill settings.

The vault opens, the login page is right there, and Bitwarden does nothing. No inline icon, no keyboard shortcut result, no prompt to fill. Or it fills one site perfectly and refuses on another. The gap between those two symptoms is the fastest way to the cause — a global failure and a one-site failure are different problems.

Autofill is a chain: the browser extension must see the page, match a login to it, and be allowed to type into it. Any link breaking produces “Bitwarden autofill not working”. Here are the nine causes, in the order they actually occur.

Triage first: what does the keyboard shortcut do?

Press Ctrl+Shift+L (Windows/Linux) or Cmd+Shift+L (macOS) on the problem site. This one test splits the failure list in half:

ResultMeans the problem is…Go to
Nothing happens at allThe extension is not seeing the page — or is not runningCauses 1–4
“No matching logins” / no resultThe vault has nothing it considers a matchCauses 2–3
The right login is highlighted and fillsMatching works; the inline prompt is the problemCauses 5–6
It fills the wrong loginMultiple matches, or a competing manager is in the wayCauses 6–7

1. The extension is disabled, pinned, or out of the browser

The boring cause is still the most common. After a browser update, a profile reset, or a new device sign-in, the extension can be present but not enabled, or enabled but not pinned and therefore effectively invisible.

  • Open the browser’s extensions page and confirm Bitwarden is enabled and pinned to the toolbar.
  • Confirm you are signed in to the extension — a locked vault behaves differently from a signed-out one, and a signed-out one looks almost identical at a glance.
  • On managed or school machines, group policy can disable extensions outright. chrome://policy shows whether that is happening.

2. The URI does not match the login entry

Bitwarden decides which logins apply by comparing the page’s URL against each entry’s URI. If the entry says accounts.example.com and you are on login.example.com, the default match detection may not connect them — and the result is “no matching logins” on a site where you know a login exists.

Open the login entry and check two things:

  1. The URI itself. It should be the actual login page’s URL. Fix or add the correct one — an entry can hold several URIs.
  2. The match detection rule for that entry (gear icon next to the URI). The useful settings, from loose to strict:
    • Base domain — matches anything under example.com, including subdomains. The right default for most people.
    • Host — exact host only.
    • Starts with / Exact — for setups where several apps share a domain and base-domain matching pulls up the wrong ones.
    • Never — the entry is excluded everywhere. This one causes permanent “not working” on one site, and it is easy to set by accident.

Global default lives in Settings → Options → Default URI match detection. Change the global rule only when every site misbehaves the same way; otherwise fix per entry.

3. The site is on the Never list

Bitwarden keeps a global “Never ask to save or fill” list, and one mis-click on the save prompt can put a domain there. After that, the extension stays silent on that site forever, with no visible indicator.

Check Settings → Options → Notifications (or the equivalent “Excluded domains” list in your version) and remove the domain. On mobile apps the equivalent list lives under the autofill settings. This cause is small but it is the single most common reason for “works everywhere except this one site”.

4. The browser is not letting the extension into the page

Modern Chrome and Edge treat extensions as untrusted by default: since Manifest V3, an extension often has no access to any site until you grant it. If Bitwarden’s site access is set to “On click” or “On specific sites”, it cannot inject into the page and autofill is dead without any error message.

  • Right-click the Bitwarden toolbar icon → Manage extension → Site access.
  • Set it to On all sites, or add the problem domains to the allowed list.
  • Also check the browser’s own password manager: if Chrome or the OS keychain is filling the form first, Bitwarden may be present but beaten to the fields. Turn the competing manager’s autofill off (Cause 7).

5. The form is inside an iframe, shadow DOM, or a multi-step login

Some sites build their login forms in ways that hide them from extensions:

  • Cross-origin iframes — the classic bank / SSO pattern. The form you see lives in a different origin than the page URL, so the URI match fails.
  • Shadow DOM and heavy JavaScript frameworks — the fields exist visually but not in the DOM tree the extension scans.
  • Multi-step logins — email on screen one, password on screen two. The extension matches when the page loads; if the password field appears later, the prompt may never attach.

Workarounds that work: use the keyboard shortcut (it re-evaluates the current DOM), split the login into what the shortcut finds, or use the extension popup’s fill button instead of the inline prompt. For iframe logins, matching the entry URI to the iframe’s origin (visible in dev tools) fixes it permanently.

6. Vault lock or timeout is shorter than you think

A locked vault cannot autofill, and the symptom is identical to a broken extension: the prompt simply does not appear. Two settings cause this:

  • Vault timeout — how long until the vault locks. Default is often 15 minutes. If it is set to “Immediately” or “On browser restart”, the vault is locked almost always.
  • Vault timeout action — Lock vs Log out. If it is set to Log out, you are not just locked — you are signed out, and biometrics and PIN prompts stop appearing.

For most people: timeout 15 minutes, action Lock, and unlock with biometrics where available. Distinguish this from Cause 1 by looking at the extension icon — a locked vault shows its locked state; a signed-out one shows a sign-in screen.

7. Another password manager is winning the race

Chrome’s built-in manager, iCloud Keychain, 1Password, LastPass or the OS-level autofill can grab the fields before Bitwarden does. The symptom is a filled form with the wrong credentials, or a prompt from the wrong product.

Disable autofill in every manager you are not using — in Chrome: Settings → Autofill and passwords; on the OS level: the system autofill service settings. Leave exactly one manager enabled per browser profile.

8. Android: the autofill service or accessibility fallback is off

On Android, Bitwarden does not use a browser extension at all — it plugs into the system autofill framework. Two switches matter:

  • Autofill service — Settings → System → Languages & input → Autofill service. Bitwarden must be the selected service.
  • Accessibility fallback — inside the Bitwarden app settings. Some browsers and apps do not support the autofill framework properly; the accessibility-based fallback fills in those cases. It needs its permission granted in Android’s Accessibility settings.

Also check that battery optimisation is not suspending the Bitwarden service — aggressive OEM skins (Xiaomi, Samsung, Oppo) kill background services, and autofill dies with them.

9. iOS: Password Options are pointing somewhere else

iOS decides which provider fills passwords, and it is not always Bitwarden after an install:

  1. Settings → General → AutoFill & Passwords.
  2. Turn on AutoFill Passwords and Passkeys.
  3. Select Bitwarden and deselect other providers — iOS allows several active at once and Safari will pick one that is not yours.

If Bitwarden does not appear in that list at all, the app’s autofill extension has not finished registering — opening the Bitwarden app once and signing in resolves it.

Still nothing? Refresh the vault itself

A stale local vault is rare but real: the extension autofills from a cached copy, and a login saved on another device never arrived. Pull down to sync in the mobile app, or use Sync vault in the extension menu. If the vault is shared through an organisation, confirm the item is actually shared to you — organisation items do not autofill for members without access.

Checklist

CheckWhere
Extension enabled, pinned, signed inBrowser extensions page
Entry URI + match rule correctThe login item’s gear icon
Domain not on the Never listSettings → Options → Notifications
Site access = On all sitesExtension → Manage → Site access (Chromium)
Only one autofill manager activeBrowser + OS autofill settings
Mobile: service selected, fallback grantedAndroid Settings / iOS AutoFill & Passwords

Frequently asked questions

Why does Bitwarden autofill work on some sites but not others?

Because matching is per site. The entry’s URI and match rule decide whether Bitwarden considers a login relevant to the page you are on, and the site’s form structure decides whether it can type into it. A one-site failure is almost always Cause 2 (URI mismatch), Cause 3 (Never list) or Cause 5 (iframe or multi-step form).

Does Bitwarden autofill automatically, without clicking?

Only if Auto-fill on page load is enabled in Settings → Options, and even then only when exactly one login matches. Most security-minded setups keep it off and use Ctrl+Shift+L, which avoids filling credentials into lookalike domains.

Why did autofill stop after a browser update?

Manifest V3 resets or restricts extension permissions more aggressively than older Chrome versions. Check site access first (Cause 4) — after an update, an extension that previously had “on all sites” can be silently moved to “on click”.

Can two password managers autofill at the same time?

No — one will win the race and the other stays silent, which looks exactly like “Bitwarden not working”. Disable autofill in every manager except the one you intend to use.

Is autofill safe on sites that look like login pages?

Autofill matching is based on the real URL, which gives it an advantage over typing — but a lookalike domain still passes a base-domain match if it owns that domain. Keeping the default “Auto-fill on page load” off, and filling with the keyboard shortcut after checking the address bar, is the safer habit.


Keep reading

Related articles

Browse all articles