Advertisement

Argon2 Password Hasher & Verifier

Compute state-of-the-art Argon2id, Argon2i, and Argon2d password hashes with customizable memory, time cost, and parallelism in WebAssembly.

65,536 KiB = 64 MB
Calculating...
Standard PHC String Format Calculated in 0ms
Ready to store in database (compatible with PHP password_hash, Node.js argon2, Python argon2-cffi).
Raw Hex Digest
Verifying...

What is Argon2 Password Hashing?

Argon2 is an advanced, memory-hard key derivation function specifically created to protect user passwords against modern high-throughput hardware cracking attacks using GPUs, FPGAs, and ASICs. In 2015, Argon2 won the official international Password Hashing Competition (PHC) and was immediately standardized in RFC 9106.

Key Capabilities & Features

  • Argon2id Hybrid Security: Combines data-dependent memory access for GPU resistance with data-independent access to thwart cache timing side channels.
  • OWASP Guidelines Tuned: Instant presets aligned with the latest OWASP Application Security Verification Standard (ASVS).
  • Standard PHC String Output: Generates modular crypt-style string ($argon2id$v=19$m=...) universally compatible with PHP password_hash(), Spring Security, Django, and Node.js.
  • 100% Client-Side WebAssembly: Powered by compiled Wasm running natively in your browser thread for zero latency and guaranteed privacy.

Step-by-Step How It Works

  1. Enter your password and generate or supply a secure random cryptographic salt.
  2. Choose your variant (Argon2id recommended) and select a memory profile (e.g. 64MB for server backends or 16MB for mobile).
  3. Click "Compute Argon2 Hash" to run the memory matrix filling and multi-pass permutations locally.
  4. Copy the standard PHC hash string directly into your configuration or user database.

Frequently Asked Questions

While Bcrypt and PBKDF2 are computationally intensive, their memory footprint is small (only 4 KB for Bcrypt). This makes them vulnerable to massive parallel cracking arrays using modern GPUs. Argon2 enforces memory hardness (filling tens of megabytes of RAM per hash), which starves GPU memory and makes parallel cracking exponentially more expensive.

OWASP recommends Argon2id with m=65536 (64 MiB of memory), t=3 (iterations), and p=4 (parallelism). If your server has constrained RAM, OWASP provides an alternate configuration of m=19456 (19 MiB) with t=2 and p=1.

The PHC hash string encodes the algorithm name, version, memory cost, iterations, parallelism, and the salt in base64. The verifier extracts these exact parameters, recomputes the hash with your candidate password, and performs a constant-time comparison against the stored digest.
AI Images