Put it to work
Encode 32 bytes as Base64URL to get a 43-character unpadded secret.
From input to output
- Open Secrets & tokens and load the example.
- Read the format notes, choose your options, and replace the example with your input. Start with test data instead of sensitive information.
- Run the tool and inspect the result and status. If an error appears, correct the input format and run it again.
- Copy the output or download a file. Generated and converted results are not saved automatically.
Same entropy, different string lengths
32 random bytes contain 256 bits of randomness. Hex produces 64 characters, padded Base64 44, and unpadded Base64URL 43. A longer encoding does not add entropy. Every generation should produce a different value; the example below explains lengths and must not be reused as a secret. When rotating a secret, coordinate configuration changes and rollout order across all consumers.
Example input
Random bytes: 32 Count: 5
Reading the result
Hex: 64 characters Base64: 44 characters (with padding) Base64URL: 43 characters (without padding)
Details that matter
Format and meaning
Bytes measure the random input. Hex uses two characters per byte.
Using it correctly
Base64 uses + and /, which may require URL escaping. Choose Base64URL for URLs.
Common pitfalls
This does not issue API keys for external services. Use the values in your own server configuration.
Supported scope and limits
1–1,024 bytes; up to 100 values per batch
Split inputs that exceed the limit. If a format or algorithm is unsupported, choose a tool that matches your requirements instead of silently changing the format.
What happens to your data?
Tools run in your browser. DNS lookup sends the queried domain to the named external provider. Ads may appear on home, guide, and workspace pages according to settings.
Open tool