UUID and ULID Generator

Random and time-ordered identifiers, with what each kind is good and bad at.

UUID version 4

b08096fb-f129-4e07-a091-e00e2f80b359
0a769ec8-2148-4eb8-b38d-78912446429f
ad64f017-2dc6-4216-a9d3-25ea397f36b9
16af29d2-feb3-4a69-88e3-493dc55a61e1
f2994efd-f6a8-4289-8e1b-d9d823617550

Random. 122 bits of it, and nothing else.

Which one to use

UUID version 4
The right default. Nothing about it can be read back: no time, no machine, no order.
The wrong choice for a primary key in a large table. Consecutive rows land in unrelated places in the index, which makes inserts slower and the index larger than it needs to be.
UUID version 7
A version 4 with the clock in front. Sorts by creation time, so an index grows at one end.
The same 36 characters and the same shape, so a column, a type and a library that hold a UUID hold this one without changing. The cost is that the creation time is now readable by anyone holding the identifier.
ULID
The same trade as version 7, decided before version 7 existed. 26 characters, no hyphens, case-insensitive.
Shorter, and easier to select with a double-click or read aloud. Against it: a community specification rather than an RFC, and a database with a native UUID type will not store it as one.

Generated on this server with the operating system's random source, sent once, and not stored. Reloading gives different ones; there is no way to get these back.