PBKDF2 Key Derivation

PBKDF2 applies an HMAC-based pseudorandom function repeatedly to a password and salt. The password, salt bytes, hash, iteration count, and requested output length all affect the final derived bytes.

1. Copy the exact password text and confirm how that system encodes it.
2. Paste the salt and select whether it is text, hex, Base64, or Base64URL.
3. Match the HMAC hash, iteration count, and output length.
4. Derive the bytes, then compare the output in the encoding used by the other application.

Load the sample to derive 32 bytes from password password, UTF-8 salt salt, one iteration, and HMAC-SHA-256. The expected hex output is:

120fb6cffcf8b32c43e7225256c4f837a86548c92ccc35480805987cb70be17b

This deliberately weak configuration is a deterministic interoperability check, not a configuration for real secrets.

This page allows up to 1,000,000 iterations and 128 output bytes, with a second cap of 2,000,000 iteration-by-output-block work units. The cap is a page performance boundary, not a recommendation for your security policy. Match your system's documented settings.

• Encryption Key Generator - Generate random raw key bytes when a password-based derivation step is not required.
• AES-GCM Encrypt - Use explicit AES key bytes, nonce, ciphertext, and authentication-tag fields.
• Encrypt File - Use a packaged browser workflow that derives a key and stores the required parameters with encrypted file data.
• Argon2id Hash - Create a password-verification string with a memory-hard password-hashing function.
• Encrypt Text with OpenSSL - See how PBKDF2 parameters become part of a repeatable command-line format.

• RFC 8018 defines PBKDF2 and its password, salt, iteration, and derived-key inputs.
• MDN SubtleCrypto deriveBits documents the browser API used by this page.