Generate Version 4 UUIDs for Test Records
Create random identifiers for sample records while keeping uniqueness checks and authorisation separate from identifier generation.
Use the interactive tool ↓Choose the identifier behavior you need
This generator creates random version 4 UUIDs. It does not create time-ordered version 7 IDs, deterministic name-based IDs or a database sequence. If a system requires a specific identifier version, check that requirement before pasting generated values into it.
UUID Generator
0cfcf129-1c7c-4675-949a-e36dac9575b000456219-8cc0-4ad9-be30-3b92c17afb803ebe8e93-073b-4ba6-ad9b-150e9dc246cbc51316b8-69f7-4b4f-85fb-df328ab099e8ae28fe70-1d04-4950-aa45-68f553344d8d
Inspect the format before importing a batch
A UUID has five hexadecimal groups in the familiar 8-4-4-4-12 layout. For version 4, the first character in the third group is 4; the variant field starts the fourth group with 8, 9, a or b. These visible fields describe structure, not proof that a value was generated securely.
The implementation uses the browser’s crypto.randomUUID where available, with a getRandomValues fallback that sets the version and variant bits. The UUID specification, RFC 9562, describes these versions and fields.
Build a small test fixture
- Choose a count of three and select Generate.
- Copy each identifier into a separate record, or use Copy all for newline-separated values.
- Verify that the receiving import expects one value per line rather than comma-separated columns.
- Keep a unique constraint in the destination database.
The interface bounds an explicit batch to 1–100 values. Requesting a new batch replaces the displayed batch, so copy values you intend to retain before generating again. Generated identifiers are not registered with a central Toolza lookup service.
Distinguish random from guaranteed unique
Random UUIDs make accidental collisions unlikely under appropriate generation, but they do not remove the need to handle a duplicate-key response in software. Regenerate or retry according to the application’s transaction rules rather than dropping a uniqueness constraint.
A hard-to-guess record ID also does not replace access control. Possessing an identifier must not automatically grant permission to read or edit the record. This utility is an identifier generator, not a password manager or token authorisation service.
Troubleshoot copying and compatibility
Clipboard permissions may vary by browser; check the pasted result in a harmless editor. Preserve hyphens if the receiving system expects canonical UUID text. If it expects a compact or binary representation, follow that system’s conversion rule instead of assuming this tool exports that representation.