UUID v4: when to use it, when to avoid it, and alternatives

Complete guide: real use cases, DB impact, alternatives (UUIDv7/createdAt), pitfalls, and FAQ.

Updated: 2026-03-22

On this guide

How to use this guide well

These guides are more useful when you read them as operational help, not as filler documentation.

Start from the section that matches the failure

Do not read linearly if you do not need to. Jump to the section that looks closest to the incident, payload, or config you are debugging.

Copy only after you understand the constraint

The useful part is usually in the caveat, not in the snippet itself: timezone, dialect, schema, audience, type inference, or portability.

Then validate with the tool

Once the reasoning is clear, use the related tool to inspect the real value, payload, or expression instead of working from memory.

A quick scan before you dive in.

Sections

Code examples

A short workflow tuned to the type of issue this guide covers.

Capture the real input

Work with the exact payload, config, or identifier that is failing instead of rebuilding it from memory.

Read the constraint before copying

Use the examples to understand the failure mode first, then adapt them to your own environment and stack.

Validate with a related tool

Once the reasoning is clear, inspect the live value with the matching tool and share a sanitized example if you need help.

UUID v4 gives unique ids without central coordination. Great for fixtures, correlation ids, and client-side temporary ids.

Time ordering, DB index fragmentation, human-friendly identifiers.

UUIDv7, created_at + UUIDv4, or auto-increment ids depending on your constraints.

Is it safe as primary key? Often yes, but measure. Use created_at for ordering.

Use the matching tool when you want to validate or reproduce the issue described in this guide.

Validate and format JSON with clear errors and quick copy.

Generate UUID v4 values and copy them to clipboard.

Transform timestamps ↔ dates in seconds or milliseconds.

Move between deep guides and shorter task-focused articles so the site works like a connected knowledge base, not a dead end.

Practical guide: edge cases, realistic formats, consistency, sizes, and a QA/frontend checklist.

Practical guide: digit rule, real examples, timezone, pitfalls, and tips to avoid expensive bugs.