One click to generate a single UUID, or a thousand. Pick v4 for random, v7 for time-ordered database keys, v1 for legacy compatibility. Copy all or download as CSV — everything runs in your browser.
UUIDs look random but aren't secrets. ClipGate's classifier knows the difference — it tags them as identifiers so they stay freely pasteable in your clipboard history, while real credentials stay locked.
// click Generate to create UUIDs
A UUID is a 128-bit identifier written as 32 hex characters in the pattern 8-4-4-4-12. The version (the first hex digit of the third group) tells you how it was generated: 4 for random, 7 for time-ordered, 1 for time+node. This generator runs entirely in your browser using crypto.randomUUID() and crypto.getRandomValues() — no network, no logging.
A Universally Unique Identifier is a 128-bit number designed so that anyone, anywhere, can generate one without coordinating with anyone else and still be confident it's unique. The standard (RFC 9562, which supersedes RFC 4122) defines several versions that trade randomness for ordering or embedded metadata. The canonical string form is 32 lowercase hex digits grouped as xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx, where M is the version and the top two bits of N are the variant.
v4 — 122 bits of CSPRNG randomness. Safe default. Use when you don't care about ordering. v7 — 48 bits of millisecond timestamp in the high bits, 74 bits of randomness in the low bits. Sorts chronologically, which makes it a drop-in replacement for auto-increment integers on B-tree indexes. v1 — 60-bit timestamp plus a 48-bit "node" identifier that was originally supposed to be a MAC address. Today it's a legacy format; we synthesize a random node for this generator so nothing identifying leaks.
crypto.randomUUID() cryptographically safe?Yes. It's part of the Web Crypto standard and is backed by the same CSPRNG the browser uses for TLS key generation. A v4 UUID has 122 bits of entropy — to get even a 1% collision probability you'd need to generate about 2.7 quintillion of them. It's shipped in every modern browser, Node 19+, Deno, and Bun. This tool uses crypto.randomUUID() directly for v4, and crypto.getRandomValues() plus manual bit-packing for v7 and v1.
A random v4 primary key scatters every insert across your B-tree index, causing page splits, fragmentation, and poor cache locality — especially bad on high-throughput tables. A v7 key, by contrast, is time-ordered: new rows always insert at the tail of the index, behaving like an auto-increment integer but without the shared-counter bottleneck. You get UUID benefits (no central authority, safe for distributed systems) and sequential-key performance. Postgres, MySQL, and SQLite all see measurable write-throughput improvements on large tables.
ClipGate's classifier sees a UUID as what it is: a 128-bit identifier, not a credential. It's tagged as a generic ID and kept fully searchable and pasteable in your clipboard history. ClipGate only applies its paste-block to things that look like real secrets — API keys, JWTs, private keys, high-entropy tokens with secret-shaped prefixes. You can generate a thousand UUIDs here and paste them anywhere without unlocking anything.