Hash Generator
Generate SHA-1, SHA-256, SHA-384, SHA-512 and other hash digests.
Drop file here or click to browse
Maximum 10 MB (*/*)
Enter text or upload a file, then click Generate Hashes
About the Hash Generator
Generate SHA-1, SHA-256, SHA-384, and SHA-512 hash digests from any text or file. Hashing produces a fixed-length fingerprint that changes completely if even one bit of the input changes, which makes it the standard way to verify downloads, detect file corruption, and store password verifiers.
How to use it
- 1 Type or paste the text you want to hash, or drop in a file.
- 2 All supported algorithms compute at once — no need to pick one first.
- 3 Compare the digest against a published checksum to verify integrity.
- 4 Click any result to copy that digest to your clipboard.
What it does
- SHA-1, SHA-256, SHA-384 and SHA-512 computed simultaneously
- Hash entire files without uploading them
- Built on the browser-native Web Crypto API
- Lowercase hexadecimal output ready for checksum comparison
Frequently asked questions
Are my files uploaded to hash them?
No. Every calculation happens locally in your browser using JavaScript. Nothing you paste is uploaded, logged, or stored on a server, which makes the tool safe to use with production data, credentials, and customer records.
Which hash algorithm should I use?
Use SHA-256 unless you have a specific reason not to — it is the current default for file integrity, digital signatures, and blockchain applications. Use SHA-512 when you want a larger digest. Avoid SHA-1 for anything security-related; it is only appropriate for checking against legacy systems that already use it.
Why is MD5 not offered?
MD5 is cryptographically broken — practical collision attacks let an attacker craft two different files with the same digest. The browser Web Crypto API deliberately omits it. For file-integrity checks against non-hostile corruption, SHA-256 is just as fast and actually secure.
Can I reverse a hash back to the original text?
No. Hashing is one-way by design. What attackers do instead is guess: they hash billions of candidate inputs and look for a match. That is why passwords must be hashed with a slow, salted algorithm such as bcrypt, scrypt, or Argon2 rather than a raw SHA digest.
Should I use SHA-256 to store passwords?
No. SHA-256 is designed to be fast, which is exactly wrong for passwords — it lets an attacker test billions of guesses per second on stolen hashes. Use a deliberately slow, salted password hash such as bcrypt, scrypt, or Argon2id.