WireGuard · Zcash · Noise protocol · modern
BLAKE2 — fast, modern cryptographic hash. Faster than MD5 and at least as secure as SHA-3. BLAKE2b (optimized for 64-bit) and BLAKE2s (optimized for 32-bit). Used in WireGuard, Zcash, Argon2, and Noise protocol. Client-side only.
Input text box — the BLAKE2 digest appears instantly in the BLAKE2 hash field as you type.BLAKE2b (512-bit) (the default), BLAKE2s (256-bit), or BLAKE2b-256.64 bytes (512 bits)) to confirm which digest you're producing.Copy to copy the hex digest to your clipboard.Clear any time to wipe the input and start over.WireGuard, Zcash, and the Noise protocol framework are all built on BLAKE2. Generate the same digest to cross-check values from those systems.
BLAKE2 is faster than MD5 and at least as secure as SHA-3, with variants tuned for 64-bit (BLAKE2b) and 32-bit (BLAKE2s) platforms.
Switch between a 512-bit BLAKE2b output and the 256-bit BLAKE2s or BLAKE2b-256 outputs to match your protocol or storage needs.
Generate a BLAKE2 digest for any string and use it as a checksum or content fingerprint to detect accidental changes.
Argon2 (password hashing) uses BLAKE2b internally, so hashing here helps you reason about the primitive underneath widely used KDFs.
Everything runs in your browser. Nothing is uploaded, logged, or sent to a server — safe for sensitive inputs and keys.
BLAKE2 is a fast, modern cryptographic hash function based on BLAKE, a SHA-3 finalist. It's faster than MD5 on modern hardware and at least as secure as SHA-3, producing a fixed-size digest from any input.
BLAKE2b is optimized for 64-bit platforms and produces a 512-bit (64-byte) digest, while BLAKE2s is optimized for 32-bit platforms and produces a 256-bit (32-byte) digest. BLAKE2b-256 is BLAKE2b truncated to 256 bits.
No. Hashing is one-way: you cannot recover the original input from a BLAKE2 digest. It's designed to verify integrity and compare values, not to hide or recover data.
This tool computes unkeyed, unsalted BLAKE2 digests. BLAKE2 also supports a keyed mode (a MAC) and a salt parameter, but those require an extra key and are not exposed here.
A hash function maps input of any length to a fixed-size output. BLAKE2b always returns 64 bytes (512 bits) and BLAKE2s returns 32 bytes (256 bits), regardless of how long your input is.
BLAKE2 has the avalanche effect: even a single bit of difference in the input produces a completely different digest. This is what makes hashes useful for detecting tampering.
Never. All hashing happens locally in JavaScript using a pure JS implementation. Your input is not sent to, stored on, or logged by any server.