Random from the platform
There is no Math.random in these values. Each byte comes from crypto.getRandomValues, the platform's cryptographic generator, and the page has no fallback that could quietly produce something weaker.
Pikkola Identifier Studio, tool No. 51
Four identifiers in one tab: UUID v4, time-ordered UUID v7, ULID and NanoID. Choose how many, pick an output shape, and every value comes from the browser's own random source. Paste one back and the page shows its version, its variant and the millisecond it was minted. Nothing is uploaded and nothing is kept.
The workbench
One tab makes values, one reads them, one keeps the numbers that decide whether any of this is safe. They share the same engine and keep their settings in this browser.
Turn on the kinds you want together. UUID v7 counts inside a millisecond, so the order it prints is the order it sorts.
ready
Kinds
Counted in this tab, from the values above. A duplicate is checked across the whole run, not only inside one kind.
One value per line. The page reads the version nibble, the variant, and for v1, v6, v7 and ULID the millisecond the value was made.
0 of 0
Nothing pasted yet. A sample above is enough to see what the reader finds.
Choose a row to see its fields.
Bit layout
Hex, nibble by nibble
The numbers behind the guarantee: how many random bits each kind carries, what a collision would take, and how to write each value in a column, a URL or a request body.
| Kind | Random bits | 50 percent at | After a million |
|---|
The birthday bound, n times n minus one, over two to the power of the bits plus one. The half column is the number of values at which a collision is as likely as not.
Logged odds for one batch. A billion values a second for a century is still far below the v4 and NanoID lines.
| Shape | Example | Where it goes |
|---|---|---|
| UUID, canonical | 3b241101-e2bb-4255-8caf-4136c566a962 | A text column, an API id, a URL path |
| UUID, URN | urn:uuid:3b241101-e2bb-4255-8caf-4136c566a962 | XML documents and registries that ask for a URN |
| UUID, braced | {3b241101-e2bb-4255-8caf-4136c566a962} | Older Windows and COM interfaces that expect a GUID string |
| ULID | 01ARZ3NDEKTSV4RRFFQ69G5FAV | Sortable keys where a 36-character string is too long |
| NanoID | V1StGXR8_Z5jdHi6B-myT | Short links, file names, client ids |
| SQL column | uuid, char(26), varchar(64) | Postgres has a uuid type; MySQL is often binary(16); a NanoID needs its own length |
A UUID is 36 characters with hyphens and 32 without. A ULID is always 26. A NanoID is exactly as long as you asked, so the column has to match the setting.
How it holds up
Nothing here is a lookup service or a central counter. Every value is made alone, in the tab, and has to be unique without asking anyone.
There is no Math.random in these values. Each byte comes from crypto.getRandomValues, the platform's cryptographic generator, and the page has no fallback that could quietly produce something weaker.
A v7 value starts with a 48-bit millisecond count, so new rows land at the end of a B-tree instead of scattering through it. Inside one millisecond a 12-bit counter keeps the order exact, and 62 random bits keep the value unguessable.
122 random bits is enough that a collision will not happen, and that is all it promises. v4 reveals nothing, v1 and v6 reveal a clock and often a node, and v7 reveals when. A token with a lifetime needs more than an identifier.
| Kind | Bits | What it does |
|---|---|---|
| UUID v4 | 122 random | Version and variant are fixed bits; the rest is one random draw. Nothing in the value says when or where it was made. |
| UUID v7 | 48 + 74 | 48 bits of millisecond time, then a 12-bit counter and 62 random bits. Sorts by time, and stays unguessable inside the millisecond. |
| ULID | 48 + 80 | The same 48-bit millisecond clock, 80 random bits, written in Crockford base32 so the value is 26 characters and case-insensitive. |
| NanoID | length x log2(alphabet) | Your alphabet and your length. 21 characters of the 64-symbol default is about 126 bits, and no part of the value carries a time. |
Questions
Next door
The same rule everywhere: no account, no upload, nothing leaves the tab.