Which version should you use?

If the identifier becomes a primary key, time-ordered variants are usually better: they cluster inserts at the end of the index instead of scattering them across pages. If the identifier is a public token, v4's larger random space is preferable.

TypeSortableRandom bitsBest for
UUID v4No122General-purpose IDs where order does not matter
UUID v7Yes (time)74Database keys, event IDs, log correlation
ULIDYes (time)80Sortable IDs with a compact 26-character form
UUID v1Yes (time + node)—Legacy systems; leaks MAC address in some implementations

How generation works in the browser

v4 uses crypto.getRandomValues to fill 122 random bits and sets the version and variant nibbles. v7 combines a 48-bit millisecond timestamp with 74 random bits, and sets the same version/variant markers. ULID encodes a 48-bit timestamp and 80 random bits in Crockford's base32.

None of these call a server. The identifier exists only in your browser until you copy it, which matters when the ID is a secret or a capability token.

Browser randomness is not a substitute for cryptographic key generation. For secrets, encryption keys or session tokens, use the platform's cryptography API.

Collision math

v4 has 122 random bits: roughly 5.3 × 10^36 possible values. You would need about 2.6 × 10^18 IDs before a 50% collision chance (birthday bound), far beyond any practical table. v7 trades random bits for time order, but its 74 random bits inside the same millisecond still give about 1.9 × 10^22 combinations.