Hash Generator
Generate MD5, SHA-1, SHA-256, SHA-384, and SHA-512 hashes from any text instantly.
Hash algorithm guide
MD5 (128-bit)
Fast but cryptographically broken — do not use for security. Still used for checksums, file integrity checks, and non-security deduplication. Produces a 32-character hex string.
SHA-1 (160-bit)
Deprecated for security purposes since 2017. Still used in Git commit hashes and some legacy systems. Not recommended for new systems. 40-character hex output.
SHA-256 (256-bit)
The current standard for secure hashing. Used in TLS certificates, Bitcoin, code signing, and password hashing (via bcrypt/Argon2 wrappers). 64-character hex output.
SHA-512 (512-bit)
Stronger than SHA-256, faster on 64-bit hardware. Used for high-security applications. Produces a 128-character hex string. Part of the SHA-2 family.
Cryptographic Hash Functions — MD5, SHA-256, and When to Use Each
A hash function takes any input — a word, a file, a database record — and produces a fixed-size fingerprint called a hash or digest. The same input always produces the same hash. Change even one character and the entire hash changes completely. This one-way, deterministic property makes hashes fundamental to security, data integrity, and computer science.
The hash algorithms compared
MD5 produces 128-bit hashes (32 hex characters). Fast but cryptographically broken since 2004 — collisions can be found in seconds. Use only for checksums and deduplication, never security. SHA-1 produces 160-bit hashes and was deprecated for security use in 2017. SHA-256 (part of SHA-2) produces 256-bit hashes and is the current security standard — used in TLS, code signing, Bitcoin, and password hashing schemes. SHA-512 provides extra margin with 512-bit output.
Hashing passwords — what not to do
Never use MD5, SHA-1, or even SHA-256 directly to hash passwords. These are fast algorithms — attackers can compute billions per second on GPUs. For passwords, use purpose-built slow functions: bcrypt, Argon2id, or scrypt. These include a cost factor that makes brute force attacks take years instead of seconds. The difference between SHA-256 and bcrypt for password storage is the difference between vulnerable and secure.
Verifying file integrity
Download a file, compute its SHA-256 hash, compare it to the hash published by the author. If they match, the file is unmodified. If they differ, the file was corrupted or tampered with during download. This is how software publishers distribute checksums alongside their downloads, and why package managers like npm and pip verify hashes before installing.