Fingerprints for strings you paste. Verify a downloaded ISO on the file SHA-256 page or with a desktop hash tool.
You pasted a webhook secret into a docs example and want the hex digest. That is a string hash. You downloaded an ISO and the site printed a SHA-256 — that is a file hash. Mixing them is how people “verify” the wrong object.
Two doors
- Hash generator hashes text you type. It is not encryption. Rainbow tables exist for short passwords; do not treat a hash as storage.
- HMAC / password check is a keyed MAC plus a naive strength readout — not a breach database, not bcrypt tuning.
- File SHA-256 owns checksums of files. SHA-256 only. Large images of disks need
Get-FileHash/sha256sum.
Need reversible confidentiality? AES. Need to read a JWT payload? Decode, do not hash it.
Text digest vs file verify
Hash generator is for strings. File SHA-256 is for a downloaded installer — SHA-256 only, not antivirus. HMAC is a keyed test, not a password manager. Large files may exceed the tab (~32 MB).