Table of Contents
Why ID Format Is a Real Decision
The Contenders at a Glance
UUID: The Standard
ULID: Sortable and URL-Friendly
NanoID: Compact and Customizable
KSUID: Big Randomness with a Timestamp
Snowflake: 64 Bits, Coordinated
Sortability and Database Indexes
How to Choose
Why ID Format Is a Real Decision
An ID looks like the smallest decision in a system, yet it touches everything: how fast your database index absorbs inserts, whether your API leaks record counts, whether URLs stay short, and whether JavaScript silently corrupts your keys. The five formats below all solve "give this thing a name" - and they make sharply different trade-offs doing it.
The Contenders at a Glance
UUID (v4/v7) ULID NanoID KSUID Snowflake
Total size 128 bits 128 bits ~126 bits 160 bits 64 bits
Text form 36 chars 26 chars 21 chars 27 chars up to 19 digits
Time-sortable v7 only yes no yes yes
Needs coordination no no no no yes (worker IDs)
Safe as JS number no no no no no - 64 bits overflows
Alphabet hexβ¦