Hashing

BLAKE2s hash generator

BLAKE2s is the small-platform member of the BLAKE2 family: it works on 32-bit words and produces a 256-bit digest, which makes it the variant you meet in embedded code and in WireGuard's protocol hashing. Like its 64-bit sibling, it targets speed close to MD5 with security closer to SHA-2. Paste any text into the Input box and the tool returns the fixed-length digest as 64 lowercase hex characters, matching every other conforming implementation.

How to use BLAKE2s

  1. Open BLAKE2s in the Toolbox101 app.
  2. Paste the string you want hashed into the Input box; the digest appears and refreshes as you type.
  3. Read the 64-character lowercase-hex digest from the Output box.
  4. Click Copy to put the digest on your clipboard, then compare it against your reference value.

Worked example

BLAKE2s returns the output below for this input.

Input

abc

Output

508c5e8c327c14e2e1a72ba34eeb452f37458b209ed63a294d999b4c86675982

Check it yourself: open BLAKE2s and enter the same input.

Frequently asked questions

What is BLAKE2s commonly used for?

BLAKE2s produces 256-bit digests using 32-bit arithmetic, so it suits embedded controllers, microcontrollers, and low-memory runtimes where BLAKE2b's 64-bit words would cost more cycles. WireGuard uses it for internal hashing. For file checksums on desktop hardware, BLAKE2b or SHA-256 is the more common choice.

Which of BLAKE2b and BLAKE2s is faster?

It depends on the CPU. BLAKE2b compresses 128-byte blocks with 64-bit word operations, so on modern 64-bit processors it usually wins on throughput. BLAKE2s works on 32-bit words and 64-byte blocks, which suits microcontrollers without 64-bit arithmetic. On desktop hardware the gap is small enough that digest size matters more.

Why is a BLAKE2s digest always 64 characters?

The full BLAKE2s output is 256 bits, or 32 bytes, and hex encodes one byte in two characters, so the digest is always 64 characters no matter how long the input. BLAKE2s supports shorter outputs down to 1 byte for protocols that request a truncated tag; the page shows the full-size hash.

Is BLAKE2s as secure as SHA-256?

Against collision and preimage attacks, BLAKE2s-256 and SHA-256 sit in the same class: no practical break is known for either. BLAKE2s is usually faster in software on 32-bit targets. For new systems either is defensible; pick what your ecosystem already uses rather than mixing families.

Use BLAKE2s now

Runs in your browser. Nothing you type is uploaded.