BLAKE3 hash generator.

BLAKE3 is the 2020 successor to BLAKE2 by O'Connor, Aumasson, Neves and Wilcox-O'Hearn. It cuts the input into 1 KB chunks, hashes them as a Merkle tree with a 7-round compression function, and gives a 256-bit digest by default that can be extended to any length. One algorithm covers hashing, keyed hashing and key derivation.

The tree. Chunks are independent, so SIMD lanes and CPU cores hash them in parallel, and the result is the same whichever way the work was split. Single-threaded with AVX2 it runs several gigabytes a second, several times SHA-256's software speed; with all cores it is limited by memory bandwidth. Short inputs are fast too, since the tree collapses to one chunk.

Yes. It keeps BLAKE2's compression function with fewer rounds, a margin the designers justified from a decade of cryptanalysis on BLAKE and BLAKE2, and the tree mode is a proven construction. It offers 128-bit security against every attack, immune to length extension, with no published weakness.

b3sum as a drop-in for sha256sum, content-addressed stores and sync tools (Iroh and the Bao verified-streaming format are built on it), deduplication, and anywhere large files are hashed often. It is not in FIPS, so regulated systems still use SHA-2 or SHA-3.

Yes, with a 256-bit key: the key replaces the standard starting values and the result is a MAC as fast as the hash. Generic HMAC over BLAKE3 also works and is what this tool's HMAC toggle computes, so the value matches a standard HMAC library rather than BLAKE3's own keyed mode.

Nothing leaves your browser. The hash is computed on your machine, by the browser's Web Crypto API or a WebAssembly build of the algorithm loaded on first use, and the page makes no request with your input. You can load the page, go offline and keep hashing.

Drop the file onto the input or choose it with the button, and the tool reads it in your browser and hashes the bytes. Files up to 1 GB work; past that the browser would need the whole file in memory, so the tool declines. Paste the published digest into the Verify field to compare.

Hex is the common form: 64 characters from 0 to 9 and a to f, the same value in upper or lower case. Base64 writes the same 32 bytes in fewer characters, and Base64url swaps + and / for - and _ with no padding. Switch the output and the digest is re-encoded, not recomputed.

Text is hashed as UTF-8 bytes, which is what every language and command line does by default. A trailing newline changes the digest, so `echo -n` or this tool's input, with no newline added, matches a command-line tool run on a file without one.

Turn on HMAC and enter the secret: the tool computes HMAC-BLAKE3 over the input with that key, the standard RFC 2104 construction, so the value matches what a server-side HMAC library produces. The key is hashed as UTF-8 text.

No. The BLAKE3 hash generator is free and opens without a sign-in, an account or an install.

Nothing. The BLAKE3 hash generator holds your input in the page's memory, so closing or reloading the tab clears it, and it saves nothing in this browser.

The toolbar switches to BLAKE2b and BLAKE2s without leaving the page. Each one reads the same input, so you can compare digests side by side.

BLAKE3 is computed by a WebAssembly build from the hash-wasm library, which the page loads the first time you hash something and reuses after that.

Yes: the File to BLAKE3 page has the same algorithms and options and opens on the file pane. Files are read in your browser and never uploaded.

Not on its own. BLAKE3 is built to be fast, and fast hashes are cheap for an attacker to guess against. Passwords need a salted, deliberately slow hash: use Argon2id, Argon2d, and bcrypt from the hash generators, which draw a fresh random salt each time.

Closest to the BLAKE3 hash generator: File to BLAKE3, BLAKE2b hash generator, SHA-256 hash generator, xxHash3 hash generator. Each opens on its own page, free and in the browser.

The BLAKE3 hash generator is one of 64 in its group. The group's page, /tools/hash, lists them all.

The tool is free. Its interface is built from shadcn.io's own components (Button, Input, Slider and the rest of the registry under /ui), which come in React, Vue, Svelte and Solid. Pro adds the blocks and templates for the product around it.