Press Generate to create a random version four UUID, or choose a bulk count between one and one hundred before generating a batch. Select uppercase or lowercase for the representation your destination expects. Copy one result or use Copy All for newline separated values. The example below uses the Nil UUID control, which has a fixed output and is useful for recognizing an explicitly empty identifier.
Use random generated values for independent identifiers rather than reusing the nil value. The normal format has hexadecimal groups of eight, four, four, four, and twelve characters, separated by hyphens. Random UUIDs do not provide creation ordering for database indexes. History retains twenty entries during the current component session; copy important results before clearing it or leaving the page.
Control: Nil UUID
Output: 00000000-0000-0000-0000-000000000000
A UUID (Universally Unique Identifier) is a 128-bit identifier that is unique across all devices and time. Use UUIDs as primary keys in databases, for distributed systems, API identifiers, session tokens, and anywhere you need guaranteed unique identifiers without a central authority.
UUID v1 is time-based, v3 and v5 are name-based (using MD5 and SHA-1 respectively), v4 is randomly generated, and v7 is time-ordered. UUID v4 is the most commonly used version as it provides 122 bits of randomness with an extremely low collision probability.
UUID v4 has 2^122 possible values. The probability of collision is astronomically low — you would need to generate 2.71 quintillion UUIDs to have a 50% chance of a single collision. For practical purposes, UUID v4 values are unique.
UUID generation runs locally using your browser’s cryptographic random source. This interface does not offer server sharing or account saving. Copy results to your own files when you need to retain them; the displayed history lasts for this component session. A copied UUID is an identifier, not an access credential or proof of ownership.
UUIDs are excellent for distributed databases and microservices where auto-increment IDs can collide. However, UUID v4 can cause index fragmentation in B-tree indexes. Consider UUID v7 (time-ordered) for better database performance, or use UUIDs as secondary identifiers alongside auto-increment primary keys.