Skip to main content
Hashing, signatures and passwords
A digest answers a different question from encryption: it proves that a file or message is the one you expect, and it cannot be reversed. These tools read the input locally and compute SHA-1, SHA-256, SHA-384 or SHA-512 through the Web Crypto API, so a large file does not have to leave the machine.
HMAC adds a shared secret to the hash, which is what most API signatures actually are. Password generation sits in the same group because a password is only as good as its entropy before it is hashed; for storing passwords, use bcrypt or Argon2id rather than any fast hash.
Pick the tool by the job
| What you are doing | Tool | In → out |
|---|---|---|
| Check a download against a published checksum | SHA-256 Hash Generator | file → SHA-256/512 hex digest |
| Sign an API request or webhook | HMAC Calculator | message + secret → HMAC-SHA256 hex/Base64 |
| Generate a password or passphrase | Secure Password Generator | length and rules → random password |
How to choose
- Use SHA-256 unless a publisher or a protocol names another digest — matching their checksum matters more than the digest size.
- Never store passwords with SHA-256, MD5 or any other fast hash; use bcrypt, scrypt or Argon2id with a per-user salt.
- HMAC proves possession of a shared secret; it is not a public-key signature and cannot be verified by a third party.
- A checksum tells you the file arrived intact, not that it is safe to run.
Guides that explain the trade-offs
All 3 tools in this group run in the browser tab. See the full tool index or start from the home page.