Cryptographic Hash & Base64 Generator
Compute SHA-256, SHA-512, SHA-1, and MD5 checksums or encode and decode standard & URL-safe Base64 strings. Engineered with 100% client-side Web Crypto — zero requests sent to servers.
Instant Cryptographic Hash Generator
Compute SHA-256, SHA-512, SHA-1, and MD5 hashes entirely in your browser. Nothing is ever sent over the network.
Never leak keys in Slack or Git. Use SnapSend to create self-destructing links that burn automatically once read.
Password Crack Time Calculator
Test how many years modern RTX 4090 GPU clusters need to brute-force a password.
Cryptographic Password Generator
Generate cryptographically secure passwords using CSPRNG entropy.
Cryptographic Hash Functions Compared
A cryptographic hash function maps arbitrary data to a fixed-size bit string. Understand the security profiles, output lengths, and intended use cases for each standard algorithm:
| Algorithm | Digest Length | Collision Resistance | Security Status | Primary Use Cases |
|---|---|---|---|---|
| SHA-256 | 256 bits (64 hex) | Very High (None Found) | Industry Standard | Bitcoin / Blockchain, TLS / SSL certificates, SnapSend zero-knowledge key derivations, file integrity verification. |
| SHA-512 | 512 bits (128 hex) | Maximum (Quantum Resilient) | Highly Secure | Government-grade digital signatures, high-security HMAC authentication, 64-bit architecture native speed hashing. |
| SHA-1 | 160 bits (40 hex) | Broken (SHAttered Attack) | Deprecated | Legacy Git commit object IDs (currently migrating to SHA-256), legacy BitTorrent v1, older software verification. |
| MD5 | 128 bits (32 hex) | Severely Broken (Instant) | Insecure for Crypto | Non-cryptographic cache key generation, file download corruption checks (non-adversarial), deduplication indexing. |
Understanding Base64 vs. URL-Safe Base64 (RFC 4648)
Base64 is a binary-to-text encoding scheme that translates raw 8-bit bytes into a sequence of 64 printable ASCII characters. However, web contexts introduce unique challenges:
Standard Base64
Uses the 64-character alphabet: A-Z, a-z, 0-9, along with + and /, padded with =.
Problem in Web: The characters + and / have reserved meanings in URI syntax. A + is interpreted by web servers as a space, and / indicates path segments, causing corrupted payloads.
URL-Safe Base64 (Base64URL)
Replaces + with - (minus) and / with _ (underscore), and typically removes trailing = padding.
Where it is used: JSON Web Tokens (JWT), OAuth2 authorization code flows, URL query parameters, and SnapSend's client-side zero-knowledge decryption keys in URL hash fragments.