{{ formattedUUID }}

  • {{ h.uuid }}

            

Introduction:

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.

Technical Details:

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.

Core Process:

  1. Read user-selected version and optional name / namespace values.
  2. If Version 1, capture timestamp & node address, inject version and variant bits, then format.
  3. If Version 4, gather 122 random bits, set version (0b0100) and variant (0b10) bits, then format.
  4. If Version 3 or 5, resolve namespace alias, hash namespace ∥ name, set version and variant bits, then format.
  5. Apply user formatting choices: uppercase, braces, and dash removal.
VersionBasisTypical Use
1Timestamp + NodeOrdered logs, legacy systems
3MD5 Name HashStable keys within a namespace
4RandomGeneral-purpose identifiers
5SHA-1 Name HashStable 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.

  • selectedVersion – algorithm choice (v1, v3, v4, v5).
  • nameInput – free-text string hashed for v3/v5.
  • namespaceInput – DNS/URL/OID/X500 alias or canonical UUID.
  • uppercase – converts output to capital letters.
  • removeDashes – presents a 32-character compact form.
  • includeBraces – wraps the UUID in “{ }”.

Version 4 example:

Random 128-bit value=8f2a4dbe-bf6c-11ee-b1d4-027d8655b555 Set version nibble4f2a4dbe-bf6c-41ee-b1d4-027d8655b555 Set variant bits4f2a4dbe-bf6c-41ee-b1d4-827d8655b555
  • UUID uniqueness is probabilistic, not absolute.
  • Clock skew can break ordering for Version 1.
  • Versions 3 and 5 inherit hash-function weaknesses.
  • Formatting changes never alter the binary value.
  • Empty nameInput with v3/v5 returns an error.
  • Non-UUID namespace strings are rejected.
  • Removing dashes breaks legacy parsers expecting 36 characters.
  • Uppercase + braces can inflate storage by two characters.

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.

Step-by-Step Guide:

Follow these steps to craft and export a custom identifier.

  1. Select a UUID Version that meets your requirements.
  2. (For v3/v5) Enter Name and Namespace.
  3. Toggle optional formatting—uppercase, dash removal, or braces.
  4. Press Generate to create the identifier.
  5. Copy the result or review the History tab to export JSON.

FAQ:

What is a UUID?

A UUID is a 128-bit identifier designed to be unique across time and space without central coordination.

Which version should I choose?

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.

Is my data stored?

No. All computations and history exports occur locally; nothing leaves your browser.

Can collisions occur?

The probability is vanishingly small for well-seeded random or timestamp sources, but it is never mathematically zero.

How do I remove dashes?

Select “Remove dashes” in the advanced panel; the underlying value remains unchanged.

Glossary:

Variant
Bit pattern indicating UUID layout.
Namespace
Reference domain inside which names are hashed.
Clock Sequence
Counter protecting Version 1 from timestamp repeats.
Hash
One-way function compressing arbitrary input into fixed length.
Entropy
Unpredictability source for Version 4 randomness.