AT-URI converter
Turn a bsky.app link into an at:// URI, and back.
Paste a bsky.app link or an at:// URI to get the other form, the stable link with the DID, and the parts of the URI: authority, collection and record key.
Converted
- AT URI
- at://did:plc:z72i7hdynmk6r22z27h6tvur
- bsky.app link
- https://bsky.app/profile/bsky.app
- Stable bsky.app link (with the DID)
- https://bsky.app/profile/did:plc:z72i7hdynmk6r22z27h6tvur
- Parts of the URI
Authority (DID) did:plc:z72i7hdynmk6r22z27h6tvur Collection (NSID) — Record key —
How it works
An AT URI names a record on the network: at://, then the account (a DID or a handle), the collection (app.bsky.feed.post for a post) and the record key. Apps and APIs use it where people use bsky.app links.
Profiles, posts, feeds, lists and starter packs have a bsky.app page; we map one to the other. A handle becomes its DID through Bluesky's AppView, so the URI keeps working after a change of handle.
Records of other collections have no bsky.app page: you get the AT URI only. When the record key is a TID, the TID decoder reads the date it encodes.
Questions
- How do I get the AT URI of a Bluesky post?
- Copy the post's link in the app (Share → Copy link) and paste it above. You get at://<did>/app.bsky.feed.post/<record key>.
- Why use the DID rather than the handle?
- The handle can change; the DID cannot. A URI or a link with the DID keeps pointing to the same record.
- Which links can it convert?
- Profiles, posts, feeds, lists and starter packs, both ways. Other AT URIs are read and split into parts, without a bsky.app link.
Documentation
Related tool
TID decoder
Read the date hidden in a record key.
Also useful:DID finderPost and thread viewer
See all the tools