Input
Preparing your workspace…
How to use
- Enter the password bytes and salt, choosing their encodings.
- Choose the hash, iterations and output length, then select Generate.
- Copy or download the derived bytes as Hex or Base64.
PBKDF2 Generator
Derive keys from password bytes with a selected hash, salt, iteration count and output length.
The result is raw key material, not encrypted text or a self-contained password record. Preserve the parameters you need to reproduce it. Input secrets are not included in the downloaded result.
Choose the bytes and parameters
UTF-8 preserves the exact text, including spaces and line endings. Hex and Base64 represent raw bytes. Encoding changes the interpretation of your input, not just its appearance.
Salt is an explicit byte sequence. Use a fresh random salt for new password-based records; store it alongside the derivation parameters.
Password: password
Salt: salt
Hash: SHA-1
Iterations: 1
Length: 20 bytes0c60c80f961f0e71f3a9b524af6012062fe037a6RFC 6070 test case 1 uses one iteration to verify compatibility; it is not a password-storage recommendation.
Derivation and processing limits
PBKDF2 repeats HMAC to increase the cost of guessing a password. The default is SHA-256, 600,000 iterations and 32 output bytes. Compatibility settings allow 1–2,000,000 iterations.
The tool accepts up to 64 KiB of input and up to 1 KiB for salt. Output is 1–256 bytes. A Worker enforces the processing timeout; no partial key is returned after cancellation.
Compare and reuse the derived key
Match all parameters with the other implementation. Hex and Base64 encode the same derived bytes, and changing output format does not rerun derivation. Treat the derived key as a secret.
Input: 1 MiB; Secret key: 64 KiB; File: 1 GiB; Passwords: 4–128 (Length), 1–100 (Count); bcrypt: 1–72 UTF-8 bytes · cost 4–14 · default 10; AES: Plaintext 1 MiB, Passphrase 1 KiB, GCM / CBC / CTR / CFB / ECB, 128/192/256-bit; PBKDF2 / HKDF: Password / input bytes 64 KiB, Salt / info 1 KiB, Output length (bytes) 1–256; 1–256 output bytes · up to 2,000,000 PBKDF2 iterations · inputs stay on your device; Time: 30 s; File: 120 s.
Frequently asked questions
Is this encryption?
No. A key derivation function produces key bytes. Use an encryption algorithm separately when you need to protect and later recover plaintext.
What must match to reproduce a result?
The password bytes, password encoding, salt bytes, hash, iterations and output length must match.
Why does the sample use SHA-1 and one iteration?
The sample is the published RFC 6070 test vector. The normal defaults are SHA-256 and 600,000 iterations; choose production parameters for your own application.
Does the salt need to be secret?
No. Salt is normally stored with the parameters. It should be unique and random for new password-based records.
Are my input or derived keys uploaded?
No. Derivation runs in a browser Worker. Copy and Download create only the device-side copies you request; inputs are not put in page URLs or stored in tool history.