Hashing
BLAKE2b hash generator
BLAKE2b is a cryptographic hash with a 512-bit output, designed as a faster alternative to SHA-2 and SHA-3 on 64-bit hardware. Zcash uses it, Argon2 hashes through it, and libsodium and OpenSSL both ship it. Paste any text into the Input box and the tool returns the digest as 128 lowercase hex characters, always the same for the same input, so values here match b2sum and any other conforming BLAKE2b implementation.
How to use BLAKE2b
- Open BLAKE2b in the Toolbox101 app.
- Paste the string you want hashed into the
Inputbox; the digest appears and refreshes as you type. - Read the 128-character lowercase-hex digest from the
Outputbox. - Click
Copyto put the digest on your clipboard, then compare it against your reference value.
Worked example
BLAKE2b returns the output below for this input.
Input
abcOutput
ba80a53f981c4d0d6a2797b69f12f6e94c212f14685ac4b74b12bb6fdbffa2d17d87c5392aab792dc252d5de4533cc9518d38aa8dbf1925ab92386edd4009923Check it yourself: open BLAKE2b and enter the same input.
Frequently asked questions
What do developers use BLAKE2b for?
BLAKE2b is built to be faster than SHA-2 and SHA-3 on 64-bit CPUs. Zcash uses it, Argon2 hashes through it, and libsodium and OpenSSL expose it. Typical jobs are file integrity, content addressing and keyed MACs, though this tool hashes plain text without a key.
What is the difference between BLAKE2b and BLAKE2s?
BLAKE2b operates on 64-bit words and targets 64-bit processors, with a default 512-bit output. BLAKE2s uses 32-bit words for smaller CPUs and embedded devices, with a default 256-bit output. Same design family and the same security profile relative to digest size. If a library or protocol names one, use that one for compatibility.
Why is a BLAKE2b digest always 128 characters?
The full BLAKE2b digest is 512 bits, or 64 bytes, and each byte becomes two hex characters, so the output runs to 128 characters for any input length. BLAKE2b can also truncate to any size from 1 to 64 bytes when a protocol requests a shorter tag, but the full-size hash is what this page shows.
Is BLAKE2b a good password hash?
No. BLAKE2b is designed to be extremely fast, which is the opposite of what password storage needs: an attacker can test billions of candidates per second. Password hashing requires a slow, memory-hard KDF like Argon2, scrypt, or bcrypt, ideally through a dedicated library rather than a generic hash tool.