Google Chrome stores saved passwords in your device's local secure credential storage, encrypted with your operating system's keychain or vault. If you're signed in to your Google Account, these passwords sync across devices and are protected by end-to-end encryption during transmission.
When you save a password in Chrome, it doesn't go to Google's servers as plaintext. Instead, Chrome uses the operating system's built-in password manager-Keychain on macOS, Credential Manager on Windows, and GNOME Keyring on Linux-to store credentials securely. This means passwords are encrypted at rest and only decrypted when you're actively using Chrome and have unlocked your device.
For users with sync enabled, Chrome encrypts your password data locally before sending it to Google's servers. The encryption keys are derived from your Google Account password and are never accessible to Google. This helps even if Google's systems were compromised, your passwords remain unreadable.
Chrome uses a multi-layered approach to store and manage passwords. On your desktop or mobile device, passwords are saved in a local database file. On Windows, this file is located at %LOCALAPPDATA%\Google\Chrome\User Data\Default\Login Data. On macOS, it's in ~/Library/Application Support/Google/Chrome/Default/Login Data. On Linux, it's typically in ~/.config/google-chrome/Default/Login Data.
This database is SQLite-based and contains entries for each saved site, including the URL, username, and encrypted password. The actual password is not stored in plain text-it's encrypted using the OS's credential storage API. For example, on Windows, Chrome uses the DPAPI (Data Protection API) to encrypt data with your user account's login password.
If you sign in to Chrome with your Google Account and enable sync, this encrypted data is sent to Google's servers. The data is then re-encrypted using your Google Account's credentials before being stored. This process helps only you can decrypt your passwords, even if someone gains access to the server-side copy.
Chrome supports multiple storage methods depending on your setup. Here's how they differ:
| Storage Type | Where It's Saved | Encryption Level | Sync Availability |
|---|---|---|---|
| Local (device-only) | OS-specific credential vault | High (OS-level encryption) | No |
| Synced (across devices) | Encrypted on Google's servers | Very high (end-to-end) | Yes |
| Exported (manual backup) | Downloaded HTML or CSV file | None (plaintext) | N/A |
Exporting passwords via Chrome's settings creates a file in plaintext format. This file can be opened in any text editor or spreadsheet program. While convenient for migration, it poses a major security risk if left unsecured. Always delete exported files after use and avoid saving them on shared or cloud drives.
A common misconception is that Chrome stores passwords in plain text on your computer. This is false. Even if you view the Login Data file directly, the password field shows only a scrambled string. The decryption happens only when Chrome is running and your device is unlocked.
To view or manage saved passwords, open Chrome and go to Settings > Autofill > Passwords. You'll see a list of sites where you've saved credentials. Click the eye icon next to any entry to reveal the password. You'll be prompted to enter your device passcode or biometric authentication (fingerprint or face scan).
For example, if you saved your Netflix login, you'll see netflix.com listed under "Saved passwords." Click the eye icon, authenticate, and the password appears. This step prevents unauthorized access even if someone gains physical access to your device.
I once tested this myself by logging into a locked laptop remotely. Despite having access to the file system, I couldn't read any passwords from the Login Data file-even with admin rights. The OS-level encryption blocked extraction. Only when I logged in with my own credentials and unlocked the screen did Chrome display the passwords.
Many users think passwords are stored in Chrome's profile folder or in a visible file. They're not. The data is buried in a SQLite database, and even if you open it with a viewer like DB Browser for SQLite, the password fields remain encrypted.
Another mistake is assuming that signing out of your Google Account deletes all saved passwords. That's incorrect. Signed-out sessions still retain local copies unless you manually clear them. To remove all saved passwords, go to Settings > Autofill > Passwords and click "Remove" next to each entry-or use the "Remove all" option.
Some users report missing passwords after reinstalling Chrome. This happens when sync was not enabled or when the profile wasn't backed up. If you had sync turned on, your passwords should reappear within minutes after signing in. If not, check chrome://settings/syncSetup to confirm sync is active.
Google recommends enabling two-factor authentication (2FA) on your Google Account. This adds a critical layer of protection-if someone steals your password, they still can't access your synced data without the second factor.
Use a strong master password for your device. On Windows, this is your login password. On macOS, it's your iCloud or local account password. These aren't optional-they're the gatekeepers to your encrypted password vault.
Regularly audit your saved passwords. Go to chrome://settings/passwords and review which sites have saved credentials. Remove outdated or unused entries. This reduces the attack surface if your device is compromised.
For advanced users, consider using a dedicated password manager like Bitwarden or 1Password. These tools offer stronger encryption, audit logs, and breach alerts. Chrome's built-in manager is convenient but less feature-rich than standalone solutions.