Choose the random bits. Then choose how to represent them.
2–94 unique printable ASCII characters. No spaces or duplicate characters.
Changing an option replaces the current results. Nothing is saved or sent.
Downloads may contain secrets. Protect the file and only export when needed.
Generated entirely in your browser.
Nothing is sent to our server.
A 32-byte sample contains 256 random bits. It encodes as 64 hexadecimal characters, 44 padded Base64 characters or 43 unpadded Base64URL characters. Those strings represent the same amount of randomness. An entropy request that is not a whole number of bytes rounds up for byte encodings; the display reports the actual amount generated.
Hexadecimal uses only 0–9 and a–f. Standard Base64 can include +, / and = padding. Base64URL uses - and _ instead of + and / and omits trailing padding here. A URL-compatible alphabet does not make it safe to put a secret in a URL: logs, browser history and referrers can expose it. Pass secrets through the receiving system’s intended protected channel.
Custom mode selects uniformly from 2–94 unique printable ASCII characters using rejection sampling. The character count rounds up so length × log₂(alphabet size) meets your requested entropy. It is not a byte encoding and is not necessarily decodable back to a whole-byte sample. Duplicate alphabet characters are rejected rather than silently biasing the distribution.
This creates random material, not a complete reset system. The server still needs secure storage, expiry, single use, an authenticated workflow and protection against leakage. Follow your application’s design requirements.
No. A text download is created locally only when you request it. The file remains on your device and may contain secrets; protect or delete it according to your workflow.