TID decoder
Read the date hidden in a record key.
Paste a TID, a post's link or an at:// URI to see the moment its record key encodes, in UTC and in your time, with its clock identifier. Or generate a TID for now.
How it works
Most records, posts included, get a TID as their record key: 13 characters such as 3l6oveex3ii2l, the last part of a post's link. It is a 64-bit number written in a sortable base32 alphabet.
Its first 53 bits after a zero bit count the microseconds since 1 January 1970, and its last 10 bits are a clock identifier that keeps two keys made at the same instant apart. Decoding it gives the time the key was made.
That time is set by the app that wrote the record: it is a claim, not a proof, and it can be backdated. Everything runs in your browser; nothing is sent.
Questions
- How do I see when a Bluesky post was made from its link?
- Paste the post's link above: its last part is a TID, and the decoder shows the time it encodes, in UTC and in your time zone.
- Is the TID's time the real posting time?
- Usually, but not always: the app that created the record chose it, so an imported or backdated post can carry an older time.
- Why does it say this is not a TID?
- Some records use another record key: a profile is always self, and some apps choose their own keys. Those keys hold no date.
Documentation
Related tool
AT-URI converter
Turn a bsky.app link into an at:// URI, and back.
Also useful:Post character counterPost and thread viewer
See all the tools