Tools / Hash Generator
Hash Generator
Generate MD5, SHA-1, SHA-256, SHA-384, and SHA-512 digests from text — in both hex and base64 — right in your browser. Nothing is uploaded.
Everything runs locally in your browser — nothing you paste here is sent anywhere.
// About this tool
Hash Generator
This hash generator computes one-way cryptographic digests of your input text using five algorithms at once: MD5, SHA-1, SHA-256, SHA-384, and SHA-512. Each digest is shown in both hex and base64 so you can paste it straight into whatever format a tool expects.
SHA-1 through SHA-512 are computed with the browser's built-in Web Crypto API. MD5 isn't exposed there, so it's computed locally with a compact, well-tested JavaScript implementation — nothing leaves your machine either way.
Hashing is one-way: you can verify a digest by hashing the same input again, but you cannot recover the original text from a digest. This is what makes digests useful for checksums, fingerprinting, and storing non-reversible values.
// When to use it
Verify a file checksum
Compute the SHA-256 of a downloaded file's contents and compare it to the publisher's published checksum to confirm integrity.
Fingerprint a config or payload
Hash a config block or request payload to get a stable identifier you can compare across systems or versions.
Store a non-reversible value
Hash an API key, token, or other secret before storing it, so the plaintext value is never kept.
// Questions
Is my input sent to a server?
No. All hashing happens locally in your browser — SHA via the Web Crypto API and MD5 via a local JavaScript implementation. Nothing is uploaded, and the tool works offline.
Which hashes are supported?
MD5, SHA-1, SHA-256, SHA-384, and SHA-512, each output in both hex and base64.
Can I recover the original text from a hash?
No. Hash functions are one-way by design. You can verify an input by hashing it again and comparing, but you cannot reverse a digest to recover the plaintext.
Is MD5 safe to use?
MD5 and SHA-1 are considered broken for security purposes like password storage or signatures due to collision attacks. Use SHA-256 or stronger for anything security-sensitive; treat MD5 and SHA-1 as suitable only for non-security checksums and compatibility.
// Related tools