UUID Generator

v4 random, cryptographically secure
1
—
click Generate

Collision chance is negligible

UUID v4 has 122 bits of randomness. To expect a single collision you'd need to generate 2.71×10¹⁸ UUIDs — roughly 139 years of generating 1 billion per second. Use them as primary keys, session IDs, and trace IDs without fear.

Related tools

UUID versions

Used by: PostgreSQL uuid type, MySQL UUID(), MongoDB ObjectID alternative, Session cookies, Distributed trace IDs, wire formats, file uploads.

Frequently asked questions

UUID vs GUID — same thing?

Yes. GUID (Globally Unique IDentifier) is the Microsoft name; UUID (Universally Unique IDentifier) is the RFC 4122 standard. They have the same format and are interchangeable in practice.

Can I use UUIDs as primary key in my database?

Yes — PostgreSQL has a native uuid type, MySQL has UUID(). But sequential v4 UUIDs hurt InnoDB index performance due to random inserts. For MySQL/MariaDB use UUID_TO_BIN(id, 1) (time-ordered) or the newer UUIDv7 which has timestamp prefix.

Are these UUIDs valid offline?

Yes — UUIDs need no central authority. Anyone, anywhere, anytime can generate v4 UUIDs and trust they'll collide with some other UUID with probability smaller than winning a lottery every day for your entire life.

Why 36 characters?

32 hex digits + 4 dashes. The dashes are purely cosmetic, breaking the ID into 8-4-4-4-12 segments. Strip or uppercase freely — the underlying 16 bytes are the same.