🔗 UUID and NanoID Generator

UUID v1, v4, v6, v7 and NanoIDs, generated in your browser. Bulk supported.

Last updated: November 8, 2026 · By the BoltQuickTools team

Generate IDs when the exact format matters

Sometimes an ID has to fit something that already exists: a legacy table expecting UUID v1, a short numeric code, or a C# snippet wanting braces. This page offers more format control than a plain UUID generator, including NanoID length and alphabet.

Controls

  1. Choose an ID Type: UUID v4, v7, v1, v6 or NanoID.
  2. Set Count and a Format: Plain, UPPERCASE, {braces} or "quoted".
  3. For NanoID, two more fields appear: NanoID Length and NanoID Alphabet.
  4. Press Generate. With a Count of 1 the ID appears on its own and clicking it copies it. With more, you get a list. Copy All copies whichever is showing.

Changing the ID Type does not make a new ID until you press Generate.

Examples from the page's functions

Output is random or time-based, so yours will differ. The v1 and v6 samples below were generated in the same run and share a timestamp, which shows how they relate:

v1  d400cea0-dbf1-11f1-a31b-a9f7d46d948f
v6  1f1dbf1d-400c-6ea0-8c41-1a7354456baa
v4  c064c995-f407-481b-b84f-1af0c71cf66c
v7  01a1be75-288a-7d1f-a170-755a4e11bb82

A v1 ID stores the low time bits first, which is why two v1 IDs do not sort by age. Drop the version digit from 11f1, rejoin the v1 groups as 1f1, dbf1, d400cea0, and you get 1f1dbf1d400cea0, the same value that v6 writes in order: 1f1dbf1d-400c-6ea0, with the version digit 6 placed before the final ea0.

With the Format set, the same kind of output looks like this: {braces} gives {edc5edf2-6cc6-4b1b-99b6-9aa8eb33167b}, and a NanoID of length 12 with the Numbers only alphabet and "quoted" gives "773591759407".

What the generator actually does

Choosing between the options

Which UUID version suits new work?

Use v7 for database keys, because it sorts by creation time, or v4 when an ID should reveal nothing about its origin. Pick v1 or v6 mainly to match an existing system. The article on UUID v7 for new databases explains the indexing reasons.

How short can a NanoID safely be?

That depends on how many you will create. Each character from the default alphabet adds 6 bits, so 21 characters gives 126 bits, and 8 characters gives only 48. Short IDs are reasonable for a small set, but check for clashes against existing IDs on insert.

How does this differ from the site's other UUID page?

The UUID generator also makes ULIDs and supports batches up to 10,000, but offers no format or alphabet options. For tokens that must be unguessable, the password generator is a better fit than either.