Visual RFC.
ALL RFCs / RFC 9562
Read the RFC ↗
RFC 9562 / MECHANISM GUIDE

Random UUID version 4

02

UUIDv4 fills the available layout with random data around fixed version and variant bits.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 5.4 ↗
RFC 9562 · § 5.4EXAMPLE
3 / 3
Random UUID version 4UUIDv4 fills the available layout with random data around fixed version and variant bits.Random UUID version 4random inputfresh random bitsversion / variant4 / standardremaining random bits122Probabilistic uniqueness is not authentication
03
Issue the identifier

Keep the identifier distinct from an authentication secret.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

The version and variant leave 122 random bits.

  • The version and variant leave 122 random bits.
  • Use a suitable random source; CSPRNG guidance appears in §6.9.
  • Collisions remain probabilistic rather than mathematically impossible.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. UUID fields and text
  2. Random UUID version 4
  3. Time-ordered UUID version 7
  4. Name-based and custom layouts
  5. Generation and privacy limits
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗