Generate URL-safe, Base64, or hex-encoded opaque bearer tokens with selectable entropy (128-512 bits).
The generator creates a random opaque token after you select an entropy size from 128 to 512 bits and a URL-safe, standard Base64, or hexadecimal representation. The result is intended to be carried as a bearer secret, not interpreted as a claims document. Changing the encoding changes the alphabet and displayed length, but does not add entropy. Generation and encoding remain in the browser, so the token is not uploaded. A common mistake is expecting the value to contain identity, scope, or expiration fields like a structured token.
The entropy control determines how much random token material is requested, while the encoding control selects its textual representation. For byte-aligned selections, dividing the bit count by eight gives the byte count. A 128-bit token contains 16 bytes, so its hexadecimal representation has 32 characters because each byte becomes two hex digits. Regenerating requests another random value.
Hexadecimal, Base64, and Base64url can represent the same underlying bytes without changing their entropy. Standard Base64 uses an alphabet containing '+' and '/', and may include '=' padding. The URL-safe alphabet substitutes '-' and '_' for those characters. Padding conventions can vary, so copy the generated value exactly. Hex is longer, but its length maps directly to the selected byte count.
No. Hex or Base64 decoding can recover the underlying random bytes, but those bytes contain no standardized subject, scope, audience, or expiration fields. The issuing application must keep a separate record that maps the token to its meaning and lifecycle. If you need self-contained claims that recipients can inspect, this opaque-token generator does not create them.
No. For this generator, the selected entropy is the meaningful comparison when the underlying randomness is otherwise equivalent. Hex requires more visible characters than Base64 to represent the same bytes, so length alone can be misleading. For example, 128 bits always equals 16 bytes and therefore 32 hexadecimal characters, regardless of what those characters happen to be.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.