What is a UUID?
A UUID (Universally Unique Identifier) is a 128-bit number represented as 32 hexadecimal digits grouped as 8-4-4-4-12 with hyphens. The format is standardized in RFC 4122 and used wherever systems need identifiers without a central allocation authority.
Unlike auto-increment integers, UUIDs can be generated independently on any machine without coordination. That makes them ideal for microservices, offline-first mobile apps, and client-side record creation.
UUID v4 Random Identifiers
Version 4 UUIDs set the version nibble to 4 and the variant bits to the RFC pattern, filling the remaining bits with random data. Roughly 5.3 × 10³⁶ possible v4 UUIDs exist — collision risk in any practical deployment is negligible.
Vertex Solutions generates v4 UUIDs using the browser's cryptographic random number generator when available, falling back to a compliant random template only in legacy environments.
Generating IDs for Development
Database seeds — Populate test tables with realistic primary keys without conflicting with production sequences.
API mocking — Return plausible id fields in stub responses during frontend development.
Correlation IDs — Assign a unique trace identifier to each request in distributed logging.
File naming — Create collision-resistant filenames for uploads and temporary artifacts.
Generate multiple UUIDs when bulk-inserting fixtures or stress-testing uniqueness constraints.
UUID vs Sequential IDs
| Approach | Pros | Cons | |----------|------|------| | UUID v4 | No coordination, opaque, merge-friendly | Larger storage, random insert patterns in B-trees | | Auto-increment | Compact, sequential, human-friendly | Requires central authority, exposes row counts |
Choose UUIDs when clients create records before syncing to a server, or when merging data from multiple sources. Choose integers when storage efficiency and sequential locality matter most.
Format Variants You May Encounter
Most APIs expect the canonical hyphenated lowercase form: 550e8400-e29b-41d4-a716-446655440000.
Some systems strip hyphens for compact storage (550e8400e29b41d4a716446655440000). PostgreSQL accepts both when casting to the uuid type. MongoDB ObjectIds are a different format entirely — do not confuse them with UUIDs.
Braced notation {550e8400-e29b-41d4-a716-446655440000} appears in Windows registry exports and COM identifiers. Remove braces before pasting into web APIs.
Worked Example: Anatomy of a Generated UUID v4
f47ac10b-58cc-4372-a567-0e02b2c3d479
|______| |__| |__| |__| |__________|
8 hex 4 4 4 12 hex chars (36 chars total with 4 hyphens)
^ ^
| +-- Variant nibble (8, 9, a, or b in RFC 4122)
+------- Version nibble (always 4 for UUID v4)
Practical Tips
- Batch testing — Generate 10–20 UUIDs at once when writing integration tests that need unique foreign keys, then format your fixture objects in the JSON Formatter.
- Logging — Prefix log lines with a freshly generated UUID per user session to correlate client-side errors across distributed services.
- Never use UUIDs as passwords — UUIDs are public identifiers; generate actual credentials in the Password Generator.