Bitwarden Argon2 Settings: What the Three Numbers Do, and Which to Change

Bitwarden's security settings show three numbers under Argon2id: iterations, memory, parallelism. Most guides tell you to raise them. Almost none tell you what each one costs the person attacking you, or what it costs you, which is the part that decides whether the change survives the week.

What the three numbers actually do

Iterations is how many passes the algorithm makes over its working memory. Doubling it roughly doubles the time for you and for the attacker. It is the simplest dial and the least interesting.

Memory is how much RAM a single unlock attempt has to allocate. This is the number that makes Argon2id different from PBKDF2. A password-cracking rig gets its speed from running thousands of guesses in parallel on a GPU or an ASIC, and those chips have enormous compute but a modest amount of fast memory per core. Force every guess to hold a large block of memory and you cut how many guesses can run at once. That is the whole idea behind a memory-hard function.

Parallelism is how many threads one attempt may use. It lets you buy more work per unlock without making the user wait longer, on hardware that has cores to spare. It does not add cost the way memory does.

So the ordering is: memory first, iterations second, parallelism only if you understand your hardware.

The constraint every guide forgets

Your vault has to open on your weakest device.

Not your desktop. The phone. The browser extension on a work laptop you do not administer. The tablet in a drawer that you will need on the exact day everything else is unavailable.

If a device cannot allocate the memory you configured, that device cannot unlock your vault. The algorithm is not negotiable at unlock time: it needs what it needs. This turns a security setting into an availability setting, and availability failures in a password manager are the ones that actually hurt people.

Not a photograph of anything this article measures. The point it does illustrate: every one of those boxes opens with a key that has to be carried, and a lock nobody can open is not more secure, it is just closed.

How to change it without losing access

The order matters more than the values.

1. Export a backup you can actually read, and store it somewhere you control. Not inside the vault you are about to re-encrypt.
2. Keep one logged-in session open on a device that already works. Do not log out of everything at once.
3. Change one parameter, then unlock on every device you own before touching anything else. Phone, extension, desktop, the old tablet.
4. Raise gradually. A value that works on your desktop tells you nothing about the phone.

Changing the KDF logs your sessions out and forces every client to re-derive the key. That is expected. What is not expected, and what people discover too late, is a client that silently fails because it cannot get the memory.

What the defaults are, and why I am not going to hand you a number

Bitwarden ships defaults on that screen, and they are chosen to work on ordinary hardware rather than to be maximal. Read the values your own client displays rather than copying any from an article, including this one: defaults change between versions, and a number that was current when a guide was written can be stale by the time you read it.

I am also not going to tell you that a specific configuration makes you safe. Two honest reasons. The first is that the KDF only matters after someone has your encrypted vault, which is a narrow and important scenario but not the common one. The far more likely failure is a weak master password, and no KDF setting compensates for a guessable one. The second is that I have not benchmarked every device you own, and neither has anyone else who wrote a guide with a recommended-settings table in it.

The one thing worth doing tonight

If your vault is still on PBKDF2 with an old iteration count from years ago, that is worth fixing, and it is a smaller change than switching algorithms. If your master password is short, fix that first, before any of this. The KDF multiplies the cost of guessing your master password. It cannot create strength that is not there.

Everything above is configuration you can verify yourself in a few minutes, on the screen in front of you, which is the only kind of security advice worth taking from a stranger.