LastPass Extension Not Working in Chrome? Here's How to Fix It

LastPass Extension Not Working in Chrome? Try This First

Most LastPass failures in Chrome come from a stuck session, a disabled permission, or a version mismatch, not a broken extension. Work through this list in order, since a full reinstall is rarely the first thing that actually fixes it.

1. Open chrome://extensions, find LastPass, and click the circular Reload icon under its name.
2. Click the LastPass icon in the toolbar, choose Log Out, then sign back in with your master password.
3. Check for a pending Chrome update at chrome://settings/help, since LastPass depends on current extension APIs shipping with recent Chrome versions.
4. On the LastPass card in chrome://extensions, confirm the toggle is switched on (blue), not greyed out by a device policy.
5. Click Details on the LastPass card and set Site access to On all sites so it can read login forms across the web.
6. Restart Chrome completely, not just the tab, so the extension's background service worker restarts cleanly.
7. If none of that works, remove LastPass and reinstall it from the LastPass listing on the Chrome Web Store.

Why Does the LastPass Extension Stop Working in Chrome?

LastPass failures fall into a handful of repeatable categories: session and login problems, a hidden or disabled icon, conflicts with other extensions or site permissions, a version mismatch after a Chrome update, and platform-specific issues on Android. The table below maps each symptom to where to start fixing it.

A Chrome update is a common, easy-to-miss trigger. LastPass ships its own extension updates independently of Chrome, so a short gap between a Chrome release and a matching LastPass patch is normal and usually resolves itself within a day or two, without you doing anything.

It's also worth ruling out a wider account problem before you touch Chrome settings at all, as reported in the Chrome Help forum thread on losing access to the LastPass extension, where several users traced the issue back to account or login state rather than the browser itself.

LastPass Vault Won't Load or You Keep Getting Logged Out

A vault that won't load, or logs you out repeatedly, is almost always a session problem, not lost data. Your saved logins live on LastPass's servers, so a broken local session doesn't put them at risk.

• Click the LastPass icon, choose Log Out, then log back in with your master password rather than waiting for it to reconnect on its own.
• Clear just the LastPass site data from chrome://settings/content/all, searching for lastpass.com, instead of wiping all of Chrome's stored data.
• Check your LastPass account status; a lapsed free trial or an expired subscription can block vault sync on the desktop extension specifically.
• If you use Chrome Sync across devices, sign out of your Google Profile and back in, since LastPass sometimes inherits a stale browser profile session.
• Confirm the system clock on your computer is correct, since a wrong date or time can break the secure connection LastPass makes to its servers.

LastPass Icon or Autofill Missing in Chrome

If the LastPass icon vanished from the toolbar, it's usually an unpinned extension, not an uninstalled one. If autofill stopped suggesting logins, that's almost always a permissions or conflict issue instead.

1. Click the puzzle-piece Extensions icon in Chrome's toolbar, next to the address bar.
2. Find LastPass in the dropdown list and click the pin icon beside it to keep it visible going forward.
3. If LastPass isn't in that list at all, open chrome://extensions and confirm it's still installed and its toggle is on.
4. For missing autofill prompts specifically, click the LastPass icon, open its own Options or vault settings, and check that autofill and form-filling are turned on inside LastPass itself.
5. Open chrome://settings/passwords and check whether Chrome's built-in Offer to save passwords is competing with LastPass for the same autofill prompt on login pages.

It's easy to assume the extension was removed when really it's just hidden. Pinning takes one click, while a genuine uninstall requires confirming a Remove dialog, so a missing icon is worth checking before you touch anything else.

LastPass Conflicts With Another Extension or a Site Permission

Two extensions competing to fill the same login field is the most common conflict, and a restrictive site-access setting is the second most common cause of failed autofill.

On click

LastPass only runs on a page when you click its toolbar icon; login fields won't auto-fill until you do that manually.

On specific sites

LastPass runs only on domains you've explicitly approved; new or unlisted sites won't get autofill or field icons at all.

On all sites

LastPass can read every page automatically, which is the setting most people expect for password autofill to work everywhere by default.

To check yours, open chrome://extensions, click Details under LastPass, and look at Site access near the top of that page. Set it to On all sites if autofill only works on a handful of sites.

Conflicts usually come from other password managers or form-fillers installed at the same time, like Bitwarden or 1Password, fighting LastPass for the same login field. Userscript managers such as Violentmonkey can also interfere with form detection on some pages. Disabling one extension at a time in chrome://extensions is the fastest way to isolate which one is actually causing the clash.

How to Reinstall the LastPass Extension in Chrome

Reinstalling fixes corrupted local extension files without touching your saved vault, which lives on LastPass's servers rather than inside the browser.

1. Go to chrome://extensions and click Remove on the LastPass card, confirming the prompt that appears.
2. Restart Chrome completely, closing every window rather than just the current tab.
3. Visit the LastPass listing on the Chrome Web Store and click Add to Chrome.
4. Click the LastPass icon in the toolbar and log in with your existing master password; do not create a new account during this step.
5. Pin the icon, set Site access to On all sites, and let it run for a minute before testing autofill on a login page you use often.

LastPass Extension Not Working on Chrome for Android or Other Platforms

Chrome for Android doesn't support desktop-style browser extensions at all, so LastPass integrates through Android's system-wide Autofill service instead of a toolbar extension.

• On Android, open Settings, then find Passwords or System > Languages & input > Autofill service, and set LastPass as the Autofill provider.
• If Chrome on Android still won't autofill with LastPass set as the service, confirm you're signed in inside the LastPass app itself, not just inside the Chrome browser.
• On ChromeOS, LastPass behaves like the desktop Chrome extension, so the fixes above apply directly; managed school or work Chromebooks may block it entirely via device policy, which shows up as a greyed-out toggle in chrome://extensions.
• On iPhone or iPad, LastPass uses a Safari extension and its own app rather than a Chrome extension, so troubleshooting steps for Chrome don't carry over there.
• If you split time between Chrome and other Chromium-based browsers like Edge or Brave, each one needs LastPass installed and signed in separately; fixing it in Chrome won't fix it in the other browser.

Still Broken? When to Consider a Different Password Manager

If LastPass keeps breaking after a clean reinstall, or the account itself is the real bottleneck, switching password managers is a legitimate option, not just a reaction to one bad day.

Most competitors let you export your LastPass vault as a CSV file and import it directly, so switching doesn't mean re-entering every saved password by hand. Compare Bitwarden vs LastPass if you only want to weigh two options, or read the full 1Password vs LastPass breakdown for a paid-tier comparison.

Whichever you pick, check how to see saved passwords in Chrome first, so you know what's currently stored locally before you migrate anything, and browse the full password manager picks for a side-by-side comparison beyond these two posts.