Does a UUID show when it was made?
A UUID looks like noise, and some are. Others carry the time they were made in their first few characters, readable by anyone who has the ID, which matters when the ID is in a web address or an export.
Written · Updated
It depends on the version, which is the first digit of the third group. Version 1 and 6 carry the time in 100-nanosecond steps since 15 October 1582, and version 1 traditionally carried the computer’s network address as well. Version 7 carries the Unix time in milliseconds in its first 12 hex digits, and so does a ULID. Version 4 is random and carries no time at all. Anybody with a v1, v6 or v7 UUID can read when it was made.
Which version you have
The version is the first character of the third group: in 01a1b031-8e3b-790f-a2ce-753e25d4939e it is 7. A ULID is a different shape, 26 characters of letters and digits with no hyphens, such as 01M6R333HVFFE6HM3S8DXD1MWQ.
Four made by IDENT, and what it reads back from each:
| ID | Kind | Time inside |
|---|---|---|
01a1b031-8e3b-790f-a2ce-753e25d4939e | UUID v7 | 6 November 2026, 09:30:00.123 UTC |
01M6R333HVFFE6HM3S8DXD1MWQ | ULID | 6 November 2026, 09:30:00.123 UTC |
c232ab00-9414-11ec-b3c8-9e6bdeced846 | UUID v1, the example in RFC 9562 | 22 February 2022, 19:22:22 UTC |
28e89caf-59b7-4a46-9137-a9a924eac298 | UUID v4 | None: 122 random bits |
Reading the time by hand
For a version 7 UUID, take the first 12 hex digits without the hyphen, 01a1b0318e3b, and read them as one hexadecimal number: 1,793,957,400,123. That is the number of milliseconds since 1 January 1970, UTC, which is 6 November 2026 at 09:30:00.123. In a browser console, new Date(parseInt("01a1b0318e3b", 16)) does the arithmetic.
A ULID holds the same 48 bits in its first ten characters, in Crockford’s base32. A version 1 UUID splits its 60-bit time into three pieces and stores them out of order, low part first, which is why version 6 was added: the same time, in an order that sorts.
Why it matters
- An ID in a web address dates the record. A customer number, an order number or a document link made with v7 tells anybody who sees it when the account was opened or the document created, to the millisecond.
- Two IDs give an interval. Anybody who sees several can tell which came first and how far apart they were made, and so how fast a service is growing or when a batch was run.
- Version 1 may name the machine. Its last twelve hex digits are the node field, which older generators filled with the network card’s MAC address. RFC 9562 now says to use a random value instead, and many libraries do, but an old v1 ID can still identify the computer that made it.
None of that is a flaw in v7. Time ordering is the reason for it: new rows go to the end of a database index instead of landing at random, which keeps inserts fast. It only becomes a disclosure when the ID leaves the database.
Which to use
- An ID that stays inside the system, a primary key nobody outside sees: v7, or a ULID, for the ordering.
- An ID that is shown or shared, in a link, an export or a support ticket, where the moment of creation should stay private: v4.
- Both: a v7 key inside, and a separate v4 for the outside world.
To check what an ID you already have gives away, paste it into IDENT: it names the version and the variant, and shows the time in UTC when there is one.
Questions people ask about the time inside a UUID
Can you get the creation time from a UUID?
From versions 1, 6 and 7, yes, and from a ULID. Version 7’s first 12 hex digits are the Unix time in milliseconds. A version 4 UUID is random and holds no time.
How do I tell which version a UUID is?
Look at the first character of the third group: in xxxxxxxx-xxxx-7xxx-xxxx-xxxxxxxxxxxx it is 7. A 4 there means random, 1 and 6 mean time-based, 7 means Unix time.
Is it safe to put a UUID v7 in a URL?
It is safe in the sense that it cannot be guessed, but it tells anyone who sees it when the record was created, to the millisecond. Use v4 for an ID that is shown outside the system if that moment should stay private.
Does a UUID contain my MAC address?
Only a version 1 UUID can, in its last twelve hex digits, and only if the library that made it used the network card’s address. Current libraries usually use a random value instead, as RFC 9562 recommends. Versions 4 and 7 never contain one.
Does a ULID show when it was made?
Yes. Its first ten characters are the creation time in milliseconds since 1970, in Crockford’s base32. The other sixteen are random.
Related tools
- Why a bar chart has to start at zeroA bar says “this much” by its length, so a cut axis draws a different number.
- When the mean is the wrong averageThe mean is a balance point, so one large value drags it. Four ways to tell when it is misleading, and the one property only the mean has.
- Benford’s law, and when it tells you nothingThe most misapplied result in auditing. Which columns the leading-digit test holds for, the five kinds it never will, the tests that need no assumption at all, and the threshold test that catches real splitting.
- Why a random sample needs a seed“Randomly” is unfalsifiable in both directions. A seed turns the draw into something anybody can reproduce and check.
- What “days between” actually meansMonday to Wednesday is two days or three, and clear days makes it one. Plus why adding a month to the 31st has two defensible answers.
What your files give away
A one-page checklist of what a photo, a document or a PDF says about you, free now. Then one letter a month, with one new tip.