RFC 9562 — The Modern UUID Standard Explained

RFC 9562 replaced RFC 4122 in May 2024, adding UUID v6 (reordered v1 for sortability), v7 (48-bit ms timestamp, the new default for database keys), and v8 (custom layout). v1 and v2 are deprecated. The Max UUID sentinel (ffffffff-ffff-ffff-ffff-ffffffffffff) was also formalised.

UUID v7 is native in PostgreSQL 18 (uuidv7()) and Python 3.13 (uuid.uuid7()).

Read more: RFC 9562 changes · All UUID versions · UUID v8 custom layout

UUID Validator · UUID Decoder

Frequently asked questions

Are there videos explaining what RFC 9562 changed in the UUID standard?

Yes. RFC 9562 overview videos cover the three new versions (v6, v7, v8), the Max UUID sentinel, and the deprecation of v1 and v2. The key takeaway is that UUID v7 is now the recommended default for time-ordered identifiers — replacing the privacy-leaking UUID v1. See RFC 9562 video walkthrough and RFC 9562 replaces RFC 4122.

What did RFC 9562 add to the UUID standard?

RFC 9562, published in May 2024, adds UUID v6 (reordered timestamp for sortability), v7 (Unix millisecond timestamp), and v8 (custom layout). It also defines the Max UUID sentinel (all-ones complement of the Nil UUID) and deprecates v1 and v2. The existing format and v3, v4, v5 semantics are unchanged.

Should I use v4 or v7?

Use v7 for database primary keys (time-sortable, index-friendly) and v4 for anything where creation order could leak information, like tokens or share links.