Pikkola Identifier Studio, tool No. 51

Make an ID. Then read it back.

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.

4
kinds in one run
100
values at a time
0
requests sent

The workbench

Generate, parse, look it up

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.

One run, up to a hundred

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

values
Case applies to UUID and ULID. A NanoID keeps the case its alphabet gives it.
The button makes new values every time, even with the same settings.
This run -

            

What came back-

Counted in this tab, from the values above. A duplicate is checked across the whole run, not only inside one kind.

How it holds up

An identifier is a promise about collisions

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.

01

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.

02

v7 puts time first

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.

03

An ID is not a secret

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.

Where the bits go
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

The ones that come up

Are these values safe to use as database keys?

Why use UUID v7 instead of v4?

Can two values collide?

Why does URN only apply to UUID?

Is anything uploaded or stored?

Does a UUID leak information?

What is NanoID, and is it a standard?

Next door

Three tools that pair with an ID

The same rule everywhere: no account, no upload, nothing leaves the tab.