Free Bluesky Share Link Generator

A Bluesky share link is a normal https URL that opens the Bluesky composer with a draft already typed. The address is https://bsky.app/intent/compose?text= followed by your URL-encoded message. Bluesky calls these intent links, the same idea as the classic tweet intent or the LinkedIn share URL. The person clicking it still reads the draft and presses Post themselves, nothing is published automatically.

A profile link asks the reader to do the work: open Bluesky, start a post, find your URL again, write something. A share link collapses all of that into one tap and lands them in a composer that already says what you want said. The practical effect is that far more people finish the share, and the wording of those shares stays consistent, which matters when you are trying to get a specific phrase or product name repeated.

Yes, and this is the single most common mistake. The compose intent has exactly one parameter, text, so your link is simply part of the message body and every character of it counts. A 60 character URL takes a fifth of your entire budget. Our counter adds the URL and hashtags to your post text and shows the real total before you ship the button.

No. Bluesky visually truncates long URLs when a post is displayed in the feed, but that is a display trick applied after posting, not a shortener. Inside the composer the full URL sits there as raw text and consumes the full character count. If your URL is long, shorten it before you build the share link, that is the only way to buy back characters.

It works in both, with a caveat. On desktop the link opens bsky.app in the browser and drops the text straight into the composer. On mobile, iOS and Android hand bsky.app URLs to the installed Bluesky app through Universal Links and App Links, so the app composer opens with your draft. If the app is not installed, the mobile browser opens the web composer instead, and the text still arrives.

No. The compose intent accepts text only, there is no parameter for media, alt text, or a poll. Anyone telling you otherwise is describing a different network. If you need an image in the post you have two options: attach it manually after the composer opens, or publish through the AT Protocol API with your own client, which uploads the blob first and then creates the record.

Not with an intent link. A share link does nothing until a human clicks it, so there is no moment in time to schedule. Scheduling requires either a third party tool that holds an app password and posts on your behalf, or your own AT Protocol integration. Share links solve distribution, not timing.

They point in opposite directions. A share link sends people INTO Bluesky with a draft ready to publish, so it belongs on your website, in your newsletter, or at the end of a blog post. A shortened link sends people OUT of Bluesky to your destination, so it belongs inside your own posts and bio. Use our Bluesky link shortener for that second job, and use this generator for the first.

Bluesky counts graphemes, which is the technical term for what a human sees as one character, so a standard emoji counts as one and an accented letter counts as one. Our counter walks code points instead, which means a flag or a skin tone emoji can read as two here. That difference always errs on the safe side: if our counter says you fit, Bluesky agrees.

Neither. The generator builds a URL string in your browser, it never talks to Bluesky, and there is nothing to authenticate. You only need an account at the moment someone actually clicks the link and posts, and that account belongs to them, not to you. Nothing here touches the AT Protocol, app passwords, or OAuth.

Yes. Type them in the hashtags field without the hash symbol and we normalise and append them. Bluesky parses hashtags at post time and turns them into tappable facets, so they become real clickable tags in the published post. Two or three focused tags outperform a wall of them, and remember each one eats into the same 300 characters.

Bluesky shows the sign in screen first. Whether the draft survives the login round trip depends on the client and the session state, so treat a logged out click as a lower probability share. This is a good argument for putting the share button where your logged in Bluesky audience already is: your newsletter, your docs, your thank you page after a signup.

Not from Bluesky, which reports nothing back to you about intent clicks. The workaround is to point your button at a Flyn short link that redirects to the bsky.app intent URL. Flyn counts every click, so you learn which page, newsletter, or docs section actually drives shares, and the composer still opens with your text intact.

No. Everything on this page is built with client side JavaScript. Your text, URL, and hashtags never leave the browser, there is no API call behind the Build button, and no server log of what you typed. The optional history lives in your browser localStorage and is capped at the last twenty entries.

Almost always double encoding. The text parameter is already percent encoded, so a tool that helpfully encodes the whole href a second time turns %20 into %2520 and the composer fills with garbage. Paste the link exactly as generated, and if your email or CMS editor mangles it, use the HTML snippet we output instead of retyping the href.