Fresh identifiers, ready for your next record, fixture or project.
UUIDs are identifiers, not passwords or API secrets. Do not treat an unguessable URL as authorization.
Changing an option replaces the current results. Nothing is saved or sent.
Downloads may contain secrets. Protect the file and only export when needed.
Generated entirely in your browser.
Nothing is sent to our server.
A UUID v4 is 128 bits wide, with version and variant fields leaving 122 random bits. The hyphenated text representation has 36 characters. The generator uses crypto.randomUUID() when available and otherwise fills 16 bytes with Web Crypto before setting the specified version and variant bits. Uppercase is a display choice; it does not create a different identifier.
Independent random UUIDs can collide. Applications that require unique records should still enforce a uniqueness constraint and handle conflicts. A UUID also does not prove who created a record or who may access it. Authorization belongs in the application, not in the apparent randomness of a record ID. The format follows RFC 9562.
Create up to 100 UUIDs at a time, copy an individual row, copy the list or download a text file with one value per line. The page keeps only the current batch. Use random tokens when you need a configurable amount of secret key material rather than a standardized identifier.
No. This tool creates only UUID v4. It does not embed a timestamp or provide time-ordered identifiers.
No, the UUIDs are independent random draws. A database uniqueness constraint remains appropriate even though random collisions are unlikely.