Use this guide as an operational checklist, then run the linked tools to validate changes immediately.
Generate SHA-384 digests in a focused workflow. SHA-384 is a one-way hash function and cannot be reversed.
Generate MD5, SHA, and HMAC digests for integrity checks, fixture snapshots, and signature debugging workflows, with reliable byte-level troubleshooting guidance for release engineering, API security, and incident response operations.
It computes digest output for plain text, file input, batch lines, and HMAC secret modes in a single focused interface.
It helps compare expected values from APIs, docs, CI pipelines, and security checks without leaving the browser.
It surfaces repeatable checks for encoding, newline handling, and algorithm selection so signature mismatches are easier to isolate.
Text hash
svc_42
HMAC input
payload + shared secret
File checksum input
artifact.tar.gz
SHA-256 sample
7f83b1657ff1fc53b92dc18148a1d65d...
HMAC sample
d2f5c5a7d2e90f1a...
Verification note
Always compare digests generated over identical bytes, including line endings and charset.
Release checklist note
Store expected checksums with artifact metadata so deployment jobs can verify integrity automatically.
Using SHA-1 for new security usage
Prefer SHA-256 or stronger algorithms.
Mismatched input encoding
Confirm UTF-8 and exact newline handling across systems.
Wrong secret in HMAC mode
Verify secret, algorithm, and payload byte order.
Comparing hex vs Base64 output directly
Normalize encoding representation before diffing results across tools.
Hidden newline appended by shell
Check whether source command added trailing newline and recompute with exact bytes.
Expecting hash equality across transformed payloads
Any byte-level modification changes output; hash the original canonical payload only.
Hash Generator should be treated as a repeatable validation step before merge, release, and handoff.
Is MD5 still safe for security?
MD5 is not recommended for security-critical integrity guarantees.
Why are two hashes different?
Small byte-level differences, including spaces and line endings, change hash output.
Can I hash files directly?
Yes. Use file mode for binary-safe digest generation.
When should I use HMAC instead of plain hash?
Use HMAC when authenticity matters and both parties share a secret key.
Can hash output prove file safety?
It proves integrity relative to a trusted source hash, but not malware safety by itself.
How do I operationalize checksum verification?
Automate digest checks in CI/CD and fail deployments when expected and actual values differ.