A version 4 UUID
The 4 at the start of the third group marks the version.
0f8fad5b-d9cb-469f-a165-70867728950eCreate unique identifiers for database rows, test data, API requests and file names. Generate one UUID or a thousand, choose classic random version 4 or modern time-ordered version 7, and format them the way your system expects.
The 4 at the start of the third group marks the version.
0f8fad5b-d9cb-469f-a165-70867728950e0f8fad5b-d9cb-469f-a165-70867728950e{0F8FAD5BD9CB469FA16570867728950E}Version 4 UUIDs are 122 bits of randomness — the chance of two ever colliding is astronomically small. Version 7 (standardised in RFC 9562, 2024) begins with a millisecond timestamp followed by random bits, so IDs created later sort later. That keeps database indexes compact and makes v7 a strong default for primary keys.
All UUIDs are generated with your browser’s cryptographically secure random number generator. They are unique identifiers, not secrets — don’t use them as passwords or security tokens.
For practical purposes, yes. With v4 you would need to generate billions of IDs per second for decades before a duplicate became likely. v7 adds the creation time, making collisions even less likely.
No. They are created in your browser using crypto.getRandomValues, and nothing is sent or stored.
Nothing meaningful: GUID is Microsoft’s name for the same 128-bit identifier. Windows tools often show GUIDs in uppercase and in braces, which the format options reproduce.
It reveals the time it was created, to the millisecond. If that matters for your use case — for example, public IDs that shouldn’t leak signup times — use v4.
Everything you need. One simple place.
Free, fast online tools for text, PDFs, images, data and everyday maths. Every tool runs entirely in your browser, so your files stay on your device.
© 2026 Toolora. All rights reserved.
Built for speed and privacy