1
Choose a version
Use v4 for a general random identifier or v7 when approximate creation-time ordering is helpful.
GENERATE.01 UUID GENERATOR
UUID Generator
Generation and presentation stay separate: create a stable v4 or v7 list, then switch GUID, JSON, SQL, and other output formats without regenerating it.
Generation settings
Version
Letter case
Uses browser-secure randomness and stores no result
Generated values
Choose a version and quantity, then generate UUIDs Choose a version and quantity, then generate UUIDsv4
UUID / GUID validator
Waiting to validate
- Standard format
- —
- Version
- —
- Variant
- —
§ 01
How to generate and use UUIDs
2
Set quantity and format
Generate 1 to 1000 values. Display style and JSON or SQL templates can change afterward without replacing the IDs.
3
Copy, download, or validate
Copy the full result, download the active template, or inspect an existing UUID version and variant below.
§ 02
UUID v4, v7, and GUID
A UUID is a 128-bit universally unique identifier, usually shown as 32 hexadecimal characters and four hyphens. v4 uses secure random bits; v7 puts Unix milliseconds in the high bits so lexical order roughly follows creation time.
GUID is the common term in Microsoft ecosystems. It is generally compatible with UUID in APIs and databases, with differences mostly in uppercase, hyphen, and brace display conventions.
§ 03
Choosing a version and format
Type
Characteristics
Good fit
UUID v4Secure random value without time data
General objects, request IDs, test data
UUID v7Timestamp in high bits for approximate ordering
Logs, events, orders, database keys
GUID displayUppercase or brace-wrapped UUID text
.NET, Windows, SQL Server
§ 04
Generate UUID v4 in code
§ 05
Frequently Asked Questions
Q1Should I use UUID v4 or UUID v7?
v4 is widely supported and fully random, making it a strong default. v7 places a millisecond timestamp in the high bits, useful for events, logs, or database indexes that benefit from time ordering.
Q2Are UUID and GUID the same thing?
They are compatible 128-bit identifiers in most practical development. GUID is the common Microsoft and .NET term and often favors uppercase or brace-wrapped display formats.
Q3Can UUID v4 values collide?
A collision is theoretically possible in any finite space, but v4 has 122 random bits and the probability is extremely low with a secure random source. A database unique constraint should still be the final guard.
Q4Why does changing a JSON or SQL template keep the same IDs?
Value generation and presentation are intentionally separate. You can adapt the same batch for several destinations without losing it because of a formatting click.
Q5Are generated or validated UUIDs saved?
No. Generation, formatting, and validation happen only in the current browser page, with no server upload or local storage.