How to Cross-Post from X to Threads, Bluesky, and Mastodon

Step by step

1. 1

   Open the cross-post composer in SocialKit

   From your dashboard, navigate to the cross-post or create area. As of June 2026 this is where SocialKit's multi-network composer lives — you will see a list of your connected accounts so you can pick which ones receive this post.

   Tip: If you only want to target the four microblog networks, tick X, Threads, Bluesky, and Mastodon and leave your other accounts unchecked. You can save that combination as a group for next time.

2. 2

   Select X, Threads, Bluesky, and Mastodon as destinations

   Check all four networks in the destination picker. SocialKit will open a separate caption panel for each so you can tailor the copy — but the shared text from step 3 pre-fills each one, so tailoring is optional rather than required.

3. 3

   Write your base post text

   Type your core message in the shared composer. As of June 2026, the standard character limits are: X 280 characters (higher for X Premium subscribers), Threads 500 characters, Bluesky 300 graphemes, and Mastodon 500 characters on most instances (though individual instances can raise or lower that cap). SocialKit shows a per-network character count as you type so you can see at a glance which variants need trimming.

   Tip: Start with the tightest limit — Bluesky's 300 graphemes — so the base copy fits everywhere, then expand the Threads and Mastodon variants with extra context if you want.

4. 4

   Customize per-network variants where the limits or audience differ

   Switch to each network's individual tab and adjust the copy. Common tweaks: shorten the X variant if it exceeds 280 characters; expand the Threads or Mastodon variant with a second paragraph; add relevant hashtags to Mastodon where discovery relies on them more heavily than on the other three. None of this is required — if the base text fits all four limits, you can skip this step entirely.

   Tip: Hashtags behave differently across these networks as of June 2026: Bluesky does not surface posts by hashtag the same way Mastodon does; X and Threads treat them as optional discoverability signals rather than primary discovery tools. Tailor hashtag use per network rather than copying them verbatim across all four.

5. 5

   Add media and check how link previews will render

   If your post includes an image, video, or a URL whose preview card you want to control, add media from the composer. Be aware that link-preview behavior varies: as of June 2026, X generates its own link card from Open Graph tags, Bluesky renders a card from the AT Protocol's embed spec, and Threads and Mastodon render cards based on OG tags — but rendering can differ by instance on Mastodon. Check the per-network preview in SocialKit before scheduling so you know what the card will look like.

6. 6

   Set the publish time or add to your queue

   Pick a date and time, or drop the post into your next available queue slot. All four networks will receive the post simultaneously at that moment. Use the SocialKit best-time data as a starting point — see the linked best-time pages below — but treat the figures as audience-specific estimates rather than guarantees.

   Tip: The four microblog audiences do not always peak at the same hour. If you have analytics showing different windows per network, consider scheduling two versions — one for X and Threads, another offset by an hour for Bluesky and Mastodon — rather than one simultaneous blast.

7. 7

   Publish or schedule, then verify delivery on each network

   Hit schedule (or publish now). After the post goes live, spot-check each platform directly: confirm the text, link card, and any media rendered as expected. As of June 2026, all four of these networks support direct API publishing for text and image posts through SocialKit, so you should not need a manual mobile step for standard posts — but check after your first cross-post to confirm everything went through on your specific account configuration.

Best practices

• Write to Bluesky's 300-grapheme limit first — it is the tightest of the four, and drafting to the tightest constraint means you have a version that fits everywhere before you expand.
• Do not paste hashtags blindly across all four networks. Mastodon discovery is hashtag-driven; Bluesky is more follow-graph-driven as of June 2026; X and Threads treat them as secondary signals. Match your hashtag strategy to how each network actually surfaces content.
• Keep the core message identical across all four, but let the opening sentence vary slightly — some Mastodon instances have local timelines where a slightly rephrased opening reads less like syndicated content and more like a genuine post.
• Use SocialKit's per-network preview before scheduling to catch link-card formatting issues. A broken OG image on one network will look unprofessional even if the text is perfect.
• After your first cross-post, pull analytics from each network separately. If one consistently underperforms, it may signal that your audience there prefers a different posting time, content style, or frequency — cross-posting is a starting point, not a permanent equalizer.
• Reconnect any account that shows a connection warning before scheduling — Bluesky app passwords and Mastodon OAuth tokens can expire or be invalidated, and a failed post to one destination does not halt the others.

Good to know

Do it in SocialKit