BLAKE3 Hash Generator

BLAKE3: a modern, parallel, extensible hash

BLAKE3 is a cryptographic hash function released in 2020 by Jack O'Connor, Samuel Neves, Jean-Philippe Aumasson and Zooko Wilcox-O'Hearn. It is the direct successor of BLAKE2, which descended from BLAKE, a finalist of the NIST SHA-3 competition (2007–2012). BLAKE3 keeps the same compression core but radically simplifies the design: a single algorithm with three modes, a fixed compression schedule, and an internal Merkle tree structure that makes the function natively parallelizable. The default output is 256 bits (32 bytes, 64 hex chars), but the construction is an XOF (extendable-output function): you can request any length up to 264 bytes from the same internal state.

Performance is BLAKE3's main selling point. On a modern x86-64 CPU with AVX-512 it runs roughly 5x faster than SHA-3, 3x faster than SHA-256 and 6x faster than SHA-512 on a single thread. Because the input is broken into 1 KiB chunks combined as a binary tree, BLAKE3 scales across all CPU cores and SIMD lanes — something SHA-2 and SHA-3 cannot do without a separate construction like Merkle-tree wrappers. ARM NEON is supported the same way.

Three operating modes

BLAKE3 ships a unified API exposing three modes:

• hash — standard cryptographic hash, drop-in replacement for sha256sum.
• keyed_hash — built-in MAC using a 256-bit key, replacing HMAC without the outer/inner construction.
• derive_key — context-string-based KDF, suitable for application-specific key separation.

Security level

BLAKE3 targets 128-bit security (collision resistance) at the default 256-bit output, the same level as BLAKE2b-256 and SHA-256. After several years of public cryptanalysis no practical attack has been published. It is not a NIST standard, but adoption is growing fast: the Rust compiler (rustc) 1.49+ uses BLAKE3 for incremental compilation caches, Tor explored it for circuit IDs, and many content-addressed-storage projects (and IPFS experiments) prefer it for raw throughput.

Reference implementations

The canonical implementation is the Rust crate blake3; the project also publishes an official C reference and Python bindings (pip install blake3). Quick CLI example after installing the standalone b3sum:

$ echo -n "hello" | b3sum
ea8f163db38682925e4491c5e58d4bb3506ef8c14eb78a86e908c5624a67200f -

FAQ

Has BLAKE3 been approved by NIST? No. NIST standardized SHA-2 (FIPS 180-4) and SHA-3 (FIPS 202). BLAKE3 has no official certification, but it is widely deployed in open-source ecosystems, particularly the Rust community.

Can BLAKE3 replace SHA-256 for file checksums? Technically yes — the security level is comparable and it is much faster — but interoperability is the catch. If recipients need to verify the hash, they must have a BLAKE3 tool installed. For internal pipelines or new protocols, BLAKE3 is a great choice; for public artifacts, SHA-256 remains the lingua franca.

BLAKE3 vs BLAKE2: what changed? BLAKE3 has a single fixed configuration (BLAKE2 had many variants), a smaller compression schedule (7 rounds vs 10/12), built-in parallel tree mode, native XOF output and the keyed/derive modes — all of which BLAKE2 lacked or required separate constructions for.

Is BLAKE3 safe for password storage? No hash function alone is. Use Argon2id, scrypt or bcrypt for passwords; BLAKE3's speed actually makes it a worse choice there because it accelerates offline brute-force attacks.

Does this tool send my data to a server? No. The hash is computed entirely in your browser via JavaScript — your input never leaves the page.