๐Ÿ”‘ Unique ID Generator

NanoID / ULID / UUID v4 / Custom Format ยท Client-Side Generation

โš™๏ธ Configuration
NanoID: 21 chars default, URL-safe, high entropy. Widely used in modern web apps.
Click "Generate IDs" to start
Generated: 0

โ“ FAQs

What is NanoID?โ–ผ

NanoID is a compact, URL-safe unique identifier format with a default length of 21 characters. Compared to UUID, NanoID is shorter (21 vs 36 chars), faster, and supports custom alphabets. It uses cryptographically secure random number generation for high entropy. It's widely used in modern web applications, database primary keys, short links, and more.

What's the difference between ULID and UUID?โ–ผ

ULID (Universally Unique Lexicographically Sortable Identifier) is a sortable unique identifier. The first 10 characters encode a millisecond-precision timestamp, and the last 16 are random. This makes ULIDs sortable by generation time, ideal for database indexes. UUID v4 is purely random and not sortable. ULID is also shorter (26 vs 36 chars) and uses Crockford Base32 encoding for readability.

Is this tool secure? Are my IDs sent to a server?โ–ผ

Absolutely. All ID generation happens entirely in your browser using the Web Crypto API (getRandomValues). No data is ever uploaded to any server. The tool works offline too. You can safely use generated IDs in sensitive production environments.

How do I choose the right ID format?โ–ผ

Quick guide:
โ€ข NanoID: Best for short IDs (URLs, API keys, short links). Default 21 chars is plenty secure.
โ€ข ULID: Best for database primary keys, time-sortable data, log IDs.
โ€ข UUID v4: Best for standardized unique identification, API design, cross-system data exchange.
โ€ข Custom: Best for specific format requirements (prefix/suffix, specific characters/length).

What's the collision probability?โ–ผ

For NanoID (21 chars, 64-symbol alphabet): you'd need to generate 1 billion IDs per day for roughly 180 million years to have a 50% chance of a single collision. ULID uses 128 bits of randomness with similarly negligible collision probability. For extra safety, always use unique constraints on database columns.

๐Ÿ’ก All processing is done locally in your browser. No data is uploaded. Works offline.