A hash turns any text into a fixed-length fingerprint: change one character and the fingerprint changes completely, while the same text always produces the same fingerprint. SHA-1 was for years the standard fingerprint for files, version control, and certificates, and it is still the right tool for checksums and identification in legacy systems, even though it is no longer trusted for security-critical signatures. This generator computes the SHA-1 digest of your text using your browser built-in cryptography, so the text never leaves your device, and the result matches any standard SHA-1 implementation.
Quick Answer: Type or paste text and click Generate SHA-1 to see its 40-character hexadecimal digest.
Free Online Tool
SHA-1 Hash Generator
Compute the SHA-1 hash of input text, a distinct algorithm from SHA-256.
How to Use the SHA-1 Hash Generator
- Type or paste the text you want to fingerprint.
- Click Generate SHA-1.
- Copy the 40-character hex digest shown.
- Compare it against a published digest to verify a file or message.
- Re-run with any change to see how completely the digest changes.
- Use the Clear button before hashing a new value.
Key Features
- Standard SHA-1 digest, 160 bits, shown as 40 hex characters.
- Computed with WebCrypto in your browser, not on a server.
- Matches command-line and library SHA-1 implementations exactly.
- Handles empty input, long text, and Unicode correctly.
- Instant for typical inputs, with no upload or wait.
- No data leaves your device at any point.
What the Result Means
The digest is a fingerprint, not an encryption: it cannot be reversed to recover the text, and two different texts should never share a digest in practice. A matching digest means the text you have is almost certainly identical to the text that produced the published digest, which is how downloads and messages get verified. A different digest means something changed, even if the difference is invisible, such as a trailing space or a line-ending change. SHA-1 collisions have been demonstrated by researchers, so for security signatures prefer SHA-256 or SHA-512, but for identification and checksums SHA-1 remains useful.
Worked Example
A software archive publishes the SHA-1 digest a9993e364706816aba3e25717850c26c9cd0d89d for a small test file whose contents are the three letters abc. Pasting abc here produces exactly that digest, confirming both the tool and the file. If the downloaded file instead produced a different digest, you would know the download was corrupted or tampered with before running it, which is the entire point of publishing digests alongside files. The same check works for any text snippet: hash the snippet you received, hash the snippet that was sent, and compare the two digests character by character rather than by eye, since a single differing character anywhere invalidates the match.
Best Practices and Tips
- Verify a download by comparing its published SHA-1 digest with the one computed here from the file contents as text, where applicable.
- Hash the exact bytes: an extra newline changes the digest completely.
- For passwords, never use plain SHA-1; use a slow password hash such as Argon2 or bcrypt.
- Keep a digest alongside backups so silent corruption is detectable later.
- When a digest mismatches, check encoding first: UTF-8 versus another encoding changes the result.
Common Mistakes to Avoid
- Using SHA-1 to protect passwords or sign security-critical data.
- Comparing digests by eye instead of copying and comparing exactly.
- Hashing a file name instead of the file contents.
- Assuming a matching digest proves who created the text; it only proves what the text is.
Frequently Asked Questions
What is the SHA-1 of abc?
a9993e364706816aba3e25717850c26c9cd0d89d. Every correct implementation produces this value.
Is SHA-1 secure?
Not for collision resistance against a determined attacker. Use SHA-256 or SHA-512 for security; SHA-1 remains fine for checksums and identification.
Can I reverse a SHA-1 hash?
No, not in general. A hash is one-way; recovering the input requires guessing it and re-hashing.
Why does a tiny change alter the whole digest?
That is the avalanche effect, a design property of hash functions: similar inputs must produce unrelated outputs.