Loading…
Generate unique identifiers (UUIDs) with various versions including v1, v4, and v7 for different use cases.
UUIDs (Universally Unique Identifiers) are 128-bit values used to uniquely identify information in computer systems. They are designed to be unique across both space and time.
A UUID (Universally Unique Identifier), also called a GUID, is a 128-bit value written as 36 characters in the familiar 8-4-4-4-12 hexadecimal pattern, for example 550e8400-e29b-41d4-a716-446655440000. UUIDs let independent systems generate identifiers that are effectively guaranteed not to collide, without needing a central authority to hand out numbers. That makes them ideal for database primary keys, distributed systems, message IDs, file names, and API request tracing.
This generator produces valid UUIDs of several versions so you can pick the one that fits your use case. Version 4 is random and by far the most common — use it when you just need a unique ID with no ordering. Version 1 is time-based and derives partly from a timestamp and node value. Version 7 is a newer time-ordered format that embeds a Unix timestamp in its leading bits, so IDs sort chronologically, which improves database index locality compared with fully random v4 values.
The chance of two randomly generated v4 UUIDs colliding is astronomically small, so in practice you can treat them as unique. Everything is generated locally in your browser using cryptographically strong randomness where available, so the identifiers never touch a server and you can produce as many as you need instantly and offline.
Version 4 is fully random, so values are unordered. Version 7 embeds a Unix timestamp in its leading bits, so IDs generated later sort after earlier ones — better for database index performance while still being unique.
Not with mathematical certainty, but the probability of a collision for random v4 UUIDs is so small that they are treated as unique in practice, even across billions of values.
Use v4 for general-purpose random identifiers, v7 when you want time-ordered IDs that index efficiently, and v1 when you specifically need a timestamp-and-node based value.
No. Identifiers are created locally in your browser, so nothing is sent over the network and you can generate them offline.