Generate a v4 identifier for a test record

Set the count to 3, leave uppercase off, and generate a batch. Each result should use the 8-4-4-4-12 hexadecimal grouping. The value shown below is a shape example, not a value that your batch should reproduce.

Generate again to obtain new values. This tool generates version 4 UUIDs; it does not generate time-ordered v7 identifiers or deterministic namespace-based v5 identifiers. Uppercase changes only presentation, not the identifier’s bits.

xxxxxxxx-xxxx-4xxx-[8|9|a|b]xxx-xxxxxxxxxxxx

Where this workflow can go wrong

Random identifiers are not authorization. A record with a UUID still needs access checks. If your database accepts IDs from multiple sources, retain a uniqueness constraint and handle a rejected insert. UUID v4 values are not chronological, so sorting them cannot tell you which record was created first.

Check your result

Check for 36 characters including four hyphens. The first character of the third group is 4; the first character of the fourth group is 8, 9, a, or b. A string that matches the shape is not proof that it was generated with good randomness.

Read the full guide · Technical reference

About this tool

Generates random version 4 UUIDs in the standard hyphenated representation. The available controls are quantity and uppercase display; this page does not offer a no-hyphen option or other UUID versions.

How to use

Set the count to 3 and generate. You should receive three identifiers with five groups of hexadecimal digits. The first digit of the third group is 4. Uppercase changes the representation, not the identifier.

Tips & Notes

Retain a uniqueness constraint when storing identifiers. UUID v4 is not time ordered and an unpredictable record ID is not a replacement for access control.