Skip to content
MySafeToolbox

UUID Generator

Free UUID generator for random v4 and time-ordered v7 IDs. Create up to 1,000 at once, then validate and decode any UUID. Secure, private and in your browser.

  • No upload — 100% private
  • Instant, on your device
  • Free, no sign-up
  • Works offline once loaded

How it works

How to use UUID Generator

  1. Choose v4 (random) or v7 (time-ordered).

  2. Set how many you need — from 1 to 1,000.

  3. Toggle uppercase, hyphens or braces to match your codebase.

  4. Copy all or download as a .txt file. Paste any UUID into the decoder to see its version and timestamp.

Why use it

Why use our UUID Generator tool

v4 and v7

Random v4 from crypto.randomUUID, plus RFC 9562 v7 IDs that sort by creation time.

Bulk generation

Up to 1,000 UUIDs in one click with copy-all and .txt download.

Format options

Uppercase, no hyphens or {braces} for SQL Server, .NET and other GUID conventions.

Validator & decoder

Checks any UUID and reveals its version, variant and embedded creation time for v1, v6 and v7.

Cryptographically secure

Uses the browser's secure random generator; IDs are created on your device and never sent anywhere.

FAQ

Frequently asked questions

What is the difference between UUID v4 and v7?

v4 is 122 bits of randomness. v7 starts with a 48-bit millisecond timestamp followed by random bits, so v7 IDs sort by creation time — much friendlier for database indexes.

Can two UUIDs ever collide?

In theory yes, in practice no. You would need to generate around 2.7 quintillion v4 UUIDs to reach a 50% chance of a single duplicate.

Is a GUID the same as a UUID?

Yes. GUID is Microsoft's name for the same 128-bit identifier format. Use the uppercase and braces options to match the usual GUID style.

Should I use UUID v7 as a database primary key?

Often, yes. Because v7 values increase over time, inserts land at the end of B-tree indexes, avoiding the page splits and fragmentation that random v4 keys cause.

Does a v7 UUID reveal when it was created?

Yes — the first 48 bits are a Unix timestamp in milliseconds. Paste one into the decoder to see it. Use v4 if creation time must stay private.