UUID Generator — v4, v7, nanoid, ULID (Bulk 1-100)
Generate UUIDs in 4 formats: v4 random (legacy), v7 time-ordered (new, DB-friendly), nanoid (URL-safe, short), ULID (Crockford Base32). Bulk 1-100.
Why use this tool
Unlike v4 (random), v7 sorts by timestamp → great for DB primary keys (index locality).
v4 uses the browser Web Crypto API — cryptographically secure.
Slider for count. Copy all in one click, or copy each individually.
How to use
- 1Pick version: v4 / v7 / nanoid / ULID.
- 2Set count slider 1-100.
- 3Click Generate. Copy each UUID or Copy all.
UUID variants
UUID v4 (random): 122-bit random, 8-4-4-4-12 hex. Most common but NOT time-sortable — causes DB index fragmentation.
UUID v7 (RFC draft 2024): 48-bit Unix ms timestamp + 74-bit random. Lexicographically sortable by time → better DB primary key (INSERT perf, range scans).
nanoid: 21 chars URL-safe (A-Za-z0-9_-). Shorter than UUID, still 126-bit entropy. Popular in the Node ecosystem.
ULID: 26 chars Crockford Base32. Time-ordered, case-insensitive, no special chars.
- ✓UUID v4 native crypto.randomUUID
- ✓UUID v7 inline implementation
- ✓nanoid custom length 6-64
- ✓ULID 26-char time-ordered
- ✓Bulk generate 1-100
- ✓Format options: uppercase, no-dashes
- ✓Copy all + per-item
FAQ
v4 vs v7 — which to use?
v4 for disjoint IDs that don't need sorting (user_id, request_id). v7 for DB primary keys needing index locality (better INSERT perf, range scan).
Is nanoid standardized?
Not an RFC standard, but widely used (Node, Stripe, GitLab). 21-char default = 126-bit entropy, close to v4 (122-bit).
How is ULID different from UUID v7?
Same concept (time-ordered). ULID uses Base32 (26 chars) vs hex 8-4-4-4-12 (36 chars). Mostly cosmetic.