TypeID Generator and Decoder

How to use

1. 1Pick a mode: Generate to create new TypeIDs, Decode and validate to inspect one, or UUID to TypeID to convert an existing UUID.
2. 2To generate, type a type prefix (or leave it blank), choose how many to create, and keep Use current time or pick a specific date and time. Click Generate TypeIDs.
3. 3Use the Monotonic option when generating a batch so identifiers created in the same millisecond stay strictly increasing, then Copy all or copy a single value.
4. 4To decode, paste a TypeID. The tool validates it against the spec and shows the prefix, the underlying UUID, the UUID version and variant, and the embedded timestamp for version 7 IDs.
5. 5If a TypeID is invalid, read the red message for the exact reason, such as an uppercase prefix, a wrong suffix length, or a character outside the alphabet.
6. 6To convert, paste a UUID and an optional prefix to get the matching TypeID, then copy it.

About this tool

TypeID Generator and Decoder is a single-purpose tool for working with TypeIDs, the type-safe, K-sortable identifier format inspired by Stripe-style prefixed IDs. A TypeID is a type prefix, an underscore separator, and a 26-character base32 suffix, like user_01h455vb4pex5vsknk084sn02q. The suffix is a standard 128-bit UUID encoded most-significant-byte-first using the lowercase Crockford base32 alphabet (0123456789abcdefghjkmnpqrstvwxyz, the Crockford set with the ambiguous letters i, l, o, and u removed), and when the UUID is a version 7 value its leading bytes hold a millisecond timestamp, which is what makes a TypeID sort by creation time with a plain string sort. The tool does three jobs. Generate mints fresh TypeIDs from a freshly built UUIDv7: it stamps the current time (or a date and time you pick) into the first 48 bits, fills the rest with cryptographically secure random bytes from the browser crypto API, sets the version and variant bits, and base32-encodes the result, with an optional monotonic mode that increments the entropy so a batch created inside the same millisecond stays strictly increasing. You choose the prefix and how many to generate at once. Decode and validate parses any TypeID string: it splits the prefix from the suffix on the final underscore (the prefix may itself contain underscores, the suffix never does), checks every spec rule, and on success shows the prefix, the underlying UUID in canonical 8-4-4-4-12 form, the UUID version and variant, the embedded Unix-millisecond timestamp and ISO 8601 time for version 7 inputs, a relative description such as 3 years ago, and the 16 raw bytes in hex. On failure it explains exactly what is wrong: an uppercase or non-letter prefix, a prefix that starts or ends with an underscore or is longer than 63 characters, a separator with no prefix, a suffix that is not exactly 26 characters, a character outside the alphabet (including the ambiguous i, l, o, and u that strict TypeID rejects), or a value that overflows 128 bits because its leading character is above 7. UUID to TypeID converts an existing UUID of any version into a TypeID with the prefix you supply, so you can adopt TypeIDs over data you already store. The base32 byte packing was checked against the published TypeID specification test vectors, including the nil identifier, the boundary values for one, sixteen, and thirty-two, the maximum valid suffix, the full-alphabet case, and a real UUIDv7, so encode and decode round-trip exactly. The reference panels lay out the anatomy of a TypeID and how it compares to a bare UUID, a ULID, and a 64-bit snowflake. Everything runs locally in your browser; the identifiers you generate or paste are never uploaded or logged.

Free to use. Works in your browser. No signup, no login.