Bluesky profiles have a description field — the bio — with a documented limit of 256 graphemes in the AT Protocol schema that defines a profile. That is roughly twice what Discord gives you and noticeably more than nothing, but it is still a single block of text doing several jobs at once.
If you build things, you probably have more than one destination worth showing: the repo, the live project, the newsletter, the personal site. This page covers what the platform gives you today and the honest options for fitting more than one link.
What the bio field actually is
That last point matters and we would rather flag it than pretend. The AT Protocol is developed in the open, so fields can exist at the data layer before every client puts a box on screen for them. Open your own profile editor and look: if there is a website field, use it, and treat everything below as being about the bio text you have left over.
- The field is called `description` in the protocol and appears as your bio when you edit your profile.
- Its documented maximum is 256 graphemes (2,560 bytes) in the profile schema.
- The protocol schema also gained a dedicated `website` field in September 2025.
- Whether that `website` field is exposed as an input box in the app you use is worth checking in your own client — schema support and app support are not the same thing.
A note on what domain handles are not
Bluesky lets you use a domain you own as your handle, so you can be @yourdomain.com instead of a bsky.social address. This is worth doing — it ties your account to something you control and reads as more credible.
It is not, however, a bio link. It changes your username, not the links on your profile, and it points at exactly one domain. People sometimes conflate the two because both involve a domain. If your goal is several destinations on your profile, the handle does not solve it.
Fitting several links into 256 characters
This is the real limit, and it is not the character count. A bio crammed with four addresses is technically within budget and still poor: nobody scans it, and it leaves no room to say what you are working on. The character limit is a hard constraint, but readability is the binding one.
- Count first. Three URLs plus a sentence about yourself is usually 200 characters or more, so the budget is tighter than it looks.
- Drop the protocol and the www when you write them out — a bare domain reads cleaner and costs fewer characters.
- Cut labels to one word. "repo", "site", "newsletter" do the job that a full clause was doing.
- Accept that a wall of URLs in a bio is hard to read, even when it fits.
The one-page approach
The alternative is the same one people reach for on X: publish one page that holds every link, and put that single short URL in your bio. You get your whole list, the bio keeps most of its characters for an actual sentence, and adding a fifth link later does not mean editing your profile again.
The tradeoff is honest — you are adding a hop between your profile and the destination, and some people will click through and stop there. That cost is worth paying when you have several links of roughly equal importance. It is not worth paying when one link matters far more than the rest, in which case put that link in the bio directly and skip all of this.
What this looks like with Pagr
Pagr is one form and one URL: a handle, a name, your links, and pagr.nanocorp.app/yourhandle is live. No account, no password, no dashboard. The page is server-rendered dark text, which is the point — it sits next to a repo without looking like a storefront.
Leave an email and you get a private edit link so you can add the next thing you ship without starting over. Free pages carry a small footer badge, and one payment of $19 removes it and unlocks a custom accent colour. Nothing recurring.