UUID Versions Explained
What are the different UUID versions and how to use them?
There are 5 UUID version plus one common unofficial version. We will explain each of these versions as well as their purpose and when to use them. For more details, see the official UUID RFC 4122.
Version-1 is based on the current time and the MAC address for the computer or "node" generating the UUID.
RFC 4122 states timestamp is number of nanoseconds since October 15, 1582 at midnight UTC. Most computers do not have a clock that ticks fast enough to measure time in nanoseconds. Instead, a random number is often used to fill in timestamp digits beyond the computer's measurement accuracy. When multiple version-1 UUIDs are generated in a single API call the random portion may be incremented rather than regenerated for each UUID. This ensures uniqueness and is faster to generate.
The last 12 hex digits of a UUID string represent the MAC address of the node. In some implementations (including the UUID generator on this site) a random MAC address is used instead of the node's actual MAC.
MAC Address and creation time can be extracted using our UUID decode tool. MAC Addresses are unique to the computer generating them. By including a MAC address in the UUID you can be sure that two different computers will never generate the same UUID. Because MAC addresses are globally unique, version-1 UUIDs can be traced back to the computer that generated them.
Version-2 UUIDs are not used very widely because of several problems with the format. These UUIDs can be useful because they contain data about when, where, and by whom the UUIDs were generated. This use a useful attribute in some systems. However, it doesn't make sense form an online generation tool like uuidtools.com.
V2 UUIDs include the MAC address of the generator, lossy timestamp, and an account ID such as user ID or group ID on the local computer. Because of the information included in the UUID, there is limited space for randomness. The clock section of the UUID only advances every 429.47 seconds (~7 minutes). During any 7 minute period, there are only 64 available different UUIDs!
UUID Version-3 vs UUID Version-5
Version-3 and version-5 are generated based on a "namespace" and unique "name". Namespace and name are concatenated and hashed. There is no temporal or random component to either versions so the same input produces the same output every time.
- namespace — a UUID
- name — can be anything
What is the difference between version-3 and version-5?
- Version-3 UUIDs are based on an MD5 hash of the name and namespace.
- Version-5 UUIDs are based on a SHA-1 hash of the name and namespace.
A SHA-1 hash is too long to be used in a UUID so it is truncated.
The UUID specification establishes 4 pre-defined namespaces. The pre-defined namespaces are:
- DNS —
- URL —
- OID —
- X.500 DN —
When a pre-defined namespace identifier is used we convert that identifier to a UUID internally.
Version-4 UUIDs are randomly generated. There are over 5.3 x 1036 unique v4 UUIDs. This is the most common UUID version.
Version-4, variant-1 UUIDs are used in the game Minecraft. You can use our tool to generate Minecraft UUIDs than can be used in-game.
Version-4, variant-2 is called a "GUID" on Microsoft systems. GUIDs are a Microsoft implementation of DCE UUIDs. GUIDs mostly conform to RFC4122. The only difference is in the byte order.
Timestamp-first are not mentioned in the UUID RFC; however, they are a common variation of version-4 UUIDs. This format is sometimes called "Ordered UUIDs" or "COMB" (combined time-GUID).
This version starts with the current time followed by randomness. There are two main reason for beginning UUIDs with the current timestamp:
- When sorting by UUID they will appear in the order created
- Ordered UUIDs can be more efficiently stored in indexed databases columns compared to random UUIDs
There are several variations of timestamp-first UUIDs in different implementations because there is not agreed upon specification. However, generally the first 8 hex digits represent the time and the remaining digits are random.
If you are using UUIDs as a primary key in a database you should use timestamp-first UUIDs.
This special case UUID is guaranteed to not be unique. The Nil UUID is all zeros: 00000000-0000-0000-0000-000000000000
This UUID might be used as a template for the format of UUIDs or when you need an easily identified UUID that is guaranteed to not be unique.
To determine the version of a UUID and to extract any information such as creation time (when available) use our UUID decode tool.