ULID Inspector

Inspect ULID timestamps and random suffixes, validate format and export a structured JSON report.

Inspect 1-1,000 ULIDs, one per line. Uppercase and lowercase accepted; whitespace and blank lines rejected. Nothing is uploaded.

Read the timestamp inside a ULID

Paste one identifier per line and choose Process input. The inspector reports a canonical uppercase identifier, its Unix millisecond timestamp, a UTC ISO date and its 16-character randomness suffix. Lowercase input is accepted; ambiguous aliases such as O for zero or I for one are not repaired.

Inspect the supplied example

Load example (replaces inputs) inserts 01ARZ3NDEKTSV4RRFFQ69G5FAV. Its timestamp is 1469922850259, shown as 2016-07-30T23:54:10.259Z. Its randomness field is TSV4RRFFQ69G5FAV. Use the result to compare a logged identifier with an expected time range, not to prove when a remote event occurred.

Validation is structural

A ULID has 26 characters, but a valid 128-bit value cannot start above 7. The inspector rejects overflow rather than discarding high bits. It also rejects wrong lengths, excluded letters, punctuation and whitespace. Each line must be a complete identifier; a trailing newline creates an empty record and produces an error. CRLF, CR and LF are supported record separators.

A valid result says nothing about the trustworthiness of its source, uniqueness or quality of the random generator. The suffix is reported in encoded form, not interpreted as a secret or checksum. Custom timestamps can refer to the past or future. The maximum timestamp remains within JavaScript Date's range; dates beyond year 9999 use an expanded ISO year with a leading plus sign.

Batch reports and troubleshooting

Input supports up to 1,000 identifiers and 27,000 characters. If any line is invalid, the whole batch fails without silently omitting that line. Duplicate identifiers are retained in input order. Remove blank lines or accidental spaces rather than relying on automatic trimming.

Download the JSON array to preserve numeric timestampMs, string utc, normalized ulid and encoded randomness fields. No final newline is added. Editing the input removes the old report and download. Use ULID Generator to create fresh examples; this inspector does not generate or rewrite identifiers in your source system.

Format reference

The canonical ULID specification defines a 48-bit millisecond time component followed by 80 random bits. Its Crockford alphabet excludes I, L, O and U. These tools use that format, rather than the padded RFC 4648 alphabet used by a general Base32 text encoder. Processing and file creation happen locally in this browser.