AnyHash
Skip to content

BLAKE2 Hash Generator

Compute BLAKE2b (512-bit) and BLAKE2s (256-bit) digests of any text or file instantly — entirely in your browser. Your input never leaves your device.

Or drop a file to hash its full contents

Drag & drop · up to 64 MB

BLAKE2 hash

 

Type or paste input to see its hash instantly.

Code snippets

Generate BLAKE2 in your language

import { createHash } from "node:crypto";

console.log(createHash("blake2b512").update("hello world").digest("hex"));
console.log(createHash("blake2s256").update("hello world").digest("hex"));

BLAKE2 is built into Node.js, Python (hashlib), Go, Rust, and the b2sum CLI. BLAKE2b-512 emits 128 lowercase hex characters; BLAKE2s-256 emits 64.

What BLAKE2 is

BLAKE2 is a family of fast cryptographic hash functions designed in 2012 by Jean-Philippe Aumasson, Samuel Neves, Zooko Wilcox-O'Hearn, and Christian Winnerlein. It reuses the ChaCha quarter-round at its core — the same primitive powering ChaCha20 — to beat SHA-2's speed while matching its security.

It ships in two main flavors, BLAKE2b (64-bit words, up to 512-bit output) and BLAKE2s (32-bit words, up to 256-bit output), plus tree/parallel modes for multi-core hashing.

What it powers

  • Argon2's internal permutation (this site's password KDF)
  • Zcash — BLAKE2b-512 for hashing
  • Bitcoin Cash and Tor — BLAKE2s
  • libsodium — the default general-purpose hash

Storing passwords? BLAKE2 alone is far too fast — Argon2id / bcrypt add the intentional slowness. See our Argon2id guide.

Algorithm guide

BLAKE2 explained

What is BLAKE2?

BLAKE2 is a cryptographic hash family finalized in 2013, derived from BLAKE — itself a finalist of the NIST SHA-3 competition. Because SHA-3 chose Keccak, BLAKE's follow-up BLAKE2 was engineered for one thing: being the fastest secure hash a software developer can reach for, without the performance drag of its cryptographic ancestors.

Its status as the "fast secure default" is now institutionalized: it is the hash used inside Argon2 (the password-hashing winner), the default hash of libsodium, the hash of the Zcash and Bitcoin Cash ecosystems, and a standard hash in Go, Rust, Python, and OpenSSL.

The ChaCha-based construction

BLAKE2 belongs to the HAIFA-like iterated hash family, but its mixing is built on the ChaCha quarter-round: a 32-bit (BLAKE2s) or 64-bit (BLAKE2b) word function of four additions, three XORs, and two rotations. The same core powers the ChaCha20 stream cipher used in TLS 1.3 and WireGuard, giving BLAKE2 both speed and a security foundation that has withstood scrutiny as a cipher core for years.

BLAKE2b vs BLAKE2s

BLAKE2bBLAKE2s
Word size64-bit32-bit
Max digest512 bits256 bits
This toolBLAKE2b-512 (128 hex)BLAKE2s-256 (64 hex)
Best for64-bit CPUs, servers32-bit / embedded devices

Keyed, truncation & parallel modes

Unlike SHA-2, BLAKE2 supports a native keyed mode — hash input under a secret key directly, no HMAC needed — and variable output length from 1 to 512 bits, so you can truncate without weakening the standard parameterization. BLAKE2bp and BLAKE2sp are the parallel variants that split input across cores; Argon2 uses the BLAKE2b function internally in its compression.

Security level

BLAKE2's designers targeted the same security as SHA-3: 128-bit and 256-bit collision/preimage levels for the b and s variants respectively. More than a decade of analysis has produced no practical attack on the full hash, and its reuse of ChaCha's well-studied round function means the security claim rests on heavily-audited hardware-independent foundations.

Real-world deployments

  • Argon2 — the PHC winner and recommended password KDF uses BLAKE2b internally; this site's Argon2id inherits it.
  • Zcash — BLAKE2b-512; Bitcoin Cash and Tor — BLAKE2s.
  • libsodium / Sodiumcrypto_generichash is BLAKE2b, the default for general hashing.
  • Go's stdlib / OpenSSL — both expose BLAKE2b and BLAKE2s natively.

How this tool works

BLAKE2 is not exposed by the Web Crypto API, so this page uses the hash-wasm WebAssembly build of the reference implementation. The WASM module is fetched once; every subsequent digest reuses it via init(), so hashing is effectively instant. Input is decoded on-device (UTF-8, hex, or Base64), hashed locally, and never transmitted.

Worked examples you can verify right now

InputBLAKE2b-512 digest (128 hex)BLAKE2s-256 digest (64 hex)
(empty string)786a02f742015903c6c6fd852552d272912f4740e15847618a86e217f71f5419d25e1031afee585313896444934eb04b903a685b1448b755d56f701afe9be2ce69217a3079908094e11121d042354a7c1f55b6482ca1a51e1b250dfd1ed0eef9
hello world021ced8799296ceca557832ab941a50b4a11f83478cf141f51f933f653ab9fbcc05a037cddbed06e309bf334942c4e58cdf1a46e237911ccd7fcf9787cbc7fd09aec6806794561107e594b1f6a8a6b0c92a0cba9acf5e5e93cca06f781813b0b

Paste the exact bytes of any row into this tool (matching UTF-8 exactly) and you will get precisely these digests — a quick, deterministic sanity check for your own BLAKE2 wiring. Switch the algorithm selector and the output length follows (128 vs 64 hex characters).

Frequently asked questions

What is the difference between BLAKE2b and BLAKE2s?

BLAKE2b is optimized for 64-bit CPUs and produces up to 512-bit digests (Zcash, Argon2). BLAKE2s is built for 32-bit platforms and small devices, producing up to 256-bit digests (Bitcoin Cash, Tor). This tool computes the 512-bit and 256-bit variants respectively, the two most common configurations.

Is BLAKE2 secure?

Yes. BLAKE2 was designed as a fast replacement for MD5/SHA-1 with security comparable to SHA-3 finalist BLAKE, and it has no known practical attacks. It is widely deployed: it is the internal permutation of Argon2 and the default hash in libsodium.

How does BLAKE2 compare to BLAKE3?

BLAKE3 is the faster, newer sibling built on BLAKE2's core. BLAKE2 is more widely deployed in protocols (Argon2, Zcash, Bitcoin Cash), while BLAKE3 wins on raw throughput and parallel streaming. Both are appropriate modern choices.

Other hash tools