Last updated: October 2026
UUID generator v4 free online — bulk, crypto-grade, no signup
Short answer: pick v4 (random) or v7 (time-ordered), set how many you need up to 1,000, and click Generate UUIDs — each ID is built with your browser's cryptographic randomness, with uppercase, no-hyphen and brace formats available. Copy all or download as .txt. No signup, nothing uploaded.
How it works
1. Choose the version: v4 for purely random IDs, v7 when the IDs will live in a database index (v7 starts with the current timestamp, so new rows sort naturally and indexes stay fast). 2. Set the count (1–1,000) and tick any format options — UPPERCASE, no hyphens, or {braces} for .NET-style GUIDs. 3. Click Generate UUIDs, then copy all or download the batch.
Randomness comes from crypto.getRandomValues (and crypto.randomUUID for v4 where available) — the same cryptographic source operating systems use — never Math.random. Because generation happens locally, no one else can see, log or predict your IDs.
When you need this
Seeding a database with test rows, generating API keys or session identifiers, creating unique filenames for uploads, or producing correlation IDs for distributed tracing — anywhere a "probably never repeats" label beats an auto-incrementing number. Bulk mode plus the .txt download covers fixtures and migrations in one step.
A UUID is unique — but it is not secret
UUIDs are designed to be practically unique, not to be unguessable passwords or security tokens. Anyone who sees a v4 UUID can't predict the next one, but a UUID alone is not access control — treat it as an identifier, not a key. For credentials that actually protect something, use the password generator instead. The format rules are defined in RFC 9562, which also explains why v7 (time-ordered) is better for database indexes than random v4.
Frequently asked questions
What is a UUID?
A UUID (Universally Unique Identifier) is a 128-bit label like 550e8400-e29b-41d4-a716-446655440000, used as database keys, session IDs and API identifiers. Version 4 UUIDs are random; version 7 UUIDs embed a timestamp so they sort in creation order.
Should I use UUID v4 or v7?
Use v4 when you just need a random unique ID. Use v7 when the IDs go into a database index — because v7 starts with the current timestamp, new rows sort naturally and indexes stay fast. Both are generated here with crypto-grade randomness.
Are these UUIDs really random?
Yes. Generation uses your browser's crypto.getRandomValues (with crypto.randomUUID for v4 where available) — the same cryptographic randomness operating systems use, not Math.random. Nothing is sent anywhere, so no one else can see or predict your IDs.
How many UUIDs can I generate at once?
Up to 1,000 per click. Set the count, choose your format options, and download the whole batch as a .txt file.
Is it private?
Completely. UUIDs are generated locally in your browser — no server, no logging, no tracking. You can even run this page offline after it loads.
What does the 8-4-4-4-12 format mean?
A UUID is 128 bits of data written as 32 hexadecimal digits, split into five groups of 8, 4, 4, 4 and 12 characters joined by hyphens — 36 characters in total, like 550e8400-e29b-41d4-a716-446655440000. In a v4 UUID, 122 of those bits are random and 6 are fixed: four bits mark the version (the leading "4" of the third group) and two bits mark the variant. The structure is standardized by RFC 4122 and updated by RFC 9562.
Can two UUIDs ever collide?
In theory, yes; in practice, treat it as impossible. A v4 UUID has 122 random bits — roughly 5.3 × 10^36 possible values. You would need to generate around two billion UUIDs per second for 36 years before reaching a 50% chance of a single duplicate. No uniqueness check or retry logic is needed for normal workloads.
Is a UUID the same as a GUID?
Essentially, yes. GUID (Globally Unique Identifier) is Microsoft's name for the same 128-bit structure — Windows stores them with braces, like {550e8400-e29b-41d4-a716-446655440000}. That is exactly what the {braces} option above produces.
Which standard defines UUIDs?
The original specification is RFC 4122 from 2005. It was superseded in 2024 by RFC 9562, which added newer versions — v6, v7 and v8 — while keeping v1 through v5 valid. The UUIDs generated here follow those standards, so they work in any system that expects a proper UUID.
What about UUID v1, v3, v5 or v6?
Other versions exist for special cases: v1 embeds a timestamp and the machine's MAC address (useful for ordering, but it leaks identity), v3 and v5 are name-based — the same namespace plus name always produces the same ID, via MD5 (v3) or SHA-1 (v5) — and v6 is a timestamp-based variant whose layout sorts naturally. This tool generates v4 and v7, which cover the vast majority of use cases.
Can I use UUIDs as database primary keys?
Yes — it is one of their most common uses, especially in distributed systems where several machines must mint IDs independently without ever colliding. Prefer v7 for primary keys: because it starts with a timestamp, new rows arrive in order and B-tree indexes stay compact, whereas fully random v4 keys scatter inserts across the index.