1Password Not Working | Fix Login And Autofill Fast

When 1Password breaks, it rarely breaks in one clean way. The app might unlock, yet the browser button won’t open. Autofill might work on one site, then vanish on the next. If you run fixes at random, you can waste an hour and end up more confused. You can fix it in minutes today.

This walkthrough gives you a steady order. You’ll start with the fast checks, then move into the browser, the app, and device settings. You’ll also see safe “stop points” so you don’t reinstall when a reboot would’ve done the job.

Fix 1Password Not Working With A Five-Minute Checklist

Start with actions that clear stuck browser processes and stale app helpers. 1Password’s own troubleshooting flow for browser issues starts with restarts and updates, since those steps often clear the underlying glitch.

What You See	Likely Cause	First Move
Extension icon won’t open	Browser process stuck	Quit the browser fully, reopen, unlock
Autofill missing on many sites	Extension disabled or blocked	Enable the extension, then restart app
Can’t sign in anywhere	Address/time issue or outage	Check time, then check status
Changes won’t sync	Stale session or network block	Switch networks, then sign out/in

1. Restart the browser — Quit it from the menu, not just by closing a window, then open it again.
2. Quit and reopen 1Password — Exit the app completely, reopen, unlock, then test the extension.
3. Update app and browser — Install updates for 1Password and your browser so you’re not stuck on a known bug.
4. Restart the device — A full reboot resets background helpers and clears stuck connections.
5. Check the status page — If sign-in or sync fails across devices, look for incidents at status.1password.com.

Quick check: Test in a fresh browser profile with no extra add-ons. If 1Password works there, your main profile has a setting conflict.

Why 1Password Stops Working After An Update

Updates are a common trigger because they change the pieces 1Password relies on. A browser update can change extension permissions. An OS update can switch off background items. A 1Password update can restart helper processes that connect the app and the browser.

Split the problem into two questions. Can you open and unlock the 1Password app? Can you use the browser extension to fill? That split tells you where to spend your time.

• App unlocks, extension fails — Focus on browser steps: restart, re-enable, then reconnect.
• App can’t sign in — Focus on sign-in address, device time, network filtering, or an outage.
• Only one website won’t fill — Confirm you’re on the exact domain you saved with the login.

If you’re seeing a mismatch warning or no fill on a look-alike URL, that can be a safety block. It’s worth checking the address bar for a misspelling before you chase settings.

Browser Extension And Autofill Fixes That Work

Most “1password not working” reports start in the browser because that’s where you notice the failure. The aim is to reset the extension’s session, confirm it’s allowed to run, then reconnect it to the desktop app.

If you use multiple browser profiles, confirm you’re testing the one where 1Password is installed. It’s easy to have the extension in one profile and do daily browsing in another, then it feels like it vanished. Also watch for privacy blockers that strip page scripts. When they block form detection, 1Password can open yet never see fields.

• Switch profiles once — Open your other profile, then check if the 1Password icon appears there.
• Pause blockers for a test — Disable script or privacy blockers on one site and see if field suggestions return.
• Check developer settings — In Chromium dev tools, turn off “Update on Reload” while you test filling.

Reset The Extension Session

Do a clean restart cycle that forces a reconnection.

1. Quit the browser fully — Close windows, then quit so the process stops.
2. Quit 1Password fully — Exit the app, wait a few seconds, then reopen and unlock.
3. Test the extension — Open the browser, click the toolbar icon, and try to fill a known login.

Confirm The Extension Is Enabled

If the icon is missing or nothing happens when you click it, start with the extensions manager in your browser.

• Turn the extension on — Make sure 1Password is enabled for the profile you’re using.
• Pin the icon — Pin it to the toolbar so you can test quickly.
• Allow site access — If the browser asks for permissions, allow access so 1Password can detect fields.

Fix Autofill That Won’t Appear In Fields

If the extension opens yet fields stay blank, fill from the toolbar once. If that works, the field menu is the part that’s stuck.

• Fill from the toolbar — Pick the login in the extension popup, then choose Autofill.
• Reload after unlock — Reload the page after unlocking so the extension can attach again.
• Try private browsing — Private mode often disables other add-ons, which helps you spot conflicts.

If the extension only fails in one browser, install it in a second browser for a quick A/B test. That tells you whether the issue is browser-specific or account-wide.

Sign-In, Unlock, And Sync Problems In The App

App issues tend to fall into three buckets: sign-in, unlock, and sync. Pick the bucket that matches what you see, then follow a short set of steps that keeps your data safe.

When Sign-In Fails

Sign-in failures often come from a wrong sign-in address, device time drift, network filtering, or an outage. Start by ruling out an outage, then verify the basics.

1. Check service status — Look for incidents at status.1password.com.
2. Verify sign-in address — Team accounts use a unique address listed on your Emergency Kit.
3. Set time to automatic — Fix date/time settings, then retry sign-in.
4. Switch networks — Try mobile data or a different Wi-Fi to rule out filtering.

If you can sign in on one device but not another, the account is fine and the local session is the problem. Signing out and signing back in on the failing device often clears it.

When Unlocking Fails

Unlock trouble can come from a stuck biometric prompt, a hung helper, or a corrupted local state. A full quit-and-relaunch is the safest first move.

• Quit and relaunch — Exit fully, reopen, then try unlocking again.
• Try password unlock once — Use your account password to separate biometric issues from app issues.
• Check keyboard layout — If the password is typed wrong due to layout changes, unlock will fail every time.

Be careful with repeated guesses. If you’re unsure about the password, stop and verify from your Emergency Kit rather than trying dozens of attempts.

When Sync Looks Stuck

Sync failures show up as missing items, stale edits, or a device that never updates. The goal is to refresh the session without wiping anything.

• Lock and unlock — Lock 1Password, unlock again, then wait a minute on a stable connection.
• Confirm the same account — If you use multiple accounts or collections, confirm you’re viewing the same one.
• Sign out and sign in — Reset the session so sync can start clean.

Device-Specific Fixes For Windows, Mac, iPhone, And Android

After the general checks, device settings are the next most common blocker. OS updates can switch off background items, change autofill permissions, or tighten battery limits that keep 1Password from staying ready.

Windows

• Quit from the tray — Exit fully from the system tray, reopen, unlock, then test the browser.
• Reboot once — A reboot clears old helper processes that can block the extension connection.
• Check Startup apps — If 1Password never launches, enable it in Startup so it’s ready when the browser opens.

Mac

• Allow background items — In System Settings, allow 1Password to run in the background.
• Review login items — Add 1Password back if it no longer starts at sign-in.
• Restart the Mac — This often restores Touch ID prompts and app-to-browser linking.

iPhone And iPad

• Enable Password AutoFill — In Settings, turn on AutoFill Passwords and select 1Password.
• Unlock the app once — Open 1Password, unlock, then return to the sign-in screen.
• Check Safari extension settings — If you use Safari, confirm 1Password is allowed there.

Android

• Set 1Password as autofill service — In device settings, choose 1Password for autofill.
• Force stop and reopen — Stop it from App Info, reopen, then unlock.
• Ease battery limits — Allow 1Password to run without strict battery restriction.

If you still see “1password not working” on Android after these steps, test autofill in a second app. If it works there, the original app is blocking autofill prompts.

When The Fix Is Not On Your Device

Some problems are not local. A wider incident can block sign-in and slow sync. A work account can enforce policies that change how the app behaves. The trick is to spot those cases fast so you don’t keep reinstalling and hoping.

Check For A Wider Incident

If sign-in fails across multiple devices, go straight to the official status page. It shows active incidents and recent history, which can save you time.

• Read the latest update — Open status.1password.com and check incident notes.
• Pause repeated retries — If an incident is active, wait until it’s marked resolved.
• Use a signed-in device — If one device is already signed in, use it while service recovers.

Reinstall Only After You Verify Access

Reinstalling can help when a local install is damaged. It is still a last move. Before you uninstall anything, confirm you can sign in on at least one device or on the web, and confirm you can reach your Emergency Kit.

1. Confirm Emergency Kit access — You need your sign-in address, email, Secret Key, and account password.
2. Verify one working sign-in — Sign in successfully somewhere before removing another install.
3. Uninstall, reboot, reinstall — Do a clean install cycle, then sign in again.

Get Help Without Sharing Secrets

If none of the steps above work, reach out through 1Password’s official contact options. Keep it safe. No legitimate agent will ask for your account password, Secret Key, or a full copy of your Emergency Kit. Share version numbers, your OS, your browser, and the exact error message.

Once you’re back in, keep two settings steady: system time set to automatic, and background allowances left on after OS updates. Those two items prevent a lot of repeat failures.