The Bluesky character limit with a link is exactly 300 characters. A URL typed directly into the text counts toward this total character for character, exactly like regular words. If you attach a link card instead, the URL does not consume any of your character allowance. A link card gives you back the space to write a complete thought before pointing readers to your site.
Does a typed URL count against the limit?
Yes. Every letter, number and punctuation mark in a URL you type into the post composer takes up a character. If your blog article has a 60-character address, pasting it into the text box leaves you with 240 characters for your message.
Long slugs chew through your limit fast. The protocol treats web addresses as standard text strings unless they are moved into an external embed. A lengthy domain name paired with a detailed blog path easily consumes a quarter of your available writing space.
What is the difference between a text link and a link card?
A text link sits inside the body of your post. Users can tap the blue text to leave the app, but it looks messy and eats up your writing space. A link card sits below your text, displaying the destination page title, a short excerpt and a thumbnail image.
When you paste a link into the official Bluesky app, it automatically fetches the page data and generates a link card. Once that card appears, you can delete the URL from the text area. The card remains attached to the post.
Deleting the text URL restores your character count. You regain the 60 or 70 characters the web address occupied. The link card handles the routing silently in the background.
How do you fit an article summary into 300 characters?
You cannot summarize a whole article in a single Bluesky post. 300 characters is roughly two short sentences. You have to pick one specific point and state it clearly.
Start with the answer. Look at the problem your blog article solves. Pull the exact solution out and make that the post. Do not write a teaser. People scroll past a post that says they need to click to find out how to fix a bug.
Write the command or the line of code that fixes the bug, then attach the link card for the full explanation. Provide immediate value in the text itself so the reader has a reason to visit your site.
How do UTM parameters affect the character count?
Tracking codes are a massive problem if you leave the URL in the text. A standard link might be 40 characters. Adding the source and medium tags pushes it well past 80 characters.
You lose over a third of your 300-character allowance just to tracking data. This forces you to write a very abrupt, incomplete message. If you paste a URL with deep tracking parameters into the text editor, you might hit the limit before you even type your first word.
When you use a link card, the UTM parameters hide inside the embed object. You track the click source perfectly without showing the ugly string to the reader or losing any writing space.
How does the Bluesky API handle text and links?
When you write code to post to Bluesky, you handle links through facets. A facet tells the server where a link begins and ends in your byte string. Text length is calculated in bytes, not just visual characters.
If you use emojis, they can take up more than one byte. You must calculate the string length precisely to avoid rejection. The API requires you to identify the start and end positions of the link within the byte array. If your calculation is off by a single byte, the server will reject the post or place the hyperlink on the wrong characters. I covered the exact payload structure when explaining how to use the Bluesky API to create a post.
If you want a link card via the API, you must explicitly construct an external embed object. You provide the URL, the title, the description and a blob reference for the thumbnail image. The text string remains completely separate from this embed object.
Can you automate the link card generation?
Yes. When I built AmplifySignal to run my own blogs, I wrote the Bluesky publisher to automatically extract the meta title and description from the drafted article.
The automation generates the external embed object and attaches it to the social post. It never puts the URL in the text body. This guarantees the drafted message has the full 300 characters available for the actual update.
The system pushes the Bluesky post about two hours after the article publishes on the blog. This gives the site time to serve the correct metadata if someone else shares the link manually first.
Why keep the post short when you have the space?
Even with the full 300 characters available, you do not have to use them all. A short, direct statement often works better than a paragraph that hits the character limit.
Readers scan a feed quickly. Two concise sentences get read. A block of text that fills the screen requires effort. If the link card already contains the article title and a description, repeating those words in your post text is redundant. Use the text to add an opinion or a specific result that the link card misses.
How do you edit a blog excerpt down to 300 characters?
Start by copying your article introduction. Paste it into a text editor. It is almost certainly too long.
Delete the setup. Remove any sentence that explains why the topic matters. The reader already knows it matters, or they would not be looking at your post. Delete adverbs and adjectives. Strip the text down to the noun and the verb. Find the core action the article describes.
If the article explains how to configure a server, do not write a long paragraph about performance benefits. Write a single sentence containing the exact Nginx setting. The second version is shorter, sharper and gives the reader a concrete reason to click the link card.
Can you use a URL shortener?
People used URL shorteners heavily when Twitter had a strict 140-character limit that included links. You do not need them on Bluesky.
A shortener hides the destination domain. Readers hesitate to click an unknown link because they cannot see where it goes. Trust is critical when asking someone to leave the platform.
The link card displays your actual domain name clearly. It proves the link goes to your site. Since the embedded card does not count against your limit, a shortener solves a problem that no longer exists.
What happens if you post multiple links?
The Bluesky composer only generates one link card per post. If you paste three different URLs into the text, the app will typically create a card for the first one it detects.
The remaining two URLs stay in the text. They count against your 300-character limit. You rarely need multiple links in a single short post.
Focus on one clear call to action. Drive the reader to one specific blog article. If you need to share a list of resources, put them inside the blog article itself rather than cluttering the social update.
How do quote posts handle links?
A quote post allows you to attach another user's Bluesky post to your own text. The quoted post acts as the embed.
You cannot have a quote post and a link card in the same message. The protocol only allows one embed object per post. If you quote a post and type a URL into your text, the URL stays as text.
It counts against your character limit. The link card will not generate because the quote embed already occupies that slot.
Does deleting the text link break the card?
No. The link card is an entirely separate piece of data attached to the post.
When you paste a URL into the official app, it fetches the metadata and builds the card. Once you see the card appear below your text, the app has secured that data.
You can highlight the URL in the text box and press delete. The card stays. The text box empties out, resetting your character count to zero. This is the exact workflow you should use every time you share a link manually.
What happens if a post exceeds 300 characters?
The Bluesky app prevents you from publishing. The character counter turns red and the post button grays out. You must edit the text down before it goes live.
If you send a post via the API that exceeds the limit, the server returns an error. The post fails silently from the user perspective. You must review your backend logs to see the rejection.
Automated tools handle this by retrying failed posts with backoff, but a hard limit error requires changing the text. The draft must be edited to fit the strict byte count.
How does this compare to other networks?
Every network has its own rules for links and length. A 300-character limit requires a different approach than a long-form platform. You cannot share the exact same text everywhere and expect it to look right.
LinkedIn gives you a massive character allowance, but cuts off the text with a prompt to read more very early. I wrote a detailed breakdown on the LinkedIn post character limit before see more to explain how to handle that specific truncation.
Writing one tailored post for Bluesky and a separate, longer post for LinkedIn gets better results than blasting a compromised middle ground to both.
How do you check your text length before posting?
You can write your draft in a plain text editor with a character count feature. This works well for standard English text.
The official web interface and mobile app handle this for you in real time, displaying a visual ring that fills up as you type. Once you cross the 300-character threshold, the ring turns red and displays the negative number of characters you need to remove.
If you include complex characters or emojis, a visual character count might mislead you. The safest method is to write concisely, aiming for 250 characters or fewer. This buffer ensures you never hit the backend byte limit. A 50-character safety margin covers unexpected encoding differences. If you want to stop counting characters and let a system format your external embeds automatically, try AmplifySignal for your site.