A random string generator draws each character independently from a pool. This random string generator offers four pools: letters, letters and numbers, hexadecimal, and URL-safe characters (A–Z, a–z, 0–9, hyphen, underscore). Every position is a uniform draw via crypto.getRandomValues. There is no “at least one digit” rule. If you need that rule, use the Password Generator.
A UUID is a formatted 128-bit identifier. This page will not emit hyphens and version bits. For that layout use the UUID Generator. Integers belong on the Random Number Generator.
Use this page for an API token, a filename suffix, or a hex nonce. The value stays in the tab. It is not uploaded and not stored. Treat hex and URL-safe output as unpredictable tokens, not as a complete account-security design.
Enter from the length field or the list runs generate. Empty length and values outside 1–256 are errors. Labels sit above the controls.
Length 8 and hexadecimal can produce a8f0c21d. Length 16 and letters and numbers produces a mixed token with no guaranteed digit. Length 22 and URL-safe is a common size for a compact token. Script-looking text in the length field is rejected as not a number.
If a system later lowercases the token, prefer hexadecimal or accept that A and a collapse. URL-safe output avoids plus and slash, which is why it is safer in a query string than classic Base64. This page does not add padding equals signs.
Generate twice for two independent tokens. There is no seed. Closing the tab discards the field. If you needed many lines of UUIDs, switch pages instead of pasting hyphens by hand.
The pool sizes are fixed: 52 letters, 62 alphanumerics, 16 hex digits, 64 URL-safe characters. Wider Unicode letters are out of scope. They would make copy/paste and fonts the problem instead of the token.
A 32-character hex string is 128 bits of alphabet, which is why people use it as a stand-in for a short key. It is still not a UUID. It has no version nibble and no hyphens. A 16-character alphanumeric string is shorter and easier to read on a whiteboard. Pick the set that matches the system that will store the token. If that system later case-folds, hex is the safer of the mixed-case pools.
Do not generate a token and then email it to yourself “for safekeeping” on an open list. The page kept the value local. The inbox is not local. Clear the field when the token is in the place it belongs.
Length 1 is allowed because a single hex digit is a valid ask for a tiny fixture. It is a poor secret. The status will not lecture you. The limits paragraph already said this is not a password-class builder.
Uniform draws from the chosen set using crypto.getRandomValues. For passwords with guaranteed character classes, use the Password Generator.
No. This page draws uniformly. The password page forces each selected class to appear.
No. Use the UUID Generator for the 8-4-4-4-12 form and version bits.
A–Z, a–z, 0–9, hyphen, and underscore. No plus, slash, or equals.
crypto.getRandomValues. If it is missing, generation stops.
