Security
Mint API keys, session secrets, and CSRF tokens with real cryptographic randomness.
Tokens are generated locally with crypto.getRandomValues. Nothing is uploaded, logged, or stored.
Hex is the safest choice — universally accepted and easy to validate. base64url packs the same entropy into roughly 25% fewer characters and is safe in URLs and headers. Plain base64 contains + and /, which can clash in URLs. As a rule of thumb: 32 bytes (256 bits) is plenty for API keys and session tokens.
Human-type passwords instead? Use the Password Generator. To sign tokens rather than just hold them, see the JWT Decoder and HMAC Generator.
Create a fresh bearer token per integration and rotate them without touching code.
Generate unpredictable values for CSRF cookies, password-reset links, and invite codes.
Decode JWT header and payload locally, then run security checks: weak algorithms, expiry, risky claims.
Generate strong random passwords with crypto.getRandomValues — pick length and character sets.
Generate Apache/Nginx .htpasswd entries with bcrypt or {SHA} schemes — fully client-side.
Generate bcrypt password hashes with adjustable cost and verify hashes against passwords.
Looking for something else? Browse all tools