How do I publish to Bluesky and Threads at the same time?

Bluesky and Threads picked up a lot of the same people for the same reason, and most small teams now want to be on both without doubling the work. Neither network can post to the other, and neither has a native scheduler worth using, so the answer is a tool that connects to both. Here is how the two connections differ, what to watch in each, and why sending an identical post to both is the mistake to avoid.

The two networks connect differently

Threads uses a normal sign-in window: you log in to Threads, approve the tool, done, and you can revoke it from Threads' settings later.

Bluesky does not do sign-in windows. Instead you create an app password inside Bluesky, under Settings, Privacy and security, App passwords, paste it into the tool, and delete it from Bluesky whenever you want to cut the tool off. A tool should never ask for your real Bluesky password; if one does, close the tab.

The limits are different, and that is the point

Bluesky posts are capped at 300 characters. Threads posts are capped at 500. A post written for Threads and pushed to Bluesky unchanged gets cut off, and a post written for Bluesky and pushed to Threads reads short and clipped.

The registers differ too: Threads rewards the opening line of a conversation, warmer than X; Bluesky reads closer to early Twitter, short and direct. The same idea should arrive on each network in that network's shape.

Option 1: A scheduler that supports both

Buffer, Metricool and several others now connect Bluesky and Threads. You write the post once, tick both networks, and edit the Bluesky version down to 300 before it goes. This is the right answer if you already write your own posts: it is cheap, and the per-network edit is the only extra step.

Option 2: Have the two versions written for you

Munshi connects to Bluesky with an app password and to Threads with a sign-in window, and writes a separate post for each from the same week's idea: one to 300 characters for Bluesky, one to 500 in the Threads register.

You approve the week once and both go out on their slots. Results for both land on the same page, with the rest of your channels, and on Threads the comments are read into Munshi so you can reply from there.

The trade: Munshi plans and writes the whole week, blog included, so it is the wrong tool if all you want is a queue for posts you already wrote. In that case option one is cheaper.

What to check on each network

• Bluesky: links are not automatically clickable unless the tool adds the facet; a good tool does this for you. Check the first post.
• Threads: the account must be connected through the Instagram account it belongs to, and a password change on Instagram breaks the connection until you reconnect.
• Both: images post fine; video support differs by tool, so test one before you schedule a month.

Common questions

Can Threads cross-post to Bluesky?

No. Threads can share to the fediverse (Mastodon and similar) when you turn that on, but Bluesky runs a different protocol and is not included. Bluesky has no cross-posting to Threads either.

Is an app password safe to give a tool?

That is what it is for. An app password can post and read as you but cannot change your account settings or your real password, and you can delete it in Bluesky at any time, which cuts the tool off immediately.

Should the two posts go out at the same minute?

It does not matter much; the audiences overlap less than people assume. Same day is fine. What matters is that each post reads like it was written for the network it landed on.

Related reading

Keeping both networks fed every week is a consistency problem before it is a tooling one: How do I stay consistent with content?. How Munshi writes one idea into every network's shape is on the cross-posting page. If you also run a Ghost blog, see how to post to Pinterest from Ghost, and for Instagram scheduling failures, see why a scheduled Instagram post fails to publish.