Argon2 Hash Generator
Argon2 is a modern password-hashing function that won the Password Hashing Competition in 2015. It provides strong protection against brute-force attacks using memory-hard and time-consuming operations.
Generate Argon2 Hash
Verify Argon2 Hash
Privacy Information
All Argon2 operations are performed entirely in your browser. Your passwords and salts are never sent to our server.
About Argon2 Hash Generator
Argon2 is the winner of the Password Hashing Competition (PHC) held in 2015. It was designed to be resistant to GPU cracking attacks and side-channel attacks. Argon2 comes in three variants: Argon2d (data-dependent), Argon2i (data-independent), and Argon2id (hybrid version).
Argon2id is the recommended variant as it provides protection against both side-channel and time-memory trade-off attacks. It's used by many modern applications and password managers for secure password storage.
All Argon2 operations are performed entirely in your browser. Your passwords and salts are never sent to our server.
Key features
- Password Hashing Competition Winner of Password Hashing Competition 2015
- Multiple Variants Three variants: Argon2d, Argon2i, and Argon2id (recommended)
- Customizable Parameters Configurable memory cost, time cost, and parallelism
- Attack Resistance Resistant to GPU, ASIC attacks and side-channel attacks
How to use Argon2 Hash Generator
- Enter password Enter the password or passphrase you want to hash.
- Provide a salt Enter or generate a unique random salt for each password (minimum 16 bytes).
- Configure parameters Adjust the memory cost, time cost, and parallelism. Argon2id is recommended. For most applications, use: memory=64MB, time=3, parallelism=4 as minimum secure parameters.
- Generate and copy Generate the hash and copy the resulting string or verify it against a password.
Usage tips
- Argon2id is recommended for password hashing as it provides balanced protection.
- For most applications, use: memory=64MB, time=3, parallelism=4 as minimum secure parameters.
- Always use a unique random salt for each password (minimum 16 bytes).
- Higher memory cost = more secure but slower. Minimum recommended: 64MB for secure password storage.
- Time cost is the number of passes over the memory. Minimum recommended: 3 iterations.