You can find saved passwords on a computer in the operating system's credential vault, a browser's password manager, or a password manager app, depending on which tool saved them. On Windows, stored credentials live in Credential Manager and browser profiles. On macOS, they live in Keychain Access and browser profiles. The encryption key on each machine decides who can read them back.

Each storage location works differently, protects differently, and fails differently. This explainer walks through the mechanism behind each vault, the numbers that govern their behavior, the edge cases that surprise people, and the practical steps to take when you need to recover your own credentials. The point is not just where the passwords sit. The point is why they sit there, why they are readable to you at all, and when they are not.

Credential vault architecture: how a saved password becomes readable

A saved password exists in three layers. First, the application encrypts it. Second, the operating system protects the encryption key. Third, a decryption path exists for the legitimate user. Skip any layer and the password is not recoverable at all.

Start with the format. Browsers store logins in an encrypted database. Chrome and Edge use a SQLite file named Login Data. Firefox uses a file named logins.json and a key database named key4.db. The password is encrypted with AES-256-GCM, a symmetric cipher that also detects tampering. Symmetric means the same key encrypts and decrypts. That single key is the crown jewel.

The key itself sits in the OS credential store. In Chromium browsers on Windows, the encryption key is itself encrypted with Data Protection API (DPAPI). DPAPI derives a master key from the user's Windows login and ties it to the user profile. On macOS, the browsers use Keychain Services, which protects the key with a master key inside the login keychain. So the browser never stores the raw key on disk. The OS holds it on behalf of the logged-in user.

Decryption follows the same path in reverse. When you open a saved-login page, the browser asks the OS to unwrap the key. The OS confirms the requesting process runs in your session. The browser then decrypts the database row for the target site. This is why a stolen Login Data file alone is often useless: without the user's OS key, the ciphertext will not open. It is also why an attacker who has your live session can read everything you can.

One plain-language line: the browser holds the locked box, and the operating system holds the key to that box, unlocked only while you are logged in.

Quantified context: where saved credentials actually live

Most saved passwords on a typical computer live in browser stores, not in any single "computer passwords" folder. A Chromium browser keeps its Login Data file inside the user profile directory, and the number of saved entries commonly ranges from a handful to several hundred per profile. A machine with several browsers and multiple browser profiles can hold thousands of encrypted entries. None of these counts are universal. They depend entirely on what you saved and where; treat them as ranges, not benchmarks.

The operating system adds its own stores. Windows Credential Manager holds website credentials and Windows credentials, plus so-called generic credentials that apps create. macOS Keychain Access can hold thousands of items including passwords, certificates, and secure notes. A synced account, such as a Google or Apple account, adds a cloud copy of the same entries, which changes where the recovery happens, not whether it exists.

The practical translation: the answer to where your passwords are depends on which app offered to save them when you last logged in. That offer, whether a browser prompt or a password manager dialog, determines the vault. If you declined every offer, there may be no saved copies to find, and recovery shifts to account-reset flows.

How to locate saved passwords in each vault

Each vault has a defined viewing path, and the path is the same one an attacker with your live session would use. Speed matters here.

Windows Credential Manager opens from Control Panel, or by searching "Credential Manager." The Web Credentials section lists website logins. The Windows Credentials section lists network and system credentials. Reach the vault through a logged-in account; the entries appear decrypted in the interface. The same caveat applies to every vault below: whoever controls your unlocked session controls the plaintext.

macOS Keychain Access opens from Applications, Utilities. Choose the login keychain and the Passwords category. Search for a site by name. Double-click an item and check "Show password." macOS asks for your login password or a Touch ID confirmation. That second factor is the OS protecting the key, not the keychain being empty.

Browser settings pages are the fastest path for browser-saved logins. In Chrome, open Settings, then Autofill and passwords, then Google Password Manager. In Firefox, open Settings, then Privacy & Security, then Saved Logins. In Safari, open Settings, then Passwords. Each page asks you to authenticate before revealing a password, which is the same OS-level unlock described earlier.

Password manager apps have their own localized interface. The typical path is a vault view with search. The difference from a browser is that the vault is portable and often cross-device. The master password, not the OS login, is the key.

Comparison of the main storage options

Storage location Typical access path Encryption key protected by Recovery if locked out
Windows Credential Manager Control Panel or search Windows account, DPAPI Sign in as the same Windows user
macOS Keychain Access Applications, Utilities Login keychain, user password or Touch ID Unlock the keychain with the login password
Browser password manager Browser settings, Autofill section OS credential store on the device Sign in to the browser profile or synced account
Password manager app App vault screen Master password, locally derived key Master password or recovery kit
IT-managed password vault Company app or SSO portal Organization identity system IT help desk identity verification
Plain text file ("passwords.txt") File system search Nothing Anyone with file access

The last row is the one to read twice. A plain text or spreadsheet file has no encryption layer. Its recovery is trivial for you and equally trivial for anyone who gets a copy.

Edge cases: when the vault cannot give the password back

The most common failure is a locked-out account. If you cannot sign in to Windows under the same user profile, DPAPI cannot unwrap the browser key, and the encrypted rows stay sealed. Resetting the Windows password can leave the old profile's key material inaccessible in some configurations. The recovery path is administrative, not a password-viewing trick.

A second failure is keychain lockout. If the macOS login keychain password differs from your current account password, Keychain Access may refuse to unlock. The fix is resetting the login keychain, which destroys its stored items rather than revealing them. That is an important distinction: this is data loss, not recovery.

A third case is browser profile deletion or reinstall. Deleting a browser profile deletes the local Login Data file. If the browser was syncing to an account, the synced copy may still exist in the cloud account, and that is the recovery route. Without sync, the local entries are gone.

Red-flag warnings to treat as bullets:

Emails claiming to contain "your computer password list" are phishing. Legitimate vaults never email plaintext passwords. Any website or app that asks you to paste passwords to "check" them is harvesting, not helping. A stolen Login Data file alone is often not enough to decrypt, but a stolen live session is. Plain text "passwords.txt" files are the single easiest credential theft target on a machine. Remote-access "support" calls asking you to read passwords aloud are a fraud pattern.

Misconceptions: what "where are my passwords" usually gets wrong

The most common misconception is that a computer has one password folder. A Windows or macOS machine has several independent stores, and a browser's database is not the same as the OS vault even though the OS protects the browser's key.

The second misconception is that stored equals readable by anyone with the file. Encryption made that false for the file alone. The realistic threat is the unlocked session, not the file. Anyone physically at your signed-in computer can open the vault by design, because the vault is built for you.

The third misconception is that password managers are all the same kind of store. A browser manager syncs through the browser vendor. A standalone manager syncs through its own service and usually requires its own master password. The two have different recovery paths.

One counterintuitive detail: "show password" in a browser is not a security bug even though the password appears in plaintext. Displaying it requires the same OS-gated key unwrap as the login flow. The display is the design working, not a vulnerability.

A professional caveat: enterprise-managed devices often use an organizational password vault and may disable local browser saving by policy. On those machines, the "where" answer is your company's identity portal, and your local browser will intentionally show nothing. Trying to bypass that policy can violate acceptable-use rules.

Practical actions: finding your own passwords and fixing the weak spots

Work from the most likely vault to the least likely, and authenticate before revealing anything.

Check the browser you use daily. Open the password settings page and authenticate. This is where most saved logins exist for most people. Check the second browser if you have one. Each browser profile has its own Login Data file. On Windows, open Credential Manager and review Web Credentials and Windows Credentials. On macOS, open Keychain Access, select the login keychain, and check the Passwords category. If you use a password manager, open the vault and search. Have the master password and recovery kit ready. If a vault is locked out, use the vendor's recovery flow before resetting anything. Resetting a keychain or profile destroys stored items. Search your disk for files named passwords.txt, pass.txt, or *.csv exports. Exports from browsers and managers are unencrypted plain text by default. Delete them after importing into a manager. Enable a password manager for future saves. One vault beats five.

Thresholds to reconcile explicitly: the number of saved entries in a browser profile is a range, not a fixed count; the availability of entries after a lockout depends on whether the OS can still unwrap the key, not on the entry count; and the threshold for deleting a suspect plain text export is zero copies on disk, not a small number. Treat "a few" and "a lot" as descriptive, not normative.

Limits: what cannot be recovered, and what this article cannot promise

Encrypted vault recovery depends on the OS key being available. If that key is destroyed, the ciphertext stays sealed, and no amount of searching reveals the password. The recovery path in that state is the account owner's password-reset flow, not the vault.

Enterprise policies may hide local vaults entirely, and consumer sync accounts may hold copies you cannot see until you sign in. Neither situation is a failure of the vault; both are the vault working as designed.

Prices and vendor-specific recovery features change, so treat them as things to verify with the vendor rather than facts to assume from any article. This explainer describes stable mechanisms, number ranges, and standard access paths. It does not promise that every saved password is recoverable, and it does not endorse bypassing any organization's security policy.

This article is general educational information about how credential storage works, not legal, security, or IT policy advice. Access only accounts and devices you own or are authorized to manage, and consult your organization's IT or security team for managed systems. If you suspect a compromise, contact a qualified security professional and your bank or identity provider promptly.