Hash Generator

Generate MD5, SHA-1, SHA-256, SHA-384 or SHA-512 digests in hex or Base64, computed locally.

Security ToolsRuns in your browserFree, no sign-up

Options

Algorithm

Output encoding

Uppercase output

Input text

Digest

Output appears here as you type.

Ctrl + Enter to run

About the Hash Generator

Produces MD5, SHA-1, SHA-256 and SHA-512 digests of whatever you paste. The everyday uses are integrity checking, deduplication and content-addressed identifiers, where SHA-256 is the sensible default.

Two cautions. MD5 and SHA-1 are cryptographically broken with practical collision attacks, so never rely on them where an attacker benefits from forging a match. And none of these belong anywhere near password storage: they are built to be fast, which is exactly the property an attacker wants. Use Argon2id, scrypt or bcrypt for that.

Frequently asked questions

Can I use this to hash passwords?

No — and this is the single most important thing to know about hashing. MD5, SHA-1 and even SHA-256 are designed to be fast, which is exactly wrong for passwords: a modern GPU computes billions of SHA-256 hashes per second. Password storage requires a deliberately slow, salted algorithm: bcrypt, scrypt, or Argon2id (the current recommendation).

Why is MD5 still offered if it is broken?

Because "broken" means collision-resistance is broken, not that the function is useless. MD5 remains the standard checksum for file-integrity verification, ETags, Gravatar URLs and countless legacy APIs. It is fine when you are detecting accidental corruption and useless when defending against a deliberate attacker.

Why is MD5 not computed by the browser like the others?

The Web Crypto API deliberately omits MD5 precisely because it is broken, so crypto.subtle.digest cannot produce it. This page ships a small self-contained MD5 implementation, verified against the RFC 1321 test vectors, while SHA-1 through SHA-512 use the browser's native, hardware-accelerated implementation.

Should I use SHA-256 or SHA-512?

SHA-256 for almost everything — it is the de facto standard and is hardware-accelerated on every modern CPU. SHA-512 is not "more secure" in any way that matters at these sizes, though it is actually faster than SHA-256 on 64-bit hardware for large inputs. Pick SHA-256 unless a specification tells you otherwise.