We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Bulk generate unique identifiers (UUID/GUID) across multiple versions (V1-V7) for developers and system design.
Completely random, the most commonly used version.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
A UUID (also called a GUID) is a 128-bit identifier. This generator supports versions 1, 3, 4, 5, 6, and 7. Version 4 uses random or pseudorandom values; versions 1 and 6 are Gregorian time-based, while version 7 places Unix time information in the leading portion. Versions 3 and 5 are name-based: they combine a namespace UUID with a name to produce a repeatable result. These versions have different layouts and properties; a higher version number does not mean a stronger security level.
Version 4 is the default for general-purpose random identifiers. Choose version 5 when a stable mapping from a name is useful, or version 3 when compatibility specifically calls for it. RFC 9562 describes the formats and recommends version 5 over version 3 where possible. The standard text representation uses hexadecimal groups separated by hyphens.
For name-based versions, select DNS, URL, OID, or X.500, or enter a custom namespace UUID. Then enter the exact name string. The same version, namespace, and name reproduce the same UUID. Changing capitalization, punctuation, URL form, or namespace changes the input and can change the output. The generator applies one identical name to every requested row, so a batch of v3 or v5 results repeats that same value.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Pick v1, v3, v4, v5, v6, or v7. For v3 or v5, also choose a namespace and provide a name. A custom namespace must be a UUID in the familiar 8-4-4-4-12 hexadecimal pattern; an empty name or malformed custom namespace leaves no generated results.
Enter how many values to make, starting at one. The maximum is shown for your account in the control. Choose uppercase if your receiving system expects it, and turn off hyphens or add braces only when that system accepts those forms. These options change the printed representation, not the UUID bits.
Results appear one per line and can be copied together. For example, three v4 results give three generated identifiers; three v5 results with the same namespace and name give three copies of the same deterministic value.
Use cases
See how the tool fits into real work and everyday tasks.
Create a batch of v4 identifiers for sample records, then copy the lines into seed data or a test setup. Keep the target database's unique constraint as the final collision check.
Agree on one namespace and a canonical naming convention across services, then use v5 to map the same logical name consistently. Document case and URL normalization rules with the team.
Evaluate v7 or v6 when a time-oriented layout is useful. Verify ordering and storage behavior in the receiving application rather than assuming that a UUID version guarantees a database performance outcome.
Q&A
Find concise answers to common questions and confusing cases.
GUID stands for Globally Unique Identifier. RFC 9562 uses UUID and GUID for this 128-bit identifier format.
No, it changes only the text formatting. Keep the standard hyphenated form unless the field or protocol receiving the value explicitly expects another representation.
The same namespace and name produce the same name-based UUID each time. Use a distinct name for each record, or select a version suited to generating new values.
No, it changes only the text formatting. Keep the standard hyphenated form unless the field or protocol receiving the value explicitly expects another representation.
Notes
Review scope, result limitations, and important precautions before use.
A UUID identifies an item; it does not prove who created it, grant permission, or serve as a secret key. Name-based values also reveal when the same namespace and name have been reused. Apply access control and conflict handling in the system that stores or consumes the identifier.
Related
Discover related tools, collections, and available API capabilities.