Bluesky · Image size

Bluesky Link Card Size

Bluesky link cards commonly use 1200×627. Keep the headline in the center band, then download in your browser—this is not a timeline photo or profile banner.

Last verified 2026-08-25 · Practical Bluesky sizes observed in community UI as of 2026-09-06. Not an official single-pixel mandate—preview on-device before you publish.

Bluesky link card size 1200×627 (~1.91:1) with safe zone
1200×627 wide header. Keep the title in the marked band; edges may trim.

Browser crop · stays on your device

Crop your Bluesky link card

1200 × 627

Add a photo to crop

Upload a story photo or flat graphic—or try the sample—then keep the headline inside the center band before you download.

Size specs

This page is for link embed cards. Timeline photos often target 1200×675; banners are a separate 3:1 upload—export each on purpose.

Publish

Export this for Bluesky upload.

Link card (practical)

Recommended

1200×627 ~1.91:1

Practical ~1.91:1 card for Bluesky URL embeds. Not the 1200×675 post photo or 3000×1000 banner.

Use in tool
Asset Pixels Ratio Notes Action
Link card (practical) Recommended 1200×627 ~1.91:1 Practical ~1.91:1 card for Bluesky URL embeds. Not the 1200×675 post photo or 3000×1000 banner. Use in tool

Link embeds are share cards—posts are timeline photos

When a Bluesky post includes a URL, clients often show a wide ~1200×627 embed card. That card sells the click. Edge-hugging type and tiny captions fail after compression and in multi-column layouts.

Native timeline photos often sit near 1200×675 (16:9). Profile banners are a very wide 3000×1000 strip. Stretching one export into every slot is how soft, clipped cards happen on AT Protocol apps.

Your site’s Open Graph (or equivalent) tags usually feed the embed. Export a clear 1200×627 master, publish it on the destination page, then verify the live card in Bluesky. Expect cache lag when you swap art mid-campaign.

Avatars are circles. Do not force the profile picture into this wide slot. Prefer one subject, high contrast, and a short title that still reads at phone preview size.

Good vs weak crop

Same short banner strip—quiet lower-left for the avatar, subject in the open mid/right band.

Clear ~1.91:1 link card

  • True 1200×627 export
  • Headline in the center band
  • Separate from post and banner

Banner or post forced into embed

  • 3:1 banner squashed into the card
  • Micro type after compression
  • Avatar circle reused as embed art

Before you upload

Tick these off against your crop preview—nothing is saved.

Related surfaces compared

Similar-looking slots often use different ratios—do not reuse one export for all of them.

Link card

1200 × 627

This page. URL embed card.

Post image

1200 × 675

~16:9 timeline photo—separate guide.

Banner

3000 × 1000

3:1 profile header—separate upload.

Profile picture

1000 × 1000

Circular avatar—not a link card.

SurfaceTypical sizeNote
Link card1200 × 627This page. URL embed card.
Post image1200 × 675~16:9 timeline photo—separate guide.
Banner3000 × 10003:1 profile header—separate upload.
Profile picture1000 × 1000Circular avatar—not a link card.

How Bluesky link embeds pick the image

Most embeds follow Open Graph-style meta on the destination page. Cropping here only helps if the live URL serves that file to crawlers.

  • Prefer one clear subject and one short title.
  • Avoid dense paragraphs on the card itself.
  • Re-check after you change the live page.

Link card vs post vs banner

Three artboards. The link card sells a URL. The post photo sits in the timeline. The banner brands the profile header.

File requirements

JPG suits photos; PNG suits flat graphics. Prefer sRGB. Keep weight reasonable for embed fetches.

Link card
1200 × 627 px (~1.91:1)
Post image (different)
1200 × 675 px
Formats
JPG or PNG (sRGB)
Best for
URL embeds on Bluesky

Common mistakes

  • Using the profile banner as the only og:image.
  • Parking the headline on the far edge.
  • Soft phone screenshots as the embed art.
  • Forgetting to update meta tags after swapping the file.

How to use the crop tool

Upload a graphic, choose Link card (1200×627), keep the title inside the center band, then download. Cropping stays in your browser.

  • Judge the result at embed size on a phone.
  • Export post and banner crops separately.
  • Verify the live Bluesky card after publish.

After you download

From this download to a live upload in a few minutes.

  1. 1

    Download the 1200×627 JPG or PNG from the tool.

  2. 2

    Set it as og:image (or your CMS social preview) on the destination URL.

  3. 3

    Share the link on Bluesky and confirm the embed on a phone.

  4. 4

    If caches show old art, wait or use a fresh URL / cache buster per your stack.

Frequently asked questions

What size is a Bluesky link card in 2026?

A practical size is 1200×627 (~1.91:1). Timeline posts often use 1200×675—export them separately.

Is the link card the same as a Bluesky post image?

No. Posts are timeline photos (often ~16:9). Link cards are URL embed art near 1200×627.

Do I upload this in Bluesky settings?

Usually you set it on the destination page (Open Graph / social preview). Bluesky then embeds that URL.

How does this relate to Open Graph 1200×630?

Very close. Many sites ship 1200×630 as the cross-network primary; Bluesky embeds here target 1200×627—see the Open Graph hub for the shared habit.

Can I crop Bluesky link cards in the browser?

Yes. This guide includes an in-browser crop—files stay on your device until you download and publish yourself.