Taprico
Developer Studio v4 / v7 / ULID 100% Client-Side

UUID Generator (v4, v7), ULID & Timestamp Inspector

Generate cryptographically random UUID v4, database-friendly sortable UUID v7 (RFC 9562), and ULIDs in bulk—or inspect embedded timestamps.

10 V7 identifiers · CSPRNG

Modern RFC 9562 UUID v7

Time-ordered 48-bit Unix millisecond prefix dramatically reduces PostgreSQL B-tree index fragmentation compared to v4.

Bulk Export (Up to 500 IDs)

Generate batches and export immediately as plain text, JSON array, CSV, or SQL VALUES lists.

Built-In UUID Inspector

Paste any UUID to inspect its RFC version, variant bits, and decoded creation timestamp (for v1 and v7).

How to Use UUID & ULID Studio

  1. 1 Select your identifier type: UUID v4 (random), UUID v7 (time-ordered), ULID (Crockford Base32 sortable), or Nil UUID.
  2. 2 Set your batch quantity (1 to 500) and toggle Uppercase, Hyphens, Braces {...}, or URN prefixes.
  3. 3 Click Regenerate or copy the list as plain lines, a JSON array, or an SQL VALUES snippet.
  4. 4 Switch to the UUID Inspector tab anytime to decode the version and embedded timestamp of an existing UUID.

Why US Backend Teams Are Migrating Primary Keys from UUID v4 to UUID v7

UUID v4 relies on 122 purely random bits. While collision resistance is astronomical, inserting completely random primary keys into clustered database B-trees (such as PostgreSQL, MySQL InnoDB, or SQL Server) scatters page writes across disk and bloats indexes at scale.

Ratified in RFC 9562, UUID v7 embeds a 48-bit Unix timestamp in milliseconds at the start of the 128-bit value, followed by 74 cryptographically random bits. You get global uniqueness without sacrificing sequential database write locality.

Frequently Asked Questions

Are these UUIDs cryptographically secure? +

Yes. Taprico uses window.crypto.randomUUID() and window.crypto.getRandomValues() backed by your operating system CSPRNG rather than insecure Math.random().

Can I extract a creation date from a UUID v4? +

No. UUID v4 contains only random bits plus version/variant metadata. Only time-based versions like UUID v7, UUID v1, and ULID embed creation timestamps.

When should I pick ULID over UUID v7? +

Pick ULID when identifiers appear prominently in URLs or API responses (26 alphanumeric characters vs. 36), and pick UUID v7 when your database offers a native 16-byte uuid column type like PostgreSQL.