Micro Tools
Advertisement

BLAKE2b hash generator

Generate BLAKE2b digests of any text in your browser, with selectable 256, 384 or 512-bit output. BLAKE2b is faster than MD5 yet as secure as SHA-3.

Input

Pick an output size, then generate. Hand-written RFC 7693 implementation.

Nothing is uploaded. Everything is computed locally in your browser.
BLAKE2b digest

The digest appears below in hexadecimal.

-
Advertisement

Speed without compromise

BLAKE2b was designed by Jean-Philippe Aumasson and others as a successor to BLAKE, a SHA-3 finalist. On 64-bit platforms it is faster than MD5 and SHA-1 while offering security comparable to SHA-3. It achieves this with a simple ARX (add-rotate-xor) round function over a ChaCha-like core, needing no lookup tables.

Where BLAKE2b is used

BLAKE2b secures the WireGuard VPN protocol, backs the Argon2 password hash internally, and ships in many backup and file-sync tools for fast integrity checks. Choose 512-bit output for maximum margin, 256-bit when you want SHA-256-sized digests.

Related tools

JSON formatterFormat and validate JSON, privately. Regex testerTest regex live with highlighting. Base64 encoderBase64 encode and decode, plus URL encoder and JWT decoder.

Blake2b Hash FAQs

Which output size should I pick?
512-bit is the full native output and the conservative choice. 256-bit matches SHA-256 digest length for drop-in comparisons. Security scales with size; all three are currently unbroken.
BLAKE2b vs SHA-256?
BLAKE2b is faster on 64-bit CPUs, immune to length-extension attacks, and supports keyed hashing natively. SHA-256 has broader hardware and standards support. For pure software speed, BLAKE2b wins.
What is BLAKE2s?
The 32-bit-optimized sibling of BLAKE2b, outputting up to 256 bits. Use BLAKE2s on 32-bit or embedded devices; BLAKE2b on 64-bit platforms. This tool implements BLAKE2b.
Is BLAKE2b quantum resistant?
Like all 256-bit-plus hashes, it degrades gracefully: the 512-bit variant keeps roughly 256-bit quantum collision resistance, considered safe.
How is it computed here?
With a hand-written JavaScript implementation of RFC 7693, including the 12-round compression function, running fully client-side.
Advertisement