Password Generator
Cryptographically secure passwords generated entirely in your browser.
Safe Password
16 charsGood for most accounts. Mix of uppercase, lowercase, digits and symbols.
Strong Password
32 charsHigh-entropy passwords for sensitive accounts, master passwords and secrets.
Database Password
32 chars · connection-string safeExcludes characters that break connection strings: ' " ; \ space
Passphrase Generator
Random words combined into a phrase that's easy to remember, hard to crack.
Passphrase
4 words · with numberEach word capitalized, separated by dashes, with a 2-digit number appended.
API Key Generator
Cryptographically secure API keys in every common format.
Hex
256-bit · 64 charsRaw hex-encoded random bytes. Universally supported, easy to inspect.
Base64
256-bit · 32 bytesURL-safe Base64 — replaces +/= with -_ with no padding. Safe in URLs, headers and JSON without escaping.
Base58
256-bit · ~44 charsNo ambiguous characters (0 O l I). Used by Bitcoin, IPFS and Stripe.
Alphanumeric
256-bit · 43 charsLetters and digits only — no symbols. Safe in any context without escaping.
Prefixed Key
custom prefix · 256-bitAdd a prefix like sk_live_ or pk_test_ to any format.
JWT Secret Generator
Secure HMAC signing secrets for HS256, HS384 and HS512 — URL-safe Base64 encoded.
HS256
256-bit · 32 bytes · 43 charsHMAC-SHA256. Minimum recommended secret length. Suitable for most applications.
HS384
384-bit · 48 bytes · 64 charsHMAC-SHA384. Stronger than HS256 with negligible performance difference.
HS512
512-bit · 64 bytes · 86 charsHMAC-SHA512. Maximum strength HMAC secret. Recommended for high-security tokens and long-lived credentials.
Encryption Key Generator
Symmetric encryption keys and IVs/nonces, hex-encoded and ready to use.
AES-128
128-bit · 16 bytes · 32 hex charsSufficient for most use cases. Fast on all hardware including devices without AES-NI.
AES-192
192-bit · 24 bytes · 48 hex charsUncommon in practice but required by certain compliance standards (e.g. some NIST profiles).
AES-256
256-bit · 32 bytes · 64 hex charsThe industry standard. Recommended for all new applications and long-term data protection.
ChaCha20
256-bit · 32 bytes · 64 hex charsModern stream cipher. Preferred over AES on devices without hardware acceleration (e.g. mobile, IoT).
IV / Nonce
AES-GCM Nonce
96-bit · 12 bytes · 24 hex charsStandard nonce size for AES-GCM. Must be unique per encryption with a given key — never reuse.
AES-CBC IV
128-bit · 16 bytes · 32 hex charsInitialisation vector for AES-CBC mode. Must be random and unpredictable for each message.
ChaCha20 Nonce
96-bit · 12 bytes · 24 hex charsNonce for ChaCha20-Poly1305. Like AES-GCM, uniqueness per key is critical to security.
NanoId & UUID
Modern random identifiers — compact, URL-safe and time-sortable.
UUID v4
128-bit · RFC 4122Randomly generated UUID. The standard choice for unique identifiers — universally supported across all databases and languages.
UUID v7
128-bit · time-ordered · RFC 9562Like UUID v4 but with a millisecond timestamp prefix — monotonically sortable and index-friendly as a database primary key.
NanoID
21 chars · URL-safeThe modern alternative to UUID. Uses A-Za-z0-9_- — safe in URLs, filenames and HTML attributes without encoding.
TOTP / 2FA Secret
Base32-encoded seeds for Google Authenticator, Authy and any RFC 6238 TOTP app.
TOTP Secret (160-bit)
20 bytes · RFC 6238 standardThe recommended size per RFC 6238. Compatible with all TOTP apps. Pass this to your otpauth:// URI or QR code generator.
TOTP Secret (256-bit)
32 bytes · higher entropyHigher entropy seed for use with TOTP-SHA256 or TOTP-SHA512 where supported. Check your library's documentation before using.
OAuth Credentials
Matched client ID and secret pairs — each row across both columns is a single credential pair.
Client ID
32 chars · alphanumericPublic identifier for the OAuth client. Safe to expose in client-side code and redirect URIs.
Client Secret
256-bit · 64 hex charsKeep this server-side only. Never expose in client code, logs or version control.
Hashing Salts
Random salts for password hashing algorithms — hex-encoded and ready to use.
bcrypt
128-bit · 16 bytes · 32 hexFor implementations requiring an explicit salt. Most bcrypt libraries generate this automatically — check yours before using.
Argon2
128-bit · 16 bytes · 32 hexRecommended minimum salt for Argon2i and Argon2id. Pass directly to your Argon2 hashing call as the salt parameter.
PBKDF2
256-bit · 32 bytes · 64 hexRecommended salt length for PBKDF2-SHA256 and PBKDF2-SHA512 per NIST SP 800-132.