UUID versions: randomness, time, and namespaces
生成 v1、v4 或 v5 格式的 RFC 4122 UUID,支援批量生成、大寫輸出和自訂連字符格式。
5720683c-9e98-4bbb-9aa6-42b658553ee2d7dbb188-d6bc-4630-b486-6e7346f54264dd99b3b4-7e37-4c3b-aa3b-3ab4cb3c4fea5137be00-7388-4113-a4b5-84495359322ca78861a6-7ace-444f-8c3d-573b89e28d9cUUID v4 範例
550e8400-e29b-41d4-a716-446655440000
格式:8-4-4-4-12 十六進位
如何使用本工具
- 選擇版本:一般推薦 v4(隨機)。
- 以滑桿設定數量(最多 50)。
- 依需求開啟大寫或移除連字號。
- 按下產生後可單筆或整批複製。
UUID versions: randomness, time, and namespaces
v4 is random (RFC 4122); v1 is time/MAC-derived (privacy concerns on some networks); v5 hashes a namespace + name. Choose v4 for opaque IDs unless you need sortable time proximity.
Database uniqueness still needs constraints—collision probability is tiny but not a substitute for transactional checks.
What each option produces
- Version 4 (default): 122 random bits from your browser’s cryptographically secure generator, plus the fixed version and variant bits. This is the right choice for almost every new identifier.
- Version 1: built from the current time as the count of 100-nanosecond intervals since 15 October 1582 (the start of the Gregorian calendar), a random clock sequence, and a random 48-bit node ID with the multicast bit set. Classic v1 used the computer’s network MAC address as the node; the random node keeps your hardware address out of the ID, as RFC 9562 recommends.
- Nil UUID: all zeros (00000000-0000-0000-0000-000000000000), used as an explicit “no value” marker.
- Formatting: generate up to 50 at once, switch to uppercase, or remove the hyphens to get a 32-character hex string.
Reading a UUID
A UUID is 128 bits written as 32 hexadecimal digits in five groups (8-4-4-4-12):
f47ac10b-58cc-4372-a567-0e02b2c3d479
^ ^
| variant: 8, 9, a or b = RFC 9562 layout
version: 4 = randomThe first digit of the third group is always the version, and the first digit of the fourth group shows the variant. That is why a v4 UUID always has a 4 in the 13th position, and why only 122 of the 128 bits are random. For a v1 UUID the first three groups hold the timestamp, so anyone can read off when it was created — something to keep in mind before exposing v1 IDs publicly.
Which version should you use?
- v4 for general identifiers: API resource IDs, file names, idempotency keys, correlation IDs in logs.
- v7 for new database primary keys: defined in RFC 9562 (2024), it starts with a Unix-millisecond timestamp, so values sort in creation order and index far better than random v4 keys in B-tree indexes. This tool does not generate v7 yet; most languages have a maintained library for it.
- v1 when an existing system expects it, for example some older Cassandra schemas (TimeUUID).
- v5 when the same input must always produce the same ID (it hashes a namespace and a name with SHA-1). Not offered here because it needs those inputs.
Will two UUIDs ever collide?
For v4, the 50% collision point arrives at about 2.7 × 10¹⁸ generated IDs — roughly 86 years of producing a billion UUIDs every second. In practice, a duplicate is far more likely to come from a bug, such as a copied ID or a badly seeded generator in another system, than from chance. Keep a unique constraint on the database column anyway; it costs nothing and catches the bugs.
Unpredictable is not the same as secret. RFC 9562 advises against assuming UUIDs are hard to guess, so do not use one as a password-reset or session token — use a dedicated random token instead.
Storing and comparing UUIDs
- Use a native type where one exists — uuid in PostgreSQL, uniqueidentifier in SQL Server — or BINARY(16) in MySQL. Storing the 36-character string takes more than twice the space and slows indexes.
- Compare case-insensitively: f47ac10b… and F47AC10B… are the same UUID. Microsoft tools traditionally show GUIDs in uppercase, often wrapped in braces {…}.
- Hyphen-free 32-character strings are common in URLs and file names. Most parsers accept both forms, but be consistent within one system.
Generating UUIDs in code
When you need IDs at runtime rather than a handful to paste, every mainstream platform has a built-in v4 generator:
JavaScript crypto.randomUUID() // browsers (HTTPS) and Node.js Python import uuid; uuid.uuid4() Java java.util.UUID.randomUUID() C# / .NET Guid.NewGuid() PostgreSQL SELECT gen_random_uuid(); -- built in since v13 Go uuid.New() // github.com/google/uuid Shell uuidgen # macOS prints uppercase
In their current implementations these use the operating system’s secure random source, like this page does. Avoid hand-rolled versions built on Math.random(), which older code snippets online still copy around.
Related tools
These free tools pair well with this page — open them in a new tab to finish your workflow.
常見問題
什麼是UUID?
UUID(通用唯一識別碼)是一個128位元數字,用於在電腦系統中唯一識別資訊。格式為32個十六進制數字,分組為8-4-4-4-12。
UUID各版本有什麼區別?
UUID v1使用當前時間戳和MAC位址;UUID v4使用隨機數,是最常用的版本。除非需要基於時間排序(v1)或基於名稱的確定性(v3/v5),推薦使用v4。
UUID真的是唯一的嗎?
UUID v4有122個隨機位元,可能的值約為2¹²²(約5.3×10³⁶)。在實際應用中,生成重複值的機率可以忽略不計。
可以將UUID用作資料庫主鍵嗎?
可以,UUID被廣泛用作主鍵,特別是在分散式系統中,自增整數可能發生衝突。注意隨機UUID(v4)在某些資料庫中可能導致索引碎片。
UUID區分大小寫嗎?
不區分。UUID表示不區分大小寫,大寫和小寫十六進制數字均有效且等同。
在瀏覽器中生成UUID安全嗎?
安全。此工具使用瀏覽器內建的crypto.randomUUID()或密碼學安全的隨機數生成器,輸出適合生產使用。