Password managers1) are one of the most important tools for having good password hygiene2). The problem is that selecting a good one can be challenging.
The aim of this guide is to provide my opinion on the best choice for most people. I use a bespoke setup, but the goal is not to convince anyone that my setup is the best setup for most people. Instead, I exclusively give password manager advice for most people.
Most people who haven't yet adopted password managers worry about security. “If I put all of my passwords in one place, isn't that one place really risky? What if that one place gets hacked?” In an ideal world, you have selected a password manager that is mathematically secure and robust enough that you don't need to think about this. My goal is to present only reasonable default choices.
This is not a set of suggestions for technologists. If you have particular needs, I elaborate more on what you should consider in a password manager elsewhere.
These are the best password managers for most people. Pick one of them, and use it!
Passkeys are the next-generation of passwords. All of the password managers above support passkeys. You should only create passkeys using these systems, which are synchronized, so you don't lose them.
This section is for advanced users. By “advanced users” I mean people who care about things like what Argon2id is, PBKDF2 parameters, and security issues and remediation.
I don't use cloud-based password managers or suggest them to security conscious people. The attack I worry about with these is not realistic, but I consider it unacceptable for security professionals or high risk individuals3) to use these services. There are other documented attacks and faults with these password managers.
For advanced users, consider a custom KeePassXC setup, like the one I use. The basic gist could apply to any offline-only password manager, but basically you need your own solution to access your vault from where you need to access it, a backup solution, and probably a plan for how to recover if you need to do that.
I don't really suggest using gopass/password store, because they inherently assume you are okay with the usernames and sites are not encrypted/plaintext. This can be okay for some people. From a purely cryptographic security perspective, KeePassXC is more secure out-of-the-box and can be tuned to be more secure by adjusting Argon2 parameters.
I don't really find it comfortable to use anything using PBKDF2 with a custom iteration count these days. It gets into really odd territory where you have to judge the iteration count and actually care about it. OWASP's Password Storage Cheat Sheet includes suggestions on what to use. But this is a moving target, and it's kind of annoying to track it.