Compute SHA-256, SHA-384, and SHA-512 digests locally with the Web Crypto API for checksums, integrity checks, and documentation fingerprints. Digests are one-way: matching a hash means testing candidate inputs, not reversing the function. This tool is for verification—not a substitute for proper password hashing (Argon2, bcrypt, and similar) on a server. Legacy MD5 and SHA-1 are omitted because of weak collision resistance. For file digests, use File Checksum Verifier; for keyed MACs, use HMAC Generator.
Not practically. Hashes are one-way. Matching a hash means testing candidate inputs, which is why strong secrets and salts matter in security systems.
Both are considered broken for collision resistance in modern security contexts. This tool sticks to stronger SHA-2 family digests. Need to compare a vendor SHA-1 file checksum? Use File Checksum Verifier (legacy label).
No. Digests are computed with Web Crypto inside your browser session.
This Hash Generator is for pasted text. File Checksum Verifier hashes local files (optional expected-hash match). HMAC Generator needs a shared secret for message authentication. Password Generator creates random secrets — do not store passwords as raw SHA digests.