What you get
A UUID v4 is 122 random bits with a fixed version and variant nibble, shown in the usual 8-4-4-4-12 hex form. Collision risk is negligible for normal app volumes.
Regenerate whenever you need a fresh id. Do not use these as secret tokens; they are identifiers, not passwords.
Example use
Paste a new UUID into a fixture, database seed, or client-side key. Prefer your platform’s crypto random API in production code paths.
Uppercase versus lowercase hex is cosmetic; most systems accept either.
Questions people ask
UUID v1 vs v4?
This tool focuses on random v4. v1 embeds time and node information.
Are they sequential?
No. v4 values do not sort by creation time.
Safe in URLs?
Yes as opaque ids. Still validate format on the server.