SHA Hash Generator

Hashing, Encryption, and Encoding — Starting with the Differences

These three terms are often used interchangeably, but they serve completely different purposes. When you're confused, just ask two questions: "Can it be reversed?" and "Does it require a key?"

Why You Shouldn't Store Passwords with SHA-256

This is where the logic "it can't be reversed, so it must be safe" breaks down. An attacker doesn't need to reverse the hash. They just need to pre-compute hashes for a massive list of common passwords (a "rainbow table") and look up your stolen hash. If you put `password1` or `qwerty123` into this tool, you can search for the resulting SHA-256 hash and find countless sites that will tell you the original password.

Speed makes the problem worse. The SHA family of algorithms was designed to be fast, and a modern GPU can compute billions of them per second. For password storage, you need the exact opposite property: you need it to be deliberately slow.

• Salt — Mix in a different random value for each user. This ensures that two users with the same password will have different hashes, rendering pre-computed tables useless.
• Slow Functions — Algorithms like bcrypt, argon2id, and scrypt are designed with an adjustable computational cost (or "work factor"). A 0.1-second delay for a single login is unnoticeable to a user, but it makes brute-force attacks prohibitively expensive.
• Conclusion — Use bcrypt or argon2id for passwords. Do not store the output of this tool in your database.

Verifying File Integrity — A Practical Walkthrough

When you download open-source software or installer files, the distributor often publishes a SHA-256 checksum alongside the download. This is used to verify that the file wasn't corrupted during transfer or tampered with by a third party.

1. Switch the input method at the top to "📁 File" and drag your downloaded file onto the drop zone. The file is only read within your browser and is never uploaded anywhere.
2. Paste the checksum from the distributor's website into the "Expected hash" field.
3. A badge will immediately show which algorithm matches—for example, "✓ SHA-256 Match".
4. If you see a mismatch, try downloading the file again. If you get the same result, the distributor may have posted an old value, or the file may genuinely be different.

• Why is there a case toggle? — Distributors format hashes differently. The comparison itself ignores case, whitespace, and colons, so you can just paste whatever you're given.
• A message like "✗ No Match (SHA-256 length)" means the hash has the correct format for that algorithm, but its value doesn't match.
• If you see "✗ Not a hexadecimal hash", you likely pasted the filename or other characters along with the hash string.

What Is SHA-1 Still Good For?

There's a reason the SHA-1 field says "Collisions found, not recommended for security." In 2017, researchers demonstrated a practical attack (called SHAttered) that produced two different PDF files with the same SHA-1 hash, and the cost of such attacks has only decreased since. This means an attacker can intentionally create a file that has different content but the same hash.

For this reason, you must not use SHA-1 for any security-sensitive application where an adversary might try to fool you, such as digital signatures, certificates, or integrity verification. However, for non-adversarial use cases—like generating cache keys or identifying duplicate files—it remains practical. This tool includes SHA-1 because you may still need to check a hash generated by an older system.

• For anything new, use SHA-256. If you don't have a specific reason to choose something else, this is the one to pick.
• SHA-384 and SHA-512 are simply longer; in practice, there are few scenarios where they are meaningfully more secure than SHA-256. On 64-bit systems, SHA-512 can sometimes even be faster.
• MD5 is not included in this tool. The standard Web Crypto API, used by browsers, does not support it at all. It's a long-deprecated algorithm, as collisions can be generated in seconds.

What This Tool Can't Do — When You Need HMAC

This tool produces a simple, keyless digest. This means anyone with the same input can calculate the same output, so it cannot be used to prove that "we sent this data." An attacker could simply modify the data, recalculate the hash, and send both along.

For use cases where there's a motive for forgery—like verifying payment callbacks, webhook signatures, or API request signatures—you should use HMAC-SHA256, which incorporates a secret key. When integration docs for a service ask you to "generate a hash," they often mean a keyed hash that includes your secret merchant key. Using a simple SHA hash will fail their verification.