File to BLAKE2s.

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 file is read on your machine and hashed there, by the browser's Web Crypto API or a WebAssembly build of BLAKE2s loaded on first use; the page makes no request with its bytes. You can load the page, go offline and keep hashing.

Drop the file onto the pane or choose it with the button. It is read into memory and hashed at once, with no size steps and no upload progress because there is no upload. Files up to 1 GB work; a 100 MB file takes well under a second on BLAKE2s.

Paste the digest the publisher gave you into the Verify field, in hex of either case, with or without spaces, colons or a 0x prefix, or in Base64. The tool says whether it matches the file you dropped. A match means the bytes are exactly the ones that were published.

Hex by default, 64 characters; Base64 and Base64url are one click away and re-encode the same 32 bytes. The download button saves a line in the `digest filename` form that sha256sum-style tools read.

Yes: turn on HMAC and enter the secret, and the file is signed with HMAC-BLAKE2s rather than hashed, the same construction a server uses to sign an upload or a webhook payload.

No. The "File to BLAKE2s" tool is free and opens without a sign-in, an account or an install.

Nothing. The "File to BLAKE2s" tool 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 BLAKE2s hash generator page has the same algorithms and options and opens on the text box. This page opens on the file pane.

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

The "File to BLAKE2s" tool 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.