Developer tool · Identifiers
Generate UUID, ULID and Nano IDs in bulk
Pick a format, choose how many you need, and get identifiers drawn from your browser's own cryptographic random source. UUID v7 and ULIDs carry a millisecond timestamp, so the paste-in inspector can tell you exactly when an ID was made — and why it is or is not valid.
1 · Format & count
UUID v4 · 122 random bitsRandom values come from crypto.getRandomValues. Nothing is uploaded, saved or written to the address bar.
2 · Inspect an ID
UUID · ULID · Nano IDYour identifiers
one per row| # | Identifier | Copy |
|---|
Where the randomness goes
bits you can rely on| Format | Random bits | Structure | Length |
|---|---|---|---|
| UUID v4 | 122 | 6 fixed nibbles, 122 random bits | 36 |
| UUID v7 | 74 | 48-bit timestamp, 12-bit counter, 62 random bits | 36 |
| ULID | 80 | 10 timestamp characters, 16 random characters | 26 |
| Nano ID · default | 126 | 21 characters from a 64-character alphabet | 21 |
Every value is produced by crypto.getRandomValues with rejection sampling, which discards draws that would make any character more likely than another. If the browser offers no cryptographic source, the tool stops and says so instead of quietly using Math.random.
How to use ID Generator
Everything below runs in this tab. Nothing is uploaded, and no account is needed.
Step by step
- Choose the format in Format & count. UUID v4 is pure randomness, UUID v7 and ULID start with a timestamp, and Nano ID takes any length and alphabet you like.
- Set How many from 1 to 1,000, or tap a quick chip for 1, 5, 10, 25, 100, 500 or 1,000. Add a prefix or suffix if your schema needs one, and pick the separator used by the text file.
- For Nano ID, choose an alphabet preset or type your own characters. The hint under the field shows the entropy in bits for the length you chose.
- Press Generate. Every identifier lands in the results table, one per row, with a live count, a character-length summary and a per-row copy button.
- Use Inspect an ID to paste any UUID, ULID or Nano ID and read back its version, variant, embedded timestamp and any validity errors.
Details and limits
Sortability is the real difference
A UUID v4 is 122 random bits, so sorting v4 values as text tells you nothing about creation order. A UUID v7 and a ULID both begin with a 48-bit millisecond timestamp, so lexicographic order matches creation order. That is why v7 and ULID are popular as database keys: they stay index-friendly while still being unguessable.
An identifier is not a secret
The job of these values is uniqueness, not confidentiality. A v4 UUID carries 122 random bits and is unguessable in practice, but a UUID is not a password reset token or an API key by design, and ULIDs deliberately expose their creation time. Never grant access on the strength of an ID alone, and never put a secret in one.
How likely is a collision?
Collision odds follow the birthday bound: about n squared over two to the power of the random bits. For a UUID v4 that is roughly 3 × 10¹⁵ IDs before the odds of one collision reach one in a million. A ULID's 80 random bits give about 1.5 × 10⁹, and a 21-character Nano ID with the 64-character alphabet about 1.3 × 10¹⁹. Short custom alphabets collapse fast: ten digits over ten characters is only 33 bits.
Everything happens in this tab
Values come from crypto.getRandomValues with rejection sampling, so there is no modulo bias, and the tool refuses to run rather than falling back to Math.random. Nothing is uploaded, nothing is stored, and the monotonic counters that keep v7 and ULID ordered inside a single millisecond live in memory only — reload the page and they restart.
Read the guide on how UUID v4 is built · The single-ID UUID generator · Install for offline use
Frequently asked questions
What is the difference between UUID v4 and UUID v7?
A UUID v4 is 122 random bits with the version and variant nibbles fixed, so it says nothing about when it was made. A UUID v7 puts a 48-bit Unix millisecond timestamp first, then twelve bits of counter and sixty-two random bits, so sorting v7 values as text sorts them by creation time.
How do I generate many IDs at once?
Set the count field to anything from 1 to 1,000, or tap a quick chip. The whole batch appears in one table with a per-row copy button, and Copy all, Download .txt and Download .csv all write the same set. The separator you choose controls how the text file joins the values.
Can I tell when a UUID v7 or ULID was created?
Yes. A UUID v7 stores Unix milliseconds in its first 48 bits, and a ULID stores them in its first ten Crockford base32 characters. Paste either into Inspect an ID and the tool decodes the timestamp to ISO 8601 in UTC and to your own local time, and reports whether the value is a valid UUID or ULID at all.
What is a ULID and how is it different from a UUID?
A ULID is 26 characters of Crockford base32: ten characters of millisecond timestamp followed by sixteen characters of randomness, eighty bits of it. It is case-insensitive, URL-safe and sortable, and it is easier to read aloud than a hyphenated UUID. It carries less randomness than a v4 UUID, so it suits shorter or lower-volume keys.
Can I use these IDs as passwords or API keys?
No. Treat them as identifiers, not secrets. Use the password generator for anything that authenticates a person or a machine. UUIDs and ULIDs are also often logged, indexed and copied into URLs, which is exactly what you do not want for a credential.
Is anything sent to a server?
No. Generation, formatting and inspection all run in this tab using the browser's own cryptographic random source. Nothing is written to the URL or to local storage, and closing the tab discards everything you generated.