Password hashing · Client-side

Argon2 Text Hash Generator

Choose between Argon2id, Argon2i, and Argon2d, set memory/CPU costs, and copy the resulting encoded hash in one click—all executed locally. Need to hash files instead? →

Password hashing · Memory hard

Argon2 Text Hash

Hash passwords or secrets with Argon2id, Argon2i, or Argon2d. Configure memory cost, iterations, and salt to match your backend settings—all without sending data to a server.

Password or message

Current length: 0 characters

Salt (base64)

Variant

Iterations

Higher iterations increase CPU cost.

Memory cost (KiB)

≈ 64 MiB used by the algorithm.

Parallelism

Increase this for multi-threaded verification setups.

Hash length (bytes)

Determines digest size (e.g., 64 hex characters).

Secret (optional)

Secrets never leave this tab. Only set this if you know your backend uses Argon2's optional secret.

Encoded Argon2 hash

Encoded hashes include variant, parameters, salt, and digest (e.g., $argon2id$v=19$…).

Raw digest (hex)

Hex digests are convenient for deterministic comparisons or when encoded strings are not supported.

Hash validation (encoded)

Enter a target hash to validate.

Argon2 overview

Argon2 won the Password Hashing Competition and supports three variants. Argon2id blends resistance to GPU cracking and side-channel attacks, making it the recommended modern default.

Argon2i prioritises side-channel protection for environments where attackers can measure memory access patterns, while Argon2d maximises GPU resistance for offline cracking scenarios. Switch between them to match your backend configuration or to compare derived hashes when migrating legacy systems.

Memory cost, iterations, and parallelism work together to raise the bar for attackers—each additional MiB or pass forces adversaries to dedicate the same resources. Use the hash length control to produce shorter digests for storage-limited systems or longer digests when you need larger derived keys.

Encoded outputs follow the PHC string format and include every parameter plus the salt and digest. Copying that string is usually all you need to persist; just store the salt and optional secret securely alongside the hash. All hashing happens locally, and closing or refreshing the page clears inputs, salts, and secrets.