Sharing to several networks at once

Sharing to several networks at once

Write a post once and it can go out to every network you have connected. There is no need to rewrite it for each one.

Two ways to share

1. 01Share on publishTick the networks while writing the post and it goes out the moment you publish.
2. 02Share laterOpen a published post, choose Share, and pick the networks. You can do this as often as you like.

Sharing on publish covers most cases. Sharing later is useful when a post got little response and you want to run it again at a different time of day.

Which networks can share on publish

Five networks appear in the tick list:

• X (Twitter)
• Facebook
• Instagram
• Telegram
• Bluesky

LINE and LinkedIn cannot share on publish. You can still connect them, so use Share later for LinkedIn.

What each network does with your post

The same text is treated differently depending on the network. Knowing this in advance avoids posts being cut in awkward places.

If Instagram is selected and there is no image, that one share fails. The others still succeed.

Different wording for X

X allows less text, so the body will be cut if pushed as is. The posting screen has a separate field for the wording used on X, and what you put there is used only for X. Leave it empty and the opening of the body is used instead.

For blogs you can also choose the language used when sharing to social, separately from the body. Use it to take a Japanese article to an English-speaking audience — see Writing a blog.

Reading the results

After publishing, each network shows success or failure. A failure on one network does not roll back the others. Use Share later to retry just the ones that failed.

About undoing a share

Once something has gone out to a network, it cannot be recalled from here. Delete it in that network's own app or website. Deleting the post on this service does not remove what is already on the networks.

If you want to check before anything goes out, save the post as Only me first, settle the content, then move it to Public. That avoids unintended automatic sharing.