Disable Chrome’s Password Save Prompts in Seconds

Chrome’s built-in password manager is convenient by default, but there are several legitimate reasons to fully disable it: using a dedicated password manager (1Password, Bitwarden, etc.) that’s already handling everything, working on a shared computer where saved passwords would be a security risk, or switching to a different browser and not wanting Chrome to keep prompting to save passwords for old sites. For a broader walkthrough, our How to Manage Google Chrome is a good next read.

The 30-second fix: paste chrome://settings/passwords into Chrome’s address bar. Turn off “Offer to save passwords” and “Auto Sign-in”. Chrome stops prompting immediately. To remove already-saved passwords, click the three-dot menu next to each entry → Remove, or scroll down and choose Export passwords first (to backup before deleting if you want to import them somewhere else).

If you also want to stop Chrome from autofilling other data (addresses, payment methods), there are separate settings — covered below. The complete shutdown also requires disabling Chrome Sync if you don’t want passwords syncing across devices via your Google account.

Turning off password saving

chrome://settings/passwords → “Offer to save passwords” toggle → Off. With this disabled: Chrome stops prompting you after each login to save the credentials. Existing saved passwords stay in the list — they’re not deleted when you turn off saving.

To also stop autofill: “Auto Sign-in” toggle → Off. This prevents Chrome from automatically filling in credentials without prompting. With both toggles off: Chrome neither saves new passwords nor fills in saved ones automatically.

Deleting existing saved passwords

Turning off saving doesn’t remove what’s already stored. To clear the saved password list: chrome://settings/passwords → in the “Saved Passwords” section, you can delete individual entries (three dots next to each → Delete) or export then delete all (three dots at the top of the section → Export passwords → then delete all). There’s no built-in “delete all at once” button in some Chrome versions; Ctrl+A doesn’t work here. You need to delete entries individually or use the export-then-wipe approach.

Before deleting: if you’re switching to a dedicated password manager, export the passwords first. Chrome exports to a CSV file that most password managers (1Password, Bitwarden, Dashlane, LastPass) can import directly. chrome://settings/passwords → three dots → Export passwords → save the CSV → import into your new manager → then delete from Chrome.

Stopping Chrome from suggesting passwords

When creating a new account on a site, Chrome suggests a generated password (a complex random string it will save automatically). If you want to generate your own passwords or use a dedicated manager: this suggestion appears above the password field and can be dismissed by clicking elsewhere, but it reappears on every new account creation.

To prevent the suggestion entirely: the same “Offer to save passwords” setting controls this. With it Off, Chrome stops both saving prompts and password generation suggestions. If you use a password manager extension: its own autofill will take precedence, and Chrome’s suggestion is suppressed because the manager’s extension handles the field.

Third-party password managers and Chrome interference

If you’re using Bitwarden, 1Password, Dashlane, or a similar extension-based password manager alongside Chrome: they sometimes conflict. Chrome tries to autofill, the extension also tries, and you end up with duplicate dropdowns or incorrect fills. The fix: disable Chrome’s autofill while keeping the extension active.

chrome://settings/passwords → turn off “Offer to save passwords” and “Auto Sign-in” → Chrome steps back and lets your extension handle everything. The extension has its own login and vault, so you’re not losing password access — you’re just eliminating the conflict between two systems trying to do the same thing simultaneously.

Password manager access via Chrome Sync

Chrome Sync, when enabled, uploads your saved passwords to your Google account at passwords.google.com. If you’re on a work account and concerned about passwords being synced to a Google account you don’t fully control: this is worth considering.

chrome://settings/syncAndGoogleServices → Manage what you sync → Customize sync → “Passwords” toggle → Off. This keeps passwords local to the current device without uploading them to Google’s servers. Passwords stay functional on this device; they just don’t sync to other devices or to the Google account.

Our guide on Chrome privacy settings covers Chrome Sync and Google account data more broadly, and our Chrome settings management covers the settings architecture. For Chrome password security and how encrypted sync works, Google’s Chrome Help documents the sync encryption options including passphrase-based encryption that separates password sync from your Google account’s view of the data.

Shared computer scenarios

On a computer shared between household members who each sign into their own Google account: Chrome profiles are separate (each profile has its own password store, cookies, and settings). If each person uses their own Chrome profile, passwords don’t cross between them. The risk scenario is a shared profile with no distinction between users — in that case, turning off password saving (or using a private browsing session for sensitive logins) is the appropriate approach.

Workplace computers: whether Chrome’s password manager is appropriate depends on whether the computer is shared and whether the work account allows it. Some IT-managed Chrome deployments disable the password manager via policy, particularly in high-security environments. If you see “Passwords are managed by your organization” in the password settings: the configuration is locked at the policy level and can’t be changed locally.

Re-enabling after disabling

Disabling Chrome’s password manager is fully reversible. If you change your mind: chrome://settings/passwords → toggle “Offer to save passwords” back On → Chrome starts prompting again for new logins. Passwords you deleted while the manager was off are gone, but Chrome begins building the saved list again from new logins.

If you export-then-deleted and want to restore from the exported CSV: chrome://settings/passwords → three dots → Import passwords → select the CSV → Chrome reloads all the entries from the file. This works even if months have passed since the export.

Chrome’s password manager is off-by-default in the sense that it doesn’t force anything — you can opt out at any point and your credentials are unaffected. The settings are in one place (chrome://settings/passwords), they work immediately when changed, and they’re reversible. For users who’ve decided a dedicated password manager better fits their workflow: the disable-and-export process transfers the existing credential store cleanly and lets you move on without losing access to anything.

Passkey support and the password manager

Chrome increasingly supports passkeys — a newer authentication standard that replaces passwords with device-based cryptographic keys. If you’ve set up passkeys for sites that support them (Google, Microsoft, GitHub, many banking apps): Chrome manages these separately from the traditional password list. Disabling the traditional password manager doesn’t affect passkey authentication.

Passkeys are stored in Chrome’s credential store and synced through Google Password Manager alongside traditional passwords. If you want to disable passkey management: this is controlled separately. For now, most users encounter passkeys as an addition rather than a replacement, and the intersection with the traditional password manager is manageable — the two coexist without conflict.

Password security on work devices

Saving work-related credentials in Chrome’s password manager has specific considerations. If Chrome Sync is enabled on a work account: saved passwords (including work application credentials) are uploaded to that Google account. If you leave the company and the account is closed: you may lose access to the stored credentials.

Best practice on work devices: use your organisation’s designated password manager (LastPass Enterprise, 1Password Teams, Keeper, CyberArk) for work credentials, and either disable Chrome’s own password manager or limit it to personal sites only. Company-issued password managers give IT visibility into access and make offboarding cleaner — credentials aren’t scattered across personal browser profiles when someone leaves.

Checking if Chrome’s password manager has been breached

Chrome includes a built-in password security check. chrome://settings/passwords → “Check passwords” → Chrome checks your saved credentials against databases of known breached passwords. If any matches are found, they appear in a prioritised list by risk level (Compromised, Weak, Reused).

This check runs locally with a privacy-preserving technique (only a partial hash is sent to Google, not the actual password) — your credentials aren’t exposed in the process. Running this check periodically (quarterly is reasonable) before deciding to disable the password manager can be useful: if many credentials are flagged as compromised, the more urgent task is changing those passwords rather than migrating to a new manager.

The case for keeping Chrome’s password manager

This guide covers disabling it, but the reverse case is worth acknowledging: Chrome’s built-in password manager is genuinely good for many users. It’s free, cross-device through Google account sync, includes breach monitoring, and generates strong passwords. It’s tightly integrated with Android for mobile autofill and works seamlessly with Chrome on desktop.

For users who are comfortable with Google having their credentials (and who trust Google’s security practices, which are substantial): Chrome’s password manager is a low-friction, high-utility option. The decision to disable it makes most sense for users who have specific security requirements, are moving to a more feature-rich dedicated manager, or have shared device concerns. For individual users on personal devices who want the simplest option: keeping it enabled with the built-in breach checking is a perfectly defensible choice.

If you’re on the fence: try running the password security check before changing anything. If the results show well-maintained credentials with no significant breaches, your current setup is probably fine. If they show widespread reuse, weak passwords, or breaches: that’s the signal that a more intentional password management approach — whether Chrome’s manager better-maintained, or a dedicated external tool — is worth the effort.

Mobile Chrome password management

On Android: Chrome’s password manager integrates with Android’s autofill system. With Chrome set as the autofill provider, it fills passwords in other apps as well — not just in Chrome browser. Settings → System → Languages and input → Autofill service → if set to Chrome, change to your preferred provider (or Off) if you don’t want Chrome handling autofill outside the browser.

On iOS: Chrome uses iOS’s native autofill system, so passwords saved in Chrome appear in the iOS AutoFill Passwords list. Settings → Chrome → AutoFill → controls whether Chrome saves and suggests passwords in iOS Safari’s compatibility mode.

If you disable Chrome’s password manager on desktop but keep it on mobile (or vice versa): the Google account sync determines which passwords are available where. Passwords deleted from one device sync the deletion to other devices unless sync is paused. Keep this in mind when doing cleanup — deleting saved passwords is a sync action, not just a local one.

Password manager performance on very large credential stores

For users with hundreds of saved credentials (which happens when Chrome is used for years and saves everything): the autofill dropdown and password check features can be slower than usual. Periodic cleanup — deleting credentials for sites you no longer use, or that have changed their URLs — keeps the list manageable. chrome://settings/passwords → search for old or unused sites → delete those entries. This is more targeted than turning off the manager entirely, and maintains functionality while reducing noise and improving performance of the built-in security check.

Chrome’s password manager, like most aspects of the browser, is configurable to your specific needs. The settings are accessible, the data is exportable, and the decision to use or not use it doesn’t have to be permanent. Start with the settings that match your current situation and adjust as your needs change.

One quick note on Chrome’s “Passwordless sign-in with passkeys” setting: if you’ve disabled the password manager but still want to use passkeys where available, passkeys can be managed through your Google account’s security settings (myaccount.google.com → Security → Passkeys) independently of Chrome’s browser-level password save/autofill settings. The passkey infrastructure and the traditional password manager are separate systems with separate controls, which gives you more granular options than the binary enable/disable of the legacy password manager.

A practical final point for users migrating away: the export CSV Chrome generates is in plain text format. If you save it to a folder that syncs to cloud storage, email it to yourself, or leave it on your desktop: that’s all your passwords in a readable file. Treat the CSV like a sensitive document — import to your new password manager immediately after export, then permanently delete the CSV file (and empty your Recycle Bin). Don’t let it sit around unprotected. The whole point of a password manager is keeping credentials secure; a plaintext export file temporarily reverses that protection.