🔤 Input Options
⚙️ BLAKE2 Variants
BLAKE2b (64-bit)
BLAKE2s (32-bit)
🔑 Keyed Mode (Optional)
When a key is provided, BLAKE2 operates in keyed mode (MAC)
📁 File Input
⚡ Hash
🎨 Alternative Format
📊 Algorithm Information
💡 Examples
ℹ️ About BLAKE2 Hash Generation
BLAKE2 is a modern cryptographic hash family for turning text, binary data, or files into a fixed-length digest. The core variants are BLAKE2b, tuned for 64-bit systems and digest sizes up to 64 bytes, and BLAKE2s, tuned for 8- to 32-bit systems and digest sizes up to 32 bytes. The algorithm is specified in RFC 7693, with additional background and reference material from the official BLAKE2 project.
Use BLAKE2 when you need fast, collision-resistant digests for file integrity checks, release checksums, content addressing, signed metadata, protocol test vectors, forensic comparisons, or message authentication. It is a good choice when both sides of a system explicitly support BLAKE2; use SHA-256 or SHA-512 when you need the broadest compatibility with older tooling.
BLAKE2 variants in this tool:
- BLAKE2b-512 and BLAKE2b-384: high-strength 64-bit variants for long digests.
- BLAKE2b-256 and BLAKE2s-256: 256-bit outputs with about 128-bit collision security.
- BLAKE2b-160, BLAKE2s-224, BLAKE2s-160, and BLAKE2s-128: shorter outputs for systems that require compact identifiers or legacy-sized digests.
Keyed hashing: RFC 7693 defines BLAKE2 with built-in keyed MAC support, so a secret key can bind a digest to a specific sender without wrapping the algorithm in a separate HMAC construction. This page's current text key field produces HMAC-style keyed digests from the selected BLAKE2 variant, so verifiers must use the same variant, input encoding, and keyed-construction choice. File hashing in this tool is currently unkeyed.
Examples: BLAKE2b-512 of abc begins with
ba80a53f981c4d0d6a2797b69f12f6e9. BLAKE2s-256 of abc is
508c5e8c327c14e2e1a72ba34eeb452f37458b209ed63a294d999b4c86675982.
Strength guidance: prefer 256-bit or larger outputs for new integrity and authentication workflows. The 128-bit and 160-bit outputs are useful for compact identifiers, but they provide less collision resistance than 256-bit and larger variants. BLAKE2 is intentionally fast, so do not use a plain BLAKE2 hash for password storage; use a password-hashing scheme such as Argon2, bcrypt, scrypt, or PBKDF2 with appropriate parameters instead.
Current limits and privacy: text, hex, and Base64 inputs are hashed in the browser. File hashing is sent to the server-side API, is limited to 100 MB, and does not include the optional key field. Avoid pasting production secrets, private keys, or unreleased files into any online hashing tool unless that handling is acceptable for your workflow.
API Usage Example:
POST /api/tools/crypto/blake2
Content-Type: application/json
{
"text": "Hello World",
"encoding": "text",
"variant": "blake2b512",
"key": null
}