Generate random UUIDs and GUIDs instantly with our free online UUID Generator. Create RFC 4122-compliant UUID v4 (random), UUID v7 (time-ordered), and NIL UUIDs in any quantity - all produced locally in your browser using the Web Crypto API for cryptographically secure randomness and complete privacy.
Our UUID generator uses crypto.getRandomValues instead of Math.random() , so every identifier is unpredictable and safe to use for database primary keys, API tokens, distributed systems, and session IDs. Customize the version, quantity, case, hyphens, and GUID brace formatting.
Here is sample output for both random and time-ordered variants. Notice the version digit (the first hex of the third group) is 4 for v4 and 7 for v7:
Generate 3x UUID v4
Generate 1x UUID v7c3a9c4f1-8b2e-4d77-9a01-2f5e6a7b8c9d
7e1d3b5a-0c64-4f2a-bd10-6a8c9e0f1a2b
0b9f2c4d-7e8a-4310-9b6c-3d5e8f1a2b3c
01923f7e-7b4d-7a01-9c2e-4f5a6b8c0d1e (v7: sorts after older v7s)crypto.getRandomValues ) - never Math.random() . A UUID (Universally Unique Identifier), also called a GUID (Globally Unique Identifier), is a 128-bit identifier standardized in RFC 4122 . It is most often shown as a 36-character hexadecimal string grouped as 8-4-4-4-12 , for example 550e8400-e29b-41d4-a716-446655440000 . Because the 128-bit space is astronomically large, randomly generated UUIDs are unique in practice without any central coordination, which makes them ideal primary keys, API tokens, and correlation IDs.
The hyphenated layout maps directly onto the UUID's internal fields. The 13th hex digit encodes the version , and the first digit of the fourth group encodes the variant , so any standards-compliant parser can tell a v4 from a v7 at a glance.
00000000-0000-0000-0000-000000000000 , used as a sentinel or placeholder meaning "no identifier assigned". Because a UUID v4 carries 122 bits of randomness, the chance of a collision is vanishingly small. The classic birthday-paradox math says you would need to generate around 2.71 × 10¹⁸ UUIDs before reaching even a 50% chance of a single duplicate — roughly a billion generated IDs every second for over 85 years. In practice, that means randomly generated UUIDs are safe to use as unique keys with no central coordinator, which is exactly why they power database primary keys, API tokens, and correlation IDs across distributed services.
Choosing the right version matters. Use v4 when you only need uniqueness. Use v7 for new database primary keys: because each value starts with a millisecond timestamp, rows insert in sorted order, keeping B-tree indexes compact and range queries fast. NIL is a sentinel meaning "no value." UUIDs are identifiers, not secrets — they are predictable enough to enumerate in some versions, so never use one as a password; for secrets, use the Password Generator.