Create one or one hundred random UUID v4 values in a single click, formatted the way your database or code expects.
Runs in your browser — nothing is uploaded
Each UUID comes from 122 random bits supplied by your browser's cryptographic random source. The values are never sent to a server or stored.
A UUID (universally unique identifier) is a 128-bit value written as 32 hexadecimal digits in five groups. Version 4 UUIDs are filled with random bits, so they can be created anywhere without a central server or a database sequence.
The format matters when you move values between systems. Some databases store UUIDs as binary, some expect the hyphenated form, and some prefer plain hexadecimal. The options above switch between those layouts without changing the identifier itself.
Values are created with crypto.getRandomValues in your browser. They are never sent to a server, so you can generate identifiers for real data without depending on a third-party service.
They are the same 128-bit format. GUID is the name Microsoft uses for UUIDs in .NET and Windows, and in practice the two terms are interchangeable. The lowercase hyphenated form is the canonical representation in RFC 9562, while Windows tools often display uppercase with braces around the value.
They are unique with overwhelming probability rather than by construction. A v4 UUID has 122 random bits. You would need to generate roughly 100 trillion values before the chance of any collision reaches one in a billion, so accidental duplicates are not a practical concern for ordinary systems.
UUID v7 (RFC 9562) puts a millisecond timestamp in its leading bits, so new keys sort roughly in creation order. That keeps B-tree indexes compact and avoids the page splits that fully random v4 keys cause on insert-heavy tables. Use v4 when you need pure randomness and do not care about ordering.
Only with care. The bits come from a cryptographically secure generator, but a UUID is not designed as a credential. Its layout is fixed, and UUIDs often appear in URLs and logs. For API keys or session tokens, use a dedicated token generator with at least 128 random bits and handle the result exactly like a password.
The compact 32-character form is common in URLs, file names and some databases. Both forms encode exactly the same 128 bits; only the hyphens differ. Pick the one your target system documents and keep it consistent across services.
No. The values exist only in the page until you copy or download them. Nothing is written to local storage, cookies or a server.