A hash function is a mathematical algorithm that converts input data of any size into a fixed-size string of characters (the hash value or digest). It's a one-way function — you cannot reverse a hash to retrieve the original input. Hash functions are widely used in cryptography, data integrity verification, password storage, and digital signatures.

MD5 produces a 128-bit (32 hex chars) hash and is now considered cryptographically broken — vulnerable to collision attacks. SHA1 produces 160-bit (40 hex chars) hashes and is also deprecated due to collision vulnerabilities. SHA256 produces 256-bit (64 hex chars) hashes and is part of the SHA-2 family, currently considered secure. For security-sensitive applications, use SHA256 or stronger (SHA384, SHA512).

CRC32 (Cyclic Redundancy Check) is a checksum algorithm primarily used to detect accidental data corruption during transmission or storage. It produces a 32-bit (8 hex chars) value. Unlike cryptographic hashes (MD5, SHA), CRC32 is not designed for security — it's fast and effective for error detection in network packets, file integrity checks, and ZIP archives, but should never be used for security purposes.

HMAC (Hash-based Message Authentication Code) combines a cryptographic hash function with a secret key. It provides both data integrity and authentication — verifying that the message came from someone who knows the secret key. Use HMAC when you need to verify both the integrity and authenticity of a message, such as in API authentication, JWT tokens, or secure cookie signing.

No. MD5 is considered cryptographically broken and should not be used for security purposes. Collision attacks allow attackers to create two different inputs with the same MD5 hash. However, MD5 is still commonly used for non-security purposes like checksums, file deduplication, and legacy system compatibility. For any security application, use SHA256 or stronger.

No, cryptographic hash functions are designed to be one-way — you cannot mathematically reverse a hash to get the original input. However, attackers can use brute force or rainbow tables (precomputed hash dictionaries) to guess common inputs. This is why salting is important for password hashing. For short or predictable inputs, hashes can sometimes be "cracked" through lookup tables.

To verify file integrity: (1) Calculate the hash of the downloaded file using this tool's File upload feature. (2) Compare the generated hash with the expected hash provided by the file's source (often published on download pages). (3) If the hashes match exactly (case-insensitive), the file is intact. Any difference means the file may be corrupted or tampered with. Use the Verify button on each hash card to quickly compare.

MD5: 32 hex characters (128 bits). SHA1: 40 hex characters (160 bits). SHA256: 64 hex characters (256 bits). SHA384: 96 hex characters (384 bits). SHA512: 128 hex characters (512 bits). CRC32: 8 hex characters (32 bits). Longer hashes generally provide stronger collision resistance.