Password managers: how they work and why use one
Encrypted vault, master password, auto-generation: how password managers actually work.
The problem they solve
Reusing the same password across multiple sites means a single data breach exposes all your accounts. A manager lets you have a unique, complex password per service, without having to remember them.
How it works
- You create a single master password, strong, that you must remember.
- The manager encrypts all your other passwords in a local or synced vault.
- It can generate long, complex random passwords for each new account.
- It auto-fills login forms (browser, apps).
A good manager uses so-called "zero-knowledge" encryption: even the service provider can't read your passwords in plain text.
Common types
| Type | Typical use |
|---|---|
| Built into the browser | Simple, but often limited to a single browser |
| Built into the OS | Convenient within a single ecosystem (one OS) |
| Dedicated, cross-platform app | Works everywhere, usually more features |
Best practices
- Pick a long master password (a memorable phrase that's hard to guess) — it's the only one you'll need to remember.
- Enable 2FA on the manager itself.
- Save the recovery method recommended by the provider: losing access to the vault can mean losing access to every stored password.
Thanks for the feedback!