PBKDF2 Generator

Enter a password, a salt, and iterations.

Use this tool

Result

The result appears in this panel after you run the tool.

About this tool

The hex result is the derived bits. It is not stored.

Iterations are limited to 1000 through 500000 on this page.

How to use it

  1. Open this page and provide the input it asks for.
  2. Set the options that are visible, then use Derive key.
  3. Read the result in the panel. Copy it or download it when a file is offered. The input stays in this browser.

Limitations

32 bytes from PBKDF2-SHA-256

The inputs that change the output

The password and the salt are both required and are both taken as UTF-8. Iterations are integers bounded by 1000 and 500000. The control starts at 100000. The derivation is PBKDF2 with SHA-256, and the output is 256 bits, printed as lowercase hex. The same password, salt, and count always produce the same hex. Change any one of them and the hex changes. The salt is not generated for you. If you leave a fixed salt for every password, identical passwords collide, which defeats the point of a salt. Pick a salt per password and store the salt and the count beside the hex if you need to repeat the derivation later. This page does not store them.

The hex is derived key material, not a ciphertext. It does not hide a message. It is not a reversible encoding of the password. It is not a bare SHA-256 of the password either: the salt and the iteration count are part of the calculation, and the iteration count is what makes guessing slower.

How this differs from the AES pages

The encryptor and decryptor also run PBKDF2-SHA-256, but they fix the count at 100000 and they use a random 16-byte salt that is packed inside the base64 message. They derive an AES-GCM key and then encrypt. This page never encrypts. Typing the same password here with a text salt will not reproduce the AES key, because the AES salt is raw bytes you do not choose in this form, and because this output is hex of derived bits rather than a GCM ciphertext. Come here for the hex string itself. Use the encryptor when you want the text protected under a password.

Limits

Counts below 1000 or above 500000 are rejected, as are non-integers. An empty password or an empty salt is rejected. The algorithm is not bcrypt, scrypt, or Argon2. Systems that store those encodings will not accept this hex as a drop-in. SHA-1 is not the hash inside this KDF. Quality tracks the password you chose and whether that salt is unique. A short password remains guessable. The iteration cap keeps the page responsive. It is not a claim that 500000 is the right number for every future threat model.

Privacy

Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.