Yes. UUIDs are generated in your browser using the Web Crypto API's cryptographically secure random number generator — the same CSPRNG used for TLS. No server is involved at any point.
Generate cryptographically secure UUID v4 and v7 identifiers in bulk — or classic Microsoft GUID format with one click. Paste any UUID or GUID and instantly decode its version, variant, and embedded timestamp. Everything runs locally via the Web Crypto API: your identifiers are never uploaded, logged, or sent to any server.
crypto.getRandomValues), the same CSPRNG your browser
uses for TLS. Need classic Microsoft GUID style? One click gives you {UPPERCASE}
format, ready to paste into C#, SQL Server, or Active Directory code.
Pick how many UUIDs you need, from 1 up to 500 at a time.
v4 or v7, uppercase, braces, no dashes — plus ready-made JSON arrays and CSV lists.
Every UUID is created by the Web Crypto API on your machine, never on a server.
Copy any format with one click, or inspect a pasted UUID to decode its metadata.
Generate SHA-256/512 hashes from text or files, or cryptographically secure passwords — all in your browser.
Browse All Free Tools →| Version | Example | What it represents |
|---|---|---|
| v1 | 550e8400-e29b-11d4-... | Time-based — derived from the MAC address and a 60-bit Gregorian timestamp. Unique but leaks the generating machine's identity and time. |
| v3 | ...-3xxx-... | Name-based — MD5 hash of a namespace and name. Same input always yields the same UUID. |
| v4 | ...-4xxx-[89ab]... | Random — 122 random bits. The most common choice when you don't need ordering or reproducibility. |
| v5 | ...-5xxx-... | Name-based — same as v3 but using SHA-1, which is preferred today. |
| v6 | ...-6xxx-... | Time-based, reordered — a v1 with fields reordered so the timestamp reads naturally left-to-right, improving index locality. |
| v7 | 0189d0e0-78d4-7xxx-... | Time-ordered — 48-bit Unix millisecond timestamp followed by random bits. Ideal for database keys: sortable by creation time. |
| v8 | ...-8xxx-... | Custom — free-form, defined by the implementer. RFC 9562 reserves it for custom or experimental layouts. |
Practically nothing. GUID is Microsoft's term for a UUID; both are 128-bit identifiers. The classic GUID display style is uppercase with braces ({A3BB189E-8BF9-438A-A0F2-0C9F49B1F234}), which RFC 4122 permits — this tool offers it as a format option.
No. With 122 random bits, you would need to generate about 2.6 × 10¹⁸ UUIDs before reaching even a one-in-a-billion chance of a collision. For any realistic workload, v4 collisions are impossible — which is why they're safe to use as database keys without checking for duplicates.
Yes. UUIDs are generated in your browser using the Web Crypto API's cryptographically secure random number generator — the same CSPRNG used for TLS. No server is involved at any point.
No. All generation and decoding happens entirely in your browser. Nothing is sent to any server, and there is no registration.
UUID v4 is fully random. UUID v7 embeds a 48-bit Unix millisecond timestamp, so identifiers sort chronologically — which improves database index locality and makes v7 a better primary key. Use v4 when you want no timing information revealed.
Yes. Because generation happens 100% in your browser, your UUIDs are never transmitted, logged, or stored on any server — there is no risk that a production identifier ends up in someone else's database.