Free Hash generator
Choose SHA-256 (recommended), SHA-384, SHA-512, or legacy SHA-1. Text is encoded as UTF-8 before hashing. Output is a continuous lowercase hex string. On insecure origins (some local URLs) Web Crypto may be unavailable — use HTTPS or localhost. Nothing leaves this tab.
How to use this tool
- 1
Open Hash generator
Use it for this task: SHA-256, SHA-384, SHA-512, SHA-1 hashes, Web Crypto support, lowercase hex output - 100% local.
- 2
Add the source text
Paste the content you want to process and choose the algorithm or output style.
- 3
Copy the generated value
Use the generated hash or result for checksums, comparisons, or documentation.
Quick facts
| Runs offline? | Yes — after this page loads, hashing uses only your browser’s Web Crypto implementation. |
|---|---|
| MD5? | MD5 is not exposed by Web Crypto in browsers here. Prefer SHA-256 or SHA-512 for new designs. |
| Is data uploaded? | No. Safe Local Tools is static; your text never leaves this tab. |
| File hashing? | This version hashes UTF-8 text only. For large files, use a desktop CLI or a dedicated file-hash tool. |
Top use cases
- SHA-256, SHA-384, SHA-512, SHA-1 hashes, Web Crypto support, lowercase hex output - 100% local.
- Runs offline?: Yes — after this page loads, hashing uses only your browser’s Web Crypto implementation.
- MD5?: MD5 is not exposed by Web Crypto in browsers here. Prefer SHA-256 or SHA-512 for new designs.
- Is data uploaded?: No. Safe Local Tools is static; your text never leaves this tab.
- File hashing?: This version hashes UTF-8 text only. For large files, use a desktop CLI or a dedicated file-hash tool.
FAQ
Why is SHA-1 marked legacy?▾
SHA-1 is no longer considered collision-resistant for security-sensitive signatures. It remains available for compatibility checks only — prefer SHA-256 or stronger for new work.
Does newline or trailing space matter?▾
Yes — hashing is byte-exact. A trailing newline is a different input than the same line without it.
Is this HMAC?▾
No — this page computes plain digests of UTF-8 bytes. HMAC needs a secret key and a different construction.
Can I hash binary pasted as Base64?▾
Not directly — the input box treats content as text (UTF-8). Decode Base64 to bytes elsewhere, or use the Base64 file tool for byte workflows.
Will the same text always produce the same digest?▾
Yes for a fixed algorithm and UTF-8 input. Changing the algorithm or any character (including invisible Unicode) changes the digest.
Where are secrets processed?▾
Only in your browser memory for this session. Clear the tab or reload when you are finished.