About ID Inspector
The formats it knows
UUID — 32 hex characters in five groups. The version is one nibble, so a UUID states what kind it is: v4 random, v7 time-ordered, v1 time and MAC address, v3 and v5 hashed from a name. v1, v6 and v7 carry a timestamp.
ULID — 26 characters of Crockford base32, starting with 48 bits of millisecond time. Sorts chronologically as a string, which is the reason to pick one.
ObjectId — MongoDB's 24 hex characters, opening with four bytes of Unix seconds. KSUID is 27 base62 characters counting seconds from 2014. Snowflake is a long number holding milliseconds, a worker and a sequence. CUID and Nano ID round it out.
How much the shape proves
Some of these announce themselves and some only fit. A UUID carries its own version number; a ULID's first character cannot exceed 7 or the timestamp would not fit in 48 bits. Those are checkable.
A Nano ID is 21 characters from an alphabet that any random string can satisfy, and CUID2 hides its structure deliberately. For those, the honest answer is that the shape matches and nothing more, which is what the badge says.
Reading the timestamp
Roughly half of these encode when they were made, each counting from somewhere different: UUID v1 counts 100-nanosecond ticks from 1582, ObjectId counts seconds from 1970, KSUID counts seconds from 2014, and ULID and UUID v7 count milliseconds from 1970.
Snowflakes are the awkward case, because the epoch belongs to whoever issued the id — Twitter, Discord and Instagram each picked their own. Choose the right one and the date is exact; choose wrong and it is years out.
Common questions
- Can it generate an ID as well?
- No, and deliberately. A bode caches each block against a fingerprint of its inputs, so a block that returned something new every run could never be cached and would give a different answer to everyone you shared it with. Identifying an id is also the harder question: any language makes a UUID in one line, but almost nothing tells you what the string in your log is.
- Is a v4 UUID really unique?
- 122 random bits, so collisions are not a practical concern — but it is randomness, not a guarantee, and it depends on the generator using a real source of entropy. If ordering matters more than opacity, v7 is the modern choice.
- Why does my ID say "unrecognised"?
- It matched none of the known formats, which is not the same as being invalid. Plenty of systems mint their own ids, and a prefixed one like user_01H9X... will not match on its own — paste the part after the prefix.
- Does anything I paste get uploaded?
- No. The whole block is string and arithmetic work in your browser, and it makes no network requests at all.