BlueskyImages & previewToolFree
See the link card your post will get before you publish it, and find out why a card is missing.
Paste the post text, the page title, description and image to see the card as it will look in the feed. Checking a live URL against the Bluesky card service is coming soon.
A Bluesky link preview is not generated when someone views the post. It is built once, by the app that creates the post, and stored inside the post record.
| What you see | Likely cause | Fix |
|---|---|---|
| No card at all | The page returned an error to the card service, or timed out | Make the page public and fast; let link-preview fetchers through your firewall |
| Card titled "Just a moment" | A security challenge page was read instead of your page | Add a rule that lets link-preview fetchers past the challenge |
| Wrong or empty title | Tags are added by JavaScript, so the raw HTML has none | Render og:title and og:description on the server |
| Card with no image | No og:image, a relative path, or an image that does not load | Use an absolute HTTPS og:image URL |
| No card on posts sent from a script or scheduler | The sender did not attach a card | Post the link from the Bluesky app, or build the card in your code |
| Old posts show the old card | Cards are stored when a post is created | Fixes apply to new posts only |
Yes. Through the API a link counts at its full length toward the 300-grapheme limit; the bsky.app composer only shortens how the link is displayed. The card itself does not count.
Give the post real likes and replies from real people so custom feeds pick it up.
Either the card service could not read your page, or the post was sent without a card. Pages that block fetchers, return errors or add tags with JavaScript get no card.
The card thumbnail is capped at 1,000,000 bytes. The Bluesky app resizes larger images for you.
The card is part of the post. The sending app has to attach it; plain text with a URL gets none.
No. Cards are stored when a post is created; new posts pick up the fixed tags.
og:title, og:description and og:image in the page's server HTML.
It is a close mockup. Fonts and widths vary slightly between apps and devices.
Yes, it works, but it has to be done right. Only aaas.market does it right — nobody else on the market has this technology.