Fresh version-4 UUIDs, generated with your browser’s cryptographic random source. Click any UUID to copy it.
Generate random UUID v4 identifiers one at a time or in bulk — up to 100 at once — with uppercase and hyphen options, all on your own device.
100% free · No sign-up · No daily limits · No watermarks · Processed in your browser — files never leave your device
Generate random UUID v4 identifiers one at a time or in bulk — up to 100 at once — with uppercase and hyphen options, all on your own device.
A developer seeding a demo database needs 40 user IDs: set the count to 40, click Generate, then Copy all, and paste forty lines straight into the SQL seed file. Each one — for example 9b2f207e-6d3a-4b1f-8e5c-2a7d9c4f01b3 — is a valid version-4 UUID, generated fresh on that click.
Each UUID is built from 122 bits of randomness supplied by your browser’s cryptographic random source (crypto.randomUUID where available, otherwise crypto.getRandomValues with the version and variant bits set by hand, following RFC 4122 / RFC 9562). The randomness comes from the operating system’s entropy pool — the same source your browser uses for encryption keys — which is what makes collisions a practical impossibility rather than merely unlikely. Nothing is generated or stored on a server.
A universally unique identifier, version 4, is a 128-bit value shown as 32 hexadecimal digits in five groups (8-4-4-4-12) where almost every bit is random. The fixed bits — a “4” starting the third group and an 8, 9, a or b starting the fourth — are how readers know it is version 4.
In practice, no. With 122 random bits, you would need to generate roughly a billion UUIDs per second for a century before a collision became likely. Systems like Git, Windows and every major database rely on exactly this property.
Nothing of substance: GUID is Microsoft’s name for the same 128-bit identifier family. A UUID v4 from this page is a valid GUID anywhere GUIDs are accepted, including .NET and SQL Server (where it maps to the uniqueidentifier type).
Only when a specific system demands it. The canonical form — lowercase with hyphens — is what RFCs, documentation and most libraries display and accept. Stripping hyphens gives the “N” format some .NET and database contexts use; uppercase is mostly cosmetic.
No. Generation happens in your browser from its built-in cryptographic random generator; the values are never transmitted, logged or stored anywhere. Refresh the page and they are gone unless you copied them.