SHA-256
256 bitsThe primary cryptographic hash for SSL/TLS certificates, Git commits, and Bitcoin mining. Delivers the ideal trade-off between performance and collision resistance.
Online Hash Generator — SHA-256, MD5, Keccak, BLAKE2 & Fast Checksums
Instant client-side calculation of cryptographic hashes, non-cryptographic hash table keys, and integrity checksums. Supports SHA-2, SHA-3, Keccak-256, BLAKE2b/s, xxHash, MurmurHash2/3, CRC-32/64, Adler-32, Whirlpool, and GOST Streebog. No data leaves your machine.
Hash Functions & Checksums Comparison
Hash functions map arbitrary amounts of data to fixed-size outputs. They are categorized into cryptographic hashes (irreversible, collision-resistant), fast non-cryptographic hashes (optimized for hash table lookups and Bloom filters), and cyclic checksums (designed for error detection in transmission).
SHA-2 Family (Industry Standard)
SHA-512
512 bitsOutputs a 512-bit digest (128 hex chars). Optimized for 64-bit CPU architectures, frequently running faster than SHA-256 while offering maximum post-quantum security margin.
SHA-384
384 bitsTruncated version of SHA-512 with a unique initial vector. Commonly required in high-compliance US Federal/Suite B cipher suites and TLS 1.3.
Legacy Checksums (Non-cryptographic use)
MD5
128 bitsLightweight 128-bit checksum. Cryptographically broken with instant collision vulnerabilities; suitable only for basic non-adversarial file integrity checks.
SHA-1
160 bitsA 160-bit digest formerly standard in Git and older TLS. Broken via collision attacks (SHAttered, 2017). Avoid in new cryptographic protocols.
Keccak & SHA-3 (Sponge Construction)
Keccak-256
256 bitsThe raw Keccak-256 specification with 0x01 padding. The core hashing algorithm of the Ethereum Virtual Machine (EVM), Solidity contracts, and address derivation.
SHA3-256
256 bitsStandardized by NIST with 0x06 domain padding. Built on Keccak sponge construction, making it completely immune to length extension attacks.
SHA3-512
512 bitsThe highest-security SHA-3 variant. Well-suited for cryptographic research and long-term data security against quantum brute-force vectors.
SHA3-384
384 bitsIntermediate 384-bit SHA-3 digest, structurally matched with 192-bit and 256-bit symmetric encryption standards.
SHA3-224
224 bitsCompact SHA-3 digest engineered to replace legacy 224-bit hashes like SHA-224.
BLAKE2 (High-Performance Cryptography)
BLAKE2b-512
512 bits64-bit optimized hash faster than MD5 and SHA-1 while matching SHA-3 security. Extensively utilized in WireGuard VPN, Argon2, and IPFS.
BLAKE2b-256
256 bitsBLAKE2b configured to produce a compact 256-bit digest, providing high throughput on 64-bit systems with minimal digest length.
BLAKE2s-256
256 bits32-bit architecture variant optimized for microcontrollers, embedded IoT hardware, and lightweight cryptographic operations.
Fast Non-Cryptographic Hashes (Hash Tables & Caches)
xxHash32
32 bitsExtremely fast non-cryptographic hash algorithm executing near RAM speed limits. Provides outstanding avalanche effect and collision avoidance for in-memory indexing.
MurmurHash3-128
128 bitsHigh-throughput 128-bit hash developed by Austin Appleby. Universally deployed in databases (Cassandra), Bloom filters, and large-scale data systems.
MurmurHash3-32
32 bitsStandard 32-bit MurmurHash3. Ideal for in-memory hash maps, cache key distribution, and quick data bucketing.
MurmurHash2-64
64 bits64-bit MurmurHash2 variant optimized for 64-bit architectures, frequently leveraged in high-load server key distribution.
MurmurHash2-32
32 bits32-bit MurmurHash2 algorithm widely found in legacy data frameworks, search engines, and real-time metrics pipelines.
Integrity Checksums (Error Detection)
CRC-32
32 bitsCyclic Redundancy Check (32-bit). Specifically designed to detect accidental transmission or storage errors in network packets (Ethernet), ZIP archives, and PNG images.
CRC-64
64 bits64-bit Cyclic Redundancy Check providing a substantially lower accidental collision probability for big file validation and storage blocks.
Adler-32
32 bitsRolling checksum invented by Mark Adler. Computes faster than CRC-32 in pure software and is the core checksum standard in zlib compression.
Specialized & National Standards
Streebog-256 (GOST R 34.11-2012)
256 bitsRussian cryptographic hash standard (GOST R 34.11-2012, 256-bit). Developed by TC 26 using an AES-like substitution-permutation network (SPN).
Streebog-512 (GOST R 34.11-2012)
512 bits512-bit variant of GOST R 34.11-2012 (Streebog). Standardized for national digital signature verification and official cryptographic documents.
Whirlpool
512 bits512-bit hash function designed by Vincent Rijmen and Paulo Barreto. Employs a heavily modified AES cipher square matrix (MDS matrix) for diffusion.
RIPEMD-160
160 bits160-bit European cryptographic standard. Essential to Bitcoin address generation where it is combined with SHA-256 (HASH160).
Frequently Asked Questions
What is the difference between Keccak-256 and SHA3-256?
Although Keccak won the NIST hash competition to become SHA-3, NIST changed the domain separation padding byte from 0x01 to 0x06 in the final standard. Ethereum launched prior to this update and kept the original Keccak-256. Consequently, their hashes for the same text do not match.
What is the difference between cryptographic and non-cryptographic hashes?
Cryptographic hashes (SHA-256, BLAKE2, Streebog) are designed to be mathematically irreversible and collision-resistant against malicious attackers. Non-cryptographic hashes (xxHash, MurmurHash) prioritize raw throughput for hash tables and Bloom filters, making them fast but vulnerable to intentional collision attacks.
Can a cryptographic hash be decrypted or reversed?
No. A hash is a one-way digest, not symmetric or asymmetric encryption. Information is irreversibly reduced. However, predictable or short inputs can be matched using precomputed rainbow tables or dictionary attacks.
Which hash function should I use for user passwords?
Never use raw fast hashes like SHA-256, SHA-512, or MD5 alone for passwords. Modern GPUs calculate billions of hashes per second. Always employ memory-hard key derivation functions such as Argon2id, bcrypt, or scrypt.
When should I choose CRC32 or Adler-32 instead of SHA-256?
CRC-32 and Adler-32 are error-detecting checksums, not secure hashes. Use them when you need to verify network packet integrity, compressed archives (ZIP/zlib), or stream transfer errors with minimal CPU overhead.
Why is xxHash32 so popular?
xxHash is an exceptionally fast non-cryptographic algorithm that operates at the maximum bandwidth limits of system RAM while achieving near-perfect randomness. It is the gold standard for in-memory indexing, game engines, and databases.
What is Streebog (ГОСТ Р 34.11-2012)?
Streebog is the national cryptographic hash function of the Russian Federation. It replaced the outdated GOST R 34.11-94 and uses an internal structure based on the AES/Kuznyechik SPN design.
Why does BLAKE2b have both 256-bit and 512-bit versions?
BLAKE2b is naturally optimized for 64-bit processors using 64-bit words, internally computing a 512-bit state. It can be safely truncated to 256 bits, offering 64-bit speed while producing a smaller digest.
Are my strings or files uploaded to your server?
No. All computations are performed locally in your browser using WebAssembly and Web Crypto API modules. No data is transmitted across the internet.
What is an avalanche effect?
The avalanche effect is a fundamental property where a modification of a single bit in the input causes approximately 50% of the bits in the resulting hash to flip randomly.
Related Developer Tools
All operations run locally in your browser.