ULID Generator, Decoder and UUID Converter
Create lexicographically sortable identifiers, inspect their millisecond timestamp, and convert the same 128 bits between ULID and UUID notation.
Generated ULIDs
Canonical uppercase Crockford Base32.
Create lexicographically sortable identifiers, inspect their millisecond timestamp, and convert the same 128 bits between ULID and UUID notation.
Canonical uppercase Crockford Base32.
A Universally Unique Lexicographically Sortable Identifier is a 128-bit identifier encoded as 26 Crockford Base32 characters. The first 48 bits store a Unix timestamp in milliseconds and the remaining 80 bits are random. Canonical ULIDs use uppercase characters and omit visually ambiguous letters.
ULIDs sort by creation time when their canonical text representations are compared. Values generated in the same millisecond share a timestamp prefix, but independently random tails do not guarantee creation order within that millisecond.
The decoder reads the first six bytes and displays the time in UTC, local time, and Unix milliseconds. The timestamp is metadata, so do not use ULIDs when exposing approximate creation time would be undesirable.
Both formats contain 128 bits. Conversion changes only the textual representation: Crockford Base32 for ULID and hexadecimal groups for UUID. A converted value is not assigned a UUID version, and converting an arbitrary UUID into ULID notation does not make its first bits a meaningful creation timestamp.
Generation uses crypto.getRandomValues() in your browser and does not send identifiers to MiniUtil. Collisions are extremely unlikely with 80 random bits, but an application that requires strict monotonic ordering or centralized uniqueness guarantees should use a production library and database constraints.
The format is documented by the ULID specification. Compare it with the UUID v7 Generator for an IETF-standard time-ordered UUID, the UUID v4 Generator for random UUIDs, or the GUID Generator for .NET-style formatting.
Share this utility
Send the tool, not any text or files you entered. Input is never added to the share URL.
Continue the workflow
Step 3 of 5. Keep the context and finish the related checks.
Keep working