Argon2 KDF

Derive raw key material with Argon2 KDF

Argon2 is a memory-hard password-based key derivation function and the winner of the Password Hashing Competition. It stretches a password with a salt and work factors for memory (m), time (t), and parallelism (p).

This page outputs only the raw derived bytes as Hex or Base64. For a PHC-encoded password hash string ($argon2id$...) plus verify flow, use the Argon2 Hash Generator instead.

Argon2id is the default and usual recommendation. Prefer Argon2i when you need stronger side-channel resistance, or Argon2d when your protocol requires the data-dependent variant.

How to use this Argon2 calculator

1. Enter the password or input material and select its encoding.
2. Enter a salt of at least 8 bytes and choose the salt encoding.
3. Choose the mode (Argon2id, Argon2i, or Argon2d), memory size (KiB), iterations, and parallelism.
4. Set the output length in bits (must be divisible by 8).
5. Derive and copy the result as Hex or Base64.

Result example

With UTF-8 password password, UTF-8 salt somesalt, Argon2id, memory 16 KiB, iterations 2, parallelism 1, and 256-bit output, the Hex digest is 058202c0723cd88c24408ccac1cbf828dee63bcf3843a150ea364a1e0b4e1ff8.

Parameter guidance

• m is memory in kibibytes. Larger values resist GPU and ASIC guessing more strongly.
• t is iterations (time cost). Each increase costs more CPU time.
• p is parallelism (lanes). Keep it modest in a browser.
• RFC 9106 requires salt length of at least 8 bytes.
• Higher parameters improve resistance to guessing, but they can freeze or exhaust memory in the browser.

Frequently asked questions

Why does my result differ from another tool?

Compare the exact password bytes, salt bytes, mode, m, t, p, and output length. Encoding differences such as UTF-8 versus Hex change the derived result even when the visible text looks the same.

Is this the same as the Argon2 Hash Generator?

No. This page returns raw key material for KDF use. The Argon2 Hash Generator packages a digest into a PHC string for password storage and verification.

Should I use Argon2 or scrypt?

Prefer Argon2id for new designs when you are not required to use another KDF. Use Scrypt KDF when your protocol expects scrypt parameters.