Dev Tools

ID Tools Tools

Generate UUID v4/v7, NanoID, and ULID, and validate UUID layout.

4 tools · 100% browser-based · No uploads · No signup

About these ID Tools tools

ID tools generate UUID v4 and v7, validate UUID layout and version, and mint NanoID and ULID values. Use them when you need unique keys in fixtures, docs, or a prototype. Do not use a website generator as the only source of IDs in a high-security lottery or crypto protocol; use your language's CSPRNG APIs in production code.

UUID v4 is random. UUID v7 is time-ordered, which is kinder to B-tree indexes. NanoID is shorter and URL-safe. ULID is sortable and encodes a timestamp.

Tools in this category

How these tools run in your browser

Generation uses crypto.getRandomValues in the browser. Validators check canonical hex form, variant bits, and version nibble. Bulk generate loops in JS; thousands are fine, millions may hitch the UI.

Common Use Cases

  • Fill a test database with unique primary keys
  • Check whether a value is a UUID and which version
  • Generate compact public IDs for a demo API
  • Show how ULID sorts compared to UUID v4

Common Mistakes

UUID v1 leaks MAC-ish time info; we focus on v4 and v7.
NanoID collision risk depends on length and alphabet. Do not shorten blindly.
UUIDs in URLs should be treated as secret if they are capability links.
Copy-paste can introduce curly quotes or hidden whitespace that fail validation.

Frequently Asked Questions

v4 or v7 for a new Postgres table?

v7 (or ULID) if you care about index locality. v4 if you already standardized on random UUIDs. This is a database design choice, not a moral one.

Are these RFC 9562 UUIDs?

v4 and v7 follow the current UUID spec layout. We are not a conformance test suite for every version.

Can I use these IDs as passwords?

They are unique identifiers, not memorable secrets, and a web page is the wrong place to mint production credentials. Use your app's password hasher and a proper secret generator in code.