Encryption / Hash

PBKDF2 Key Derivation

Derive a fixed-length key from a passphrase and random salt with Web Crypto.

PBKDF2
Derived locally with Web Crypto; the passphrase is never uploaded.
Derived output
Hex
—
Base64
—

PBKDF2 Key Derivation

Derive fixed-length key material from a passphrase, salt, iteration count, and hash using the browser Web Crypto API. Inputs are not uploaded.

Security Notes

  • The salt and parameters are required to reproduce a key
  • Use a unique random salt; it is not a password
  • For new password-storage systems, evaluate Argon2id; this output is raw derived key material, not a complete password record

Frequently Asked Questions

How many iterations should I use?
Iterations exist to slow brute force. OWASP 2023 recommends at least 600,000 for PBKDF2-HMAC-SHA256; a practical target is ~250–500 ms per verification on your hardware — imperceptible to users, devastating to attackers. Store the iteration count with the salt and raise it over time.
Do the salt and iteration count need to stay secret?
No — both are stored in the clear alongside the hash. The salt defeats rainbow tables and identical-password correlation; it is not a secret. The only secret is the user’s password itself.
PBKDF2, bcrypt, or Argon2?
Argon2id for new systems (memory-hard, resists GPUs and ASICs); bcrypt for compatibility; PBKDF2 where FIPS certification or Web Crypto’s native support matters — this tool uses the latter, well suited for deriving encryption keys or matching existing systems rather than designing new password storage.