Skip to content
Sealpaste

Delete all recent work?

This removes the 0 items saved in this browser. Your settings stay.

Stop saving recent work?

New work won't be saved in this browser. The 0 items already saved can stay or go.

UUID Generator

IDs
Ready
Runs in your browser. Nothing you paste is uploaded unless you share it.

Inspect an ID

Generate UUIDs (GUIDs): v4, v7, v1, v6, v8, name-based v3/v5 or nil, up to 1,000 at once, as text or a JSON array

Generate UUIDs (v4 random or v7 time-ordered) in bulk, and paste any UUID or ULID to see its version and creation time.

How to use it

  1. Pick UUID v4, UUID v7, ULID or another version under Other (v1, v6, v8, nil, max, or name-based v3 and v5 from a namespace and a name), and how many you need. Choose hyphens and capitals, wrap each in braces {…}, urn:uuid: or quotes, and copy them one per line, comma-separated or as a JSON array.
  2. Click Generate, then copy one or all.
  3. To inspect an ID, paste it into "Inspect an ID": it names the version and, for time-based IDs, when it was made.

Example

UUID v4 vs v7

Input
Generate one of each
Result
v4: 3f0c8a52-9d1e-4b7a-a6c2-5e1f0d9b2c47
v7: 0192f4a1-7c3e-7d2a-9b41-6c8e2f0a1d35

The v7 starts with a timestamp, so new IDs sort after old ones.

v4, v7 or ULID?

TypeHow it’s builtGood for
UUID v4122 random bitsDefault choice; nothing leaks about when or where it was made
UUID v748-bit Unix milliseconds + random bits (RFC 9562)Database primary keys: inserts stay in index order
ULID48-bit milliseconds + 80 random bits, Crockford Base32Short, URL-friendly, sortable ids

Sources: RFC 9562

Questions

Are these IDs secure and unique?
They use your browser’s cryptographic random generator (crypto.getRandomValues). A v4 UUID has 122 random bits, a ULID 80 and a v7 UUID 74 for every millisecond, so a collision is not a practical concern. The IDs are made on your device and aren’t sent anywhere.
Is a GUID the same as a UUID?
Yes. GUID is Microsoft’s name for a UUID, and .NET’s Guid.NewGuid() makes a v4. For the registry form {…}, set Wrap each to braces; Inspect an ID reads it with or without them.
Why use UUID v7 for database keys?
Random v4 keys land all over a B-tree index, causing page splits and poor cache use in PostgreSQL, MySQL and others. v7 keys increase over time, so new rows append at the end like an auto-increment id.
Can I get the creation time from a UUID?
From v1, v6 and v7 UUIDs and from ULIDs, yes: paste one into "Inspect an ID". A v4 UUID contains no time.
What are name-based UUIDs (v3 and v5)?
A v3 or v5 UUID is a hash of a namespace UUID and a name: MD5 for v3, SHA-1 for v5. The same namespace and name give the same UUID on every system, so you can derive a stable ID from a domain, URL or key instead of storing one. Prefer v5; with the DNS namespace, www.example.com gives 2ed6657d-e927-568b-95e1-2665a8aea6a2, the example in RFC 9562.
When would I use v1, v6, v8, nil or max?
v1 and v6 hold a 60-bit timestamp; v6 reorders it so IDs sort by time, for systems that cannot take v7. The node here is random, not your network card. v8 is the free-form version: here 122 random bits labeled 8, for tests that need one. Nil (all zeros) and max (all F) are the special values RFC 9562 defines for "no ID" and sentinels.

Related tools