BLAKE2s hash generator.

BLAKE2s is the 32-bit flavour of BLAKE2 (2012, RFC 7693): the same design as BLAKE2b on 32-bit words with 10 rounds, giving up to 256 bits (this tool uses all 32 bytes). It was made for 32-bit and embedded CPUs, where it outruns SHA-256 comfortably.

Yes. BLAKE2 was designed in 2012 from BLAKE, a SHA-3 finalist that received years of cryptanalysis without a practical attack. The best published results reach only a fraction of its rounds. BLAKE2 is in RFC 7693, in libsodium as the generic hash, in Argon2 and in WireGuard, and no attack on the full function is known.

WireGuard uses BLAKE2s for its key derivation and MACs; the Linux kernel carries an implementation for it; and it turns up in firmware, IoT devices and anywhere a 64-bit multiplier is absent or memory is tight. On a 64-bit server BLAKE2b or BLAKE3 is the faster choice.

128-bit collision resistance from a 256-bit digest, the same level as SHA-256 and SHA3-256, which is the level the whole internet runs at. The smaller state does not make it weaker at that size; it only caps the output at 32 bytes.

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-BLAKE2s 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 BLAKE2s hash generator is free and opens without a sign-in, an account or an install.

Nothing. The BLAKE2s 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 BLAKE3 without leaving the page. Each one reads the same input, so you can compare digests side by side.

BLAKE2s 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 BLAKE2s 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. BLAKE2s 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 BLAKE2s hash generator: File to BLAKE2s, BLAKE2b hash generator, BLAKE3 hash generator, SHA-256 hash generator. Each opens on its own page, free and in the browser.

The BLAKE2s 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.