HEX2×
0-9 a-f
Every byte dey use two hexadecimal characters. The length clear and almost every language and tool support am.
Good for: Config files, command line, logs and debugging.
Key generator
256 bits
Very high strength
Encoding
If you change setting, fresh key go generate by itself; use the button repeat with the same setting.
Keys wey generate
E dey generate…
Random source na crypto.getRandomValues(), wey secure for cryptography. Key no go remain after refresh; copy or download am keep for secret manager.
Encoding formats
The same random bytes fit show with different text encoding. Choose the format wey your URL, JSON, config file or protocol need.
Base64≈1.34×
A-Z a-z 0-9 + / =
Compact binary-to-text format, but +, / and = need escape for URL and some file names.
Good for: JSON/XML transfer and normal text storage.
Base64URL≈1.34×
A-Z a-z 0-9 - _
URL-safe Base64 wey use - and _ and remove = padding.
Good for: JWT, OAuth tokens, cookies and URL parameters.
Base32≈1.6×
A-Z 2-7
E no care about capital letter and e avoid 0/O and 1/I/L wey fit confuse person.
Good for: TOTP secrets, DNS records, barcodes and manual entry.
Questions people dey ask
This key generator secure?
Yes. E use crypto.getRandomValues from operating system secure random source, no be Math.random.
Dem dey send or record the keys?
No. Generation and encoding happen for browser; no history dey save and refresh go clear the result.
I fit use am as login password?
The keys na for machine secrets like API key, encryption key and token. Use password manager for password wey person go type.
Two keys fit be the same?
E possible for theory, but the chance small well-well for recommended length. 32-byte key get 2^256 possible values.
How I go keep the key?
Keep long-term key for secret manager or protected environment variable. No put am for source code, chat or log, and rotate am sometimes.