Polymorpher
The Utility Factory — Free Developer Tools
Convert, transform, beautify & decode — all in one place.
⚡ All Tools
Did You Know?
Select a tool from the sidebar to get started, or explore our free developer utilities.
About this Tool
Hash Generator — MD5, SHA1, SHA256, SHA384, SHA512 & HMAC
Generate cryptographic hash digests from any text using industry-standard algorithms: MD5, SHA1, SHA256, SHA384, and SHA512. Supports HMAC (Hash-based Message Authentication Code) with custom secret keys for authenticated hashing.
Select a specific algorithm or generate all digests simultaneously. HMAC mode adds a secret key to the hash function, producing authenticated message digests used in API authentication, webhook verification, and data integrity checks.
All hashing happens server-side using .NET's System.Security.Cryptography library — the same battle-tested implementation used by enterprise applications worldwide. Your input text is processed and immediately discarded — zero data retention.
Live Examples
Example 1 — Hash a password (all algorithms)
Input: MySecretPassword
Output:
MD5: a847912ca3aee891c4b58e0e0e02a4b0 SHA1: 4bcbb2e3ee0e9143f0e80e0a0f18c5f2c7bf2f3b SHA256: 8f0e2f76e22b43e2868c80…(64 hex chars) SHA384: …(96 hex chars) SHA512: …(128 hex chars)
Example 2 — HMAC-SHA256 for webhook verification
Input: {"event":"payment.completed","id":"evt_123"}
Secret Key: whsec_abc123
Output:
HMAC-SHA256: 3d5e8a…(64 hex chars)
Compare this digest against the X-Signature header from Stripe, GitHub, or any webhook provider to verify authenticity.
Example 3 — File integrity check
Paste the contents of a text file and compare the SHA256 output against a known checksum to verify the file has not been tampered with.
Algorithm Comparison
| Algorithm | Digest Length | Security Status |
|---|---|---|
| MD5 | 128-bit (32 hex) | Broken — do not use for security |
| SHA1 | 160-bit (40 hex) | Deprecated — collision attacks exist |
| SHA256 | 256-bit (64 hex) | Recommended for most use cases |
| SHA384 | 384-bit (96 hex) | Secure — used in TLS 1.3 |
| SHA512 | 512-bit (128 hex) | Secure — best for high-security needs |
When to Use
- Verifying file integrity (comparing checksums)
- Generating HMAC signatures for API authentication
- Verifying webhook payloads from Stripe, GitHub, Slack, etc.
- Creating content-addressable identifiers for caching
When Not to Use
- Password storage: Use bcrypt, scrypt, or Argon2 — not raw SHA256
- Encryption: Hashing is one-way; use AES or RSA for encryption
- MD5 for security: MD5 is cryptographically broken; only use it for non-security checksums
Related Tools: JWT Decoder · Base64 Encoder · URL Encoder