Random Token Generator

Generated 2 base64url token(s) from 32 random byte(s) (256 bits of entropy each).

How it works

• Read the byte length, count and encoding.
• Drew that many bytes from the platform CSPRNG.
• Encoded the bytes as base64url.
• Reported the exact entropy, which equals the byte length because every byte is uniform.

• The entropy of a token is fixed by its byte length; the encoding changes the text, not the randomness.
• Generated tokens stay in your browser and are never sent or stored.

Methodology

1. Read the requested byte length, count and encoding.
2. Draw the exact number of bytes from the platform CSPRNG.
3. Encode the bytes with the standard alphabet for the chosen encoding.
4. Report the entropy as byteLength × 8 bits, which is exact because each byte is uniform.

Usage

1. Choose how many random bytes each token should contain.
2. Pick the encoding you need for your protocol.
3. Generate one or more tokens and copy the value.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

Two reproducible 32-byte base64url tokens

{
  "byteLength": 32,
  "count": 2,
  "encoding": "base64url",
  "seed": "example"
}

A 16-byte hex token

{
  "byteLength": 16,
  "encoding": "hex",
  "seed": "example"
}

A 20-byte base58 token

{
  "byteLength": 20,
  "encoding": "base58",
  "seed": "example"
}

Limitations

Tokens are bearer secrets

A token's security is the randomness behind it plus the discipline of the system that accepts it. Store a hash of the token rather than the token itself, bind it to a subject and an expiry, and compare in constant time.

This tool gives you the random material and an exact entropy figure. It deliberately does not choose a token lifetime or a storage strategy, because those depend on your protocol.