You find saved passwords on a computer through the password manager built into your browser or operating system, not through a folder or file you can browse to. On Windows, that means Credential Manager or your browser's password settings; on macOS, Keychain Access or Safari's Passwords panel. Third-party managers like Bitwarden, 1Password, or Dashlane store them behind a master password. Plain-text files, sticky notes, and screenshots are the fallback most people forget to check.

How Password Storage Actually Works

When you save a password in a browser, the browser does not write it into a text file you can open. It encrypts the credential and stores it in a database tied to your user profile. The encryption key is derived from your operating system login credentials, which is why someone with physical access to your unlocked machine can often read saved passwords without knowing them.

The dominant storage mechanisms are:

Browser password databases (Chrome's Login Data SQLite file, Firefox's logins.json plus key4.db, Safari's interaction with the system keychain) Operating-system credential vaults (Windows Credential Manager, macOS Keychain) Dedicated password managers with their own encrypted vaults Application-specific stores (email clients, VPN software, SSH key agents)

Each method encrypts the payload but leaves the database file readable on disk. That distinction matters: encryption protects the contents, not the existence of the file.

Chrome on Windows encrypts saved passwords using a key protected by the Data Protection API (DPAPI), which binds the key to your Windows user account. Firefox uses a primary password you can optionally set; without it, logins.json is encrypted with a key stored locally, meaning anyone with your OS session can decrypt it. Safari delegates to the login keychain, unlocked automatically when you log in.

The plain-language version: your passwords are locked in a box, but on most systems the box opens with the same key that unlocks your computer.

Where the Credentials Live, by Platform

Windows stores web and app credentials in two places most users never open. Credential Manager (search "Credential Manager" in the Start menu) holds Windows credentials, certificates, and generic credentials used by apps and network shares. Browser passwords appear under Control Panel > Credential Manager > Web Credentials, but only for Internet Explorer and legacy Edge. Modern Edge, Chrome, and Firefox keep their own stores.

On macOS, Keychain Access (in Applications > Utilities) is the central vault. Safari passwords appear under the "login" keychain, and the Passwords panel in System Settings (macOS Ventura and later) surfaces them in a friendlier interface.

The comparison below shows what each location actually covers:

Location What it stores Access method Protection
Chrome password manager Websites saved in Chrome chrome://password-manager/passwords OS-bound encryption
Edge password manager Websites saved in Edge edge://settings/passwords OS-bound encryption
Firefox logins Websites saved in Firefox about:logins Optional primary password
Windows Credential Manager Apps, network shares, certificates Start menu search DPAPI, user account
macOS Keychain Access System and app credentials Utilities folder Login keychain unlock
Third-party manager All sites you add Master password + 2FA Zero-knowledge encryption

The counterintuitive detail: browser password managers are not interchangeable. Saving a password in Chrome does not make it visible in Edge or Firefox, even on the same machine, unless you explicitly enable sync or import. People routinely conclude their passwords are "gone" when they are simply in a different browser profile.

Quantified Context: How Common Is Saved-Password Storage?

Password reuse and saved-password habits are widespread. Survey research consistently finds that a large share of adults reuse passwords across multiple accounts, and browser-based password managers are the most-used manager type by raw user count, largely because they ship enabled by default. Chrome, Edge, Safari, and Firefox all offer to save credentials after login, so the population with stored passwords is effectively anyone who has ever clicked "Save."

The practical scale: a typical person has 100 to 200 online accounts, according to password-manager vendor research, but remembers far fewer unique passwords. That gap is exactly what fills browser databases.

Time matters too. A saved password from 2015 may still sit in your Chrome profile if you have not cleared it, even after you changed the password on the website. Old entries are a common source of confusion when you export credentials and find duplicates.

Edge Cases That Break the Simple Answer

Several situations make "just check your browser settings" fail.

Corporate-managed devices often block password export and sometimes disable the browser password manager entirely through policy. If you work on a company laptop, your saved passwords may be managed by IT and unavailable to you directly.

Password managers with zero-knowledge encryption cannot show you your passwords on the vendor's website, only in the app after you unlock the vault. If you lose the master password and recovery key, the data is unrecoverable by design. This is a feature, not a bug, but it surprises people expecting a "forgot password" reset.

Encrypted disk scenarios matter. If your drive uses BitLocker or FileVault, saved passwords are protected at rest, but once you log in, the vault is open. Conversely, a stolen unlocked laptop exposes everything.

Synced versus local-only storage changes the answer. A password saved in a browser profile synced to your Google or Microsoft account exists on the vendor's servers, encrypted, and appears on every signed-in device. A local-only profile keeps it on one machine.

Red flags to watch for:

A password manager that emails you your password in plain text is not using proper encryption. Browser extensions requesting access to all sites can read form data, including passwords, as you type. A "password recovery" service that claims to decrypt a zero-knowledge vault without your master key is almost certainly a scam. Credentials stored in a plain .txt, .docx, or spreadsheet file are readable by anyone with file access and by malware. Screenshots of passwords in your photo library are synced to cloud backups by default.

That last point deserves emphasis. A photograph of a handwritten password list is one of the most common "hidden" storage methods and one of the least secure, because photo libraries sync broadly.

Misconceptions Worth Correcting

The biggest misconception is that saved passwords are hidden somewhere secret. They are in predictable, documented locations, and the operating system protects them with the same authentication that protects your files. Security comes from your login, not from obscurity.

A second misconception: clearing your browser history deletes saved passwords. It does not. History and passwords are separate stores; you must clear passwords explicitly in the password manager settings.

A third: incognito or private mode does not save passwords, so people assume nothing is stored. True for that session, but passwords saved in normal browsing remain.

A fourth: antivirus software protects saved passwords. Most consumer antivirus does not encrypt or isolate browser credential stores; some security suites add vault features, but that is a separate product, not automatic protection.

The professional caveat: exporting your passwords to a CSV file to "back them up" creates a plain-text copy on disk. Chrome and Edge both allow this export, and both warn you. That CSV is unencrypted and is a common breach vector. Prefer an encrypted export format or migrate directly into a password manager with encrypted export.

A Timeline of What Happens to Stored Credentials

Understanding the lifecycle explains why old entries persist and why some disappear.

Stage What happens Typical timing
Save prompt Browser offers to store credential after login At login
Local encryption Credential written to profile database Seconds
Sync (if enabled) Encrypted blob uploaded to account Minutes
Password change on site Old entry remains unless updated Never automatic
Profile reset or reinstall Local store may be deleted On action
Breach exposure Reused passwords appear in dumps Months to years later
Credential rotation You update password in manager Manual

The takeaway from the timeline: nothing expires saved passwords automatically. A 2018 credential can sit in your Chrome profile in 2025 unless you remove it. Audit periodically.

Practical Actions: Finding and Securing Your Passwords

Start with the browser you actually use. In Chrome, go to chrome://password-manager/passwords. In Edge, edge://settings/passwords. In Firefox, about:logins. In Safari, Settings > Passwords. These pages list every saved site, let you reveal individual passwords after OS authentication, and allow deletion.

On Windows, open Credential Manager for app and network credentials. On macOS, open Keychain Access for system-level entries.

Then follow these concrete steps:

Check every browser profile you use, including work and personal profiles, because they are separate stores. Search your filesystem for files named "passwords," "logins," or ".csv" using your OS search, and inspect any you find. Review your photo library for screenshots of password lists. Export credentials only to an encrypted password manager, then delete any CSV immediately and empty the trash. Change any password that appears in a known breach; haveibeenpwned.com is a free check by email address. Enable two-factor authentication on your primary email, since it is the reset path for everything else.

Threshold guidance: rotate any password older than about two years on high-value accounts (email, banking, primary social). For low-value accounts, uniqueness matters more than rotation frequency.

If you cannot find a password anywhere, use the site's own "forgot password" flow rather than hunting further. The credential may never have been saved.

Limitations and What This Guide Cannot Do

This explainer describes where standard systems store credentials. It cannot recover a password from a zero-knowledge vault without the master key, decrypt a disk protected by full-disk encryption without the recovery key, or bypass corporate device management. It also cannot guarantee that a given file you find is a complete record, because malware can exfiltrate credential stores silently.

Password storage mechanisms change across browser versions. Always verify current menu paths in your installed version, since vendors rename and relocate settings between releases. For account-specific recovery, contact the service provider directly.

[HIGH-STAKES DISCLAIMER] This article is general educational information about how operating systems and browsers store credentials. It is not security advice tailored to your device, network, or threat model, and it does not promise that any recovery or protection method will succeed. For device forensics, breach response, or corporate policy questions, consult a qualified IT security professional. If you suspect active compromise, disconnect the device and contact your provider's security team or local law enforcement.