{{ formattedUUID }}
Universally Unique Identifiers (UUIDs) are 128-bit numbers encoded as 36-character strings that allow systems to tag data, sessions, or components without coordination. Because the format is statistically collision-free across space and time, UUIDs simplify database keys, distributed logs, and message queues. They appear in hexadecimal blocks separated by hyphens and braces.
This generator lets you pick one of the four RFC 4122 algorithms—time-based, name-based with MD5, random, or name-based with SHA-1—then instantly creates a fresh identifier in a reactive engine. Optional switches let you strip dashes, change case, wrap the code in braces, or convert well-known namespace aliases into canonical form.
A software build pipeline might request hundreds of UUIDs to label artefacts produced by parallel jobs; using this tool avoids network calls and preserves an auditable trail through the built-in history export. Although collisions are astronomically unlikely, always confirm the selected version satisfies your project’s randomness, timestamp, or namespace compliance requirements.
RFC 4122 defines a UUID as a 128-bit value comprising 32 hexadecimal digits grouped into five fields: time-low, time-mid, time-high-and-version, clock-seq-and-variant, and node. Each version fills those fields differently: Version 1 embeds a timestamp and node address; Versions 3 and 5 hash an arbitrary name within a namespace using MD5 or SHA-1; Version 4 sets only variant and version bits then fills the remainder with cryptographically strong pseudo-random numbers offering ample entropy.
Version | Basis | Typical Use |
---|---|---|
1 | Timestamp + Node | Ordered logs, legacy systems |
3 | MD5 Name Hash | Stable keys within a namespace |
4 | Random | General-purpose identifiers |
5 | SHA-1 Name Hash | Stable keys where MD5 is barred |
Choose a version that aligns with ordering, determinism, or cryptographic policy; formatting options never affect the underlying 128-bit value.
Version 4 example:
Primary reference: RFC 4122; further analysis in Leach et al., “A Universally Unique IDentifier URN Namespace,” 2005.
No personally identifiable information is processed; generation occurs entirely client-side and complies with GDPR data-minimisation principles.
Follow these steps to craft and export a custom identifier.
A UUID is a 128-bit identifier designed to be unique across time and space without central coordination.
Use Version 4 for general randomness, Version 1 for sortable IDs, and Versions 3/5 when the same inputs must always yield the same result.
No. All computations and history exports occur locally; nothing leaves your browser.
The probability is vanishingly small for well-seeded random or timestamp sources, but it is never mathematically zero.
Select “Remove dashes” in the advanced panel; the underlying value remains unchanged.