Hash (SHA)
HashingCompute SHA-1, SHA-256, SHA-384, or SHA-512 digests.
What this tool helps with
A cryptographic hash maps any input to a fixed-length digest that is fast to compute and infeasible to reverse or to collide deliberately. SHA-256 and SHA-512 are the workhorses for checksums, content addressing, and signature inputs. This tool computes SHA-1, SHA-256, SHA-384, and SHA-512 with the browser's SubtleCrypto implementation, so the digest matches what your backend produces, and the input never leaves the page.
How to use Hash (SHA)
- Open the Hash (SHA) page and paste, type, or generate the hash input you want to work with.
- Pick the options you need so the tool can compute SHA-1, SHA-256, SHA-384, or SHA-512 digests
- Copy the sha result with one click and use it in your next step — terminal, editor, ticket, or anywhere else you need it.
Common uses
- Reach for Hash (SHA) when you need to compute SHA-1, SHA-256, SHA-384, or SHA-512 digests during debugging, code review, or content preparation.
- Skip installing a desktop hash app — open this hashing utility on a shared machine, an iPad, or a colleague's laptop and it just works.
- Bookmark or share the page when you and your team keep coming back to the same hash, sha, sha1, and sha256 workflow.
FAQ
Which SHA should I use?
SHA-256 for general integrity and signatures. SHA-512 if you specifically want a longer digest. Avoid SHA-1 for anything security-sensitive — it is broken for collision resistance — though it is still fine for non-adversarial checksums.
Can I use a hash to store passwords?
Not a raw SHA. Password storage needs a slow, salted KDF like bcrypt or PBKDF2 to resist brute force. A plain SHA-256 of a password is fast to crack. Use the bcrypt tool for that.
Why does my hash differ from another tool's?
Almost always a difference in input bytes: a trailing newline, CRLF vs LF, or an encoding mismatch. Hash the exact same bytes and the digests match.