⚡ BLAKE3 Hash Generator

🔤 Input

⚙️ Mode

Standard unkeyed BLAKE3 hash.

MAC-style hash. Key must be exactly 32 bytes.

Derive subkeys from input material using a context string.

🔑 32-byte Key

Text mode: 32 ASCII characters. Hex mode: 64 hexadecimal characters. Base64 mode: must decode to 32 bytes.

🧬 Context String

Use a stable, application-specific ASCII identifier. Different contexts produce independent key streams.

📏 Output Length (bytes)

Default 32 bytes (256 bits). BLAKE3 is an XOF — longer outputs simply extend the digest deterministically.

⚡ BLAKE3 Hash (hex)

bits ( bytes) — mode: 🔐 Keyed

📊 Algorithm Information

Speed: Faster than MD5, SHA-1, SHA-2, SHA-3, and BLAKE2 on modern CPUs
Security: 128-bit collision resistance at 256-bit output
Designers: O'Connor, Aumasson, Neves, Wilcox-O'Hearn
Published: 2020
Modes: Hash, Keyed (MAC), Derive Key (KDF)
Output: Extendable (XOF) — any length up to 1024 bytes in this tool

💡 Examples

⚠️

ℹ️ About BLAKE3 Hash Generator

BLAKE3 is a modern cryptographic hash function — typically faster than MD5, SHA-1, SHA-2, SHA-3, and BLAKE2, while still meeting the same 128-bit collision security target. Unlike older designs, BLAKE3 is a single algorithm with one fixed structure: it always produces an extendable output, you can ask for any number of bytes (1 byte up to 1 KiB in this tool, and up to 264-1 bytes in the spec), and the first n bytes of a longer digest always equal the n-byte digest.

The algorithm was published in 2020 by Jack O'Connor, Jean-Philippe Aumasson, Samuel Neves, and Zooko Wilcox-O'Hearn. Reference material lives at the BLAKE3 reference repository and the accompanying BLAKE3 specification.

Three modes:

  • Hash — the standard unkeyed BLAKE3 hash. Use for checksums, content addressing, file integrity, signature pre-hashes, and any general-purpose digest need.
  • Keyed hash — built-in message authentication. Takes a 32-byte secret key and produces a MAC-style digest. Faster than HMAC-BLAKE2 / HMAC-SHA, and uses no nested-hash construction.
  • Derive key — a key-derivation function. Combines a free-form context string (treated as the domain separator) with input key material to produce subkeys. The context string should be a unique, hard-coded ASCII identifier such as org.example.tool 2026-05-27 session keys.

Extendable output (XOF): any output length up to 1024 bytes in this tool. Useful when you need more than 32 bytes of pseudorandom material — for example, deriving multiple subkeys, expanding seeds, or fingerprints longer than the standard 256-bit digest.

Examples: BLAKE3 of the empty string is af1349b9f5f9a1a6a0404dea36dcc9499bcb25c9adc112b7cc9a93cae41f3262. BLAKE3 of abc is 6437b3ac38465133ffb63b75273a8db548c558465d79db03fd359c6cd5bd9d85.

Strength guidance: BLAKE3 targets ~128-bit collision resistance at the default 256-bit output length, matching SHA-256 and BLAKE2 in security but with significantly higher throughput on modern hardware. Like other fast hashes, do not use BLAKE3 directly for password storage — use a password-hashing scheme such as Argon2id, scrypt, bcrypt, or PBKDF2 with appropriate parameters. For symmetric authentication of messages, prefer BLAKE3 keyed mode over wrapping an unkeyed hash in HMAC.

Privacy: all hashing runs in your browser through a TypeScript module; the same module is used on the server when the API endpoint is called. Inputs typed into this page never leave the browser unless you call the API explicitly. Even so, avoid pasting production secrets or unreleased file contents into any online tool unless that handling is acceptable for your workflow.

API Usage Example:

POST /api/tools/crypto/blake3
Content-Type: application/json

{
    "text": "Hello World",
    "encoding": "text",
    "mode": "hash",
    "length": 32
}
Ready