Smart Unit ConvertersSmart Unit Converters

Hash Calculator (MD5 / SHA-1 / SHA-256 / SHA-384 / SHA-512)

Compute cryptographic hashes of text or files in your browser. All five major algorithms, no upload.

Utility

Hash Calculator (MD5 / SHA-1 / SHA-256 / SHA-384 / SHA-512)

Generated on April 25, 2026

MD5128 bits · 32 hex chars
(empty)
Legacy file checksums, ETags. Insecure for cryptography.
SHA-1160 bits · 40 hex chars
(empty)
Git commit IDs, legacy systems. Deprecated for security.
SHA-256256 bits · 64 hex chars
(empty)
Bitcoin, TLS certificates, modern integrity checks.
SHA-384384 bits · 96 hex chars
(empty)
TLS 1.3, NSA Suite B. Stronger SHA-2 variant.
SHA-512512 bits · 128 hex chars
(empty)
Server-side password hashing (with salt + bcrypt/argon2 better).
Security note: MD5 and SHA-1 are broken for cryptography (collisions can be deliberately constructed). They're still fine for non-adversarial integrity checks (file checksums, ETags). For passwords, use bcrypt / argon2 / scrypt with salting — never plain hashes.

?What is the Hash Calculator (MD5 / SHA-1 / SHA-256 / SHA-384 / SHA-512)?

The Hash Calculator computes the cryptographic digest of any text or file using the five most common algorithms: MD5 (128-bit, legacy/integrity-only), SHA-1 (160-bit, deprecated for security), SHA-256 (256-bit, the modern default), SHA-384 and SHA-512 (longer SHA-2 variants used in TLS 1.3, NSA Suite B, and high-assurance contexts). All hashing happens in your browser via the Web Crypto SubtleCrypto API (SHA family) and crypto-js (MD5) — your text and files are never uploaded anywhere. Useful for verifying file downloads against published checksums, generating ETags, debugging signed APIs, and learning how cryptographic primitives produce avalanche-effect outputs from any input.

The Formula

Hash function H(message) → fixed-size output. Cryptographic hashes are deterministic, fast, one-way, and exhibit the avalanche effect (1-bit input change flips ~50% of output bits).

Hash Algorithm Reference — Output Sizes & Use Cases

Side-by-side comparison of supported hash functions.

AlgorithmOutput bitsHex charsSecurity statusCommon uses
MD512832BROKEN (collisions known since 2004)Legacy file checksums, ETags
SHA-116040DEPRECATED (collisions since 2017)Git commit IDs, legacy systems
SHA-25625664Secure (recommended default)Bitcoin, TLS, HMAC, modern integrity
SHA-38438496SecureTLS 1.3, NSA Suite B
SHA-512512128SecureLong-output HMAC, high-assurance contexts

Practical Examples

1

Verify an ISO download against its published SHA-256 checksum to detect tampering or corruption.

2

Generate ETags for HTTP caching: hash the response body, send as `ETag: "<hash>"`.

3

Debug HMAC signatures in API integrations — compute the expected SHA-256 of a known payload + secret to compare.

4

Git uses SHA-1 for commit IDs (40-character hex strings) — paste a commit's contents to see its hash.

5

Bitcoin block hashing uses SHA-256 twice (SHA-256(SHA-256(block_header))).

Frequently Asked Questions

Only for non-security purposes (file integrity checks, ETags, deduplication). MD5 is broken — collisions can be deliberately constructed. Use SHA-256 for anything security-related.

Popular Conversions

Jump to a ready-made conversion — useful for quick reference and sharing:

Explore More Tools

Base Converter

Convert between binary, decimal, hexadecimal, and octal number systems.

Unix Timestamp Converter

Convert between Unix epoch timestamps and human-readable dates.

Color Converter

Convert between HEX, RGB, and HSL color formats with live preview.