Question 1

v4 vs v7: when to use which?

Accepted Answer

Use v4 when you need pure randomness and the insertion order of records does not matter — for example, user IDs, API tokens, or session tokens. Use v7 when you are inserting into a B-tree database index (PostgreSQL, MySQL, SQLite) and you want new rows to land at the end of the index rather than in random positions. Random v4 UUIDs cause index fragmentation: every insert has to split a random page, leading to write amplification and slower range scans. v7 UUIDs embed a millisecond-precision Unix timestamp in the first 48 bits, so they sort chronologically and append to the index sequentially — just like auto-increment integers, but globally unique without a central counter.

Question 2

Why is v1 discouraged now?

Accepted Answer

UUID v1 encodes the host MAC address and a 100-nanosecond timestamp. The MAC address exposure is a privacy and security concern — it can identify the physical machine that generated the UUID, which has been exploited in practice (the original Melissa worm author was traced via a v1 UUID). Additionally, the timestamp resolution is so fine that two UUIDs generated within the same 100ns window on the same machine can collide. The IETF published RFC 9562 in 2024 officially deprecating v1 and v2, recommending v4 for randomness and v7 for time-ordered use cases.

Question 3

Will UUID collide as a database primary key?

Accepted Answer

The probability is negligible in practice. A UUID v4 has 122 bits of randomness (the remaining 6 bits encode version and variant). The birthday paradox tells us you need to generate about 2^61 ≈ 2.3 × 10^18 UUIDs before the collision probability reaches 50%. At 1 billion inserts per second, that would take over 73 years. For UUID v7 the random portion is 62 bits per millisecond window; within a single millisecond you'd need to generate 2^31 ≈ 2.1 billion UUIDs before a collision becomes likely. No real application comes close to these rates. Use a UNIQUE constraint for safety, but collisions are not a practical concern.

Question 4

Can I extract the timestamp back out of a v7 UUID?

Accepted Answer

Yes. The first 48 bits of a v7 UUID are a big-endian millisecond Unix timestamp. Take the first 12 hex characters of the UUID (drop the hyphens), parse them as a hexadecimal integer, and you get the milliseconds since 1970-01-01 UTC. For example, the UUID 0190b8e5-7c00-7000-8000-000000000000 starts with 0190b8e57c00, which is 1719331000320 ms, roughly 2024-06-25. This makes v7 useful for rough debugging: you can tell when a record was created without a separate created_at column. Note this is approximate: the timestamp is the generation moment, not necessarily the database commit time, and v4 carries no timestamp at all (those 48 bits are random).

Question 5

Should I strip the hyphens before storing UUIDs?

Accepted Answer

It depends on your column type. If you store UUIDs in a native uuid column (PostgreSQL) the hyphens are display-only and stripping them is irrelevant: the value is 16 bytes on disk either way. If you store them as text/varchar, the canonical 36-character form with hyphens costs 36 bytes versus 32 without, and a true BINARY(16) column costs just 16. For high-volume tables, store the raw 16 bytes and format on read. The strip-hyphens toggle here is mainly for compact URLs, filenames, and cache keys where the four dashes add noise, for example turning a 36-char string into a cleaner 32-char slug.

UUID Generator

What this tool does

Tool details

How to use

1. Input

2. Process

3. Copy / Download

How UUID Generator fits into your work

Generation jobs

Generation checks

Good next steps

Real-world use cases

Generating v7 keys to migrate off auto-increment IDs

Building 500 fixture IDs without a uuidgen loop

Common pitfalls

Privacy

FAQ

Tool combos

UUID Generator

What this tool does

Tool details

How to use

1. Input

2. Process

3. Copy / Download

How UUID Generator fits into your work

Generation jobs

Generation checks

Good next steps

Real-world use cases

Generating v7 keys to migrate off auto-increment IDs

Building 500 fixture IDs without a uuidgen loop

Common pitfalls

Privacy

FAQ

Password Generator

NanoID Generator

Mock Data Generator

QR Code Generator

CSS Grid Generator

.htaccess Generator

Markdown TOC Generator

Meta Tag Generator

robots.txt Generator

24-Point Solver & Game

Chinese Acupoint Locator

API Key Generator