How to use this tool
- Choose 32, 48 or 64 random bytes and an output encoding.
- Generate fresh keys locally. Reveal only when needed.
- Copy explicitly, then store the key in your application’s secret manager. Clear this page when finished.
Read a secret’s format without reusing the example
Choose 32 bytes and hex when a service expects a 256-bit random secret encoded as text.
Input
32 random bytes · hex · one key · no prefix Fixed test bytes: 0xab repeated 32 times
Expected output
{
"keys": [
"abababababababababababababababababababababababababababababababab"
],
"entropyBits": 256,
"length": 64,
"prefixLength": 0
}The fixed test output illustrates the 64-character format; it is public demonstration data, not a usable credential. A real generation uses fresh Web Crypto randomness. Thirty-two bytes represent 256 bits; a nonsecret prefix contributes no entropy.
More examples
- 32 bytes encode as 64 hex characters and represent 256 bits of entropy.
- 48 bytes encode as 64 unpadded base64url characters. A prefix adds no entropy.
- Alphanumeric output uses rejection sampling and rounds length upward to meet the chosen entropy.
Know the limits
These are random strings, not activated credentials for OpenAI, AWS or another provider. Clipboard managers and downloaded files may retain secrets.
Common questions
Does a prefix make a key stronger?
No. Only the randomly generated portion contributes entropy.
Are generated keys stored here?
No. Keys remain in page memory until you reset, navigate or close the tab. Your operating system may retain copied or downloaded data.