Skip to main content
Screendesk
Free tool

UUID Generator

Generate random v4 or time-ordered v7 UUIDs and GUIDs, up to 500 at a time. Validate and inspect any UUID you paste.

Open source on GitHub

Generate UUIDs

Version
 

v4 UUIDs carry 122 random bits from your browser’s cryptographic random number generator.

Validate and inspect

Accepts hyphenated, braced, urn:uuid: or 32-character forms.

Runs entirely in your browser. Nothing you paste here is uploaded or stored.

Versions

UUID versions compared. What each version encodes and when to use it.

UUID versions defined in RFC 9562
VersionBuilt fromUse it for
v1Timestamp (100 ns since 1582) + clock sequence + node ID, often the MAC addressLegacy systems. Leaks the generating host and time.
v3MD5 hash of a namespace UUID and a nameDeterministic IDs from names. Prefer v5.
v4122 random bitsThe default for most applications and APIs.
v5SHA-1 hash of a namespace UUID and a nameDeterministic IDs, e.g. the same URL always maps to the same UUID.
v6v1 fields reordered so the timestamp sorts firstMigrating v1 systems to sortable IDs.
v748-bit Unix millisecond timestamp + 74 random bitsDatabase primary keys: sortable by creation time, index-friendly.
v8Custom, vendor-defined layoutExperimental or application-specific formats.
Nil / MaxAll zeros (00000000-…) or all ones (ffffffff-…)Sentinel values meaning “no UUID” or “upper bound”.
Format

Anatomy of a UUID. 32 hex digits in five groups: 8-4-4-4-12.

UUID field layout
FieldLengthWhat it holds
time_low / unix_ts_ms8 hexFirst 32 bits. In v7, the first 48 bits (8 + 4 hex) are the Unix time in milliseconds.
time_mid4 hexNext 16 bits.
version + time_hi4 hexThe first hex digit is the version: 4 in …-4xxx-…, 7 in …-7xxx-….
variant + clock_seq4 hexThe first hex digit is 8, 9, a, or b for standard (RFC 9562) UUIDs.
node12 hexFinal 48 bits: random in v4 and v7, a node ID in v1.
FAQ

Frequently asked questions

What is the difference between a UUID and a GUID?

They are the same thing. GUID (globally unique identifier) is Microsoft’s name for the 128-bit identifier standardised as a UUID (universally unique identifier) in RFC 4122, now RFC 9562. Microsoft tools often display GUIDs in uppercase and wrapped in braces, which you can switch on above.

Should I use UUID v4 or v7?

Use v7 for database primary keys and anything you want sorted by creation time: its leading timestamp keeps B-tree indexes compact and inserts sequential. Use v4 when an ID must not reveal when it was created, such as public tokens or URLs. Both are 128 bits and work in any UUID column.

Can two generated UUIDs collide?

In practice, no. A v4 UUID has 122 random bits, so you would need to generate about 2.7 quintillion UUIDs to have a 50% chance of a single duplicate. v7 UUIDs combine a millisecond timestamp with 74 random bits, and this generator increments a counter within the same millisecond so a batch stays unique and in order.

Are these UUIDs generated securely?

Yes. v4 UUIDs come from crypto.randomUUID() and the random parts of v7 UUIDs from crypto.getRandomValues(), the browser’s cryptographically secure random number generator. They are created on your device and never sent anywhere. Even so, a UUID is an identifier, not a secret: do not use one as a password or API key.

How do I check which version a UUID is?

Look at the first character of the third group: in 3f2b8c1e-9d4a-4e6f-…, the 4 means version 4. The first character of the fourth group shows the variant: 8, 9, a, or b means a standard RFC 9562 UUID. Paste any UUID into the inspector above to see its version, variant, and, for v1, v6, and v7, the time it was created.

Customer support runs on Screendesk.

Start for free