UUID Generator (v4 & v7) & Password Generator
Random v4 or time-ordered v7 UUIDs, a UUID inspector and strong passwords, all from your browser's cryptographic random generator.
UUID generator
v4 is 122 random bits: the safe default when you only need a unique ID.
UUID inspector
Password
How it works
Pick v4 for a purely random ID or v7 for one that starts with the current time in milliseconds, so IDs sort in creation order (handy for database keys). v7 follows RFC 9562 and adds a counter so several IDs made in the same millisecond still come out in order. Uppercase, no-hyphen and {brace} formats are one click away.
The UUID inspector reads any UUID you paste, with or without hyphens, braces or a urn:uuid: prefix, and tells you its version and variant; for v7, v6 and v1 it shows exactly when it was created. See UUID v4 vs v7 for which to choose.
Random v4 UUIDs come from crypto.randomUUID() and passwords from crypto.getRandomValues(), the same cryptographically secure source browsers use for TLS keys. Nothing is generated on, or sent to, a server.
Password characters are chosen without modulo bias, and the entropy figure shows roughly how many guesses an attacker would need (2 to that power). Around 80 bits is strong for most accounts; a password manager makes long random passwords painless.
Questions
What is the difference between UUID v4 and v7?
v4 is 122 random bits. v7 puts a millisecond Unix timestamp in the first 48 bits and fills the rest with random bits, so v7 IDs sort by creation time but reveal when they were made.
Can two UUID v4s collide?
In theory, but with 122 random bits you would need to generate billions per second for decades to have a realistic chance.
What does avoid look-alikes do?
It removes 0, O, 1, l and I, which are easy to misread when typing a password by hand.