Every team that publishes to more than two networks eventually asks the same question: do we write once and let it travel, or does every platform get its own version? The real answer is a third option that neither camp likes to hear — write once, then decide per network, per post, which parts are allowed to move.

This guide is that decision, made concrete: what stays identical across every destination, what has to change, and the costs you cannot see until the invoice or the algorithm explains them.

The two questions that settle it

Before touching a single draft, answer two questions.

How much do the audiences actually overlap? If your Instagram followers, LinkedIn connections and Facebook page likers are substantially different people, a post that was written for one of them is being shown to two audiences it was not built for. That is not automatically wrong — it just means you are spending someone else's attention budget on content they did not ask for.

Does the platform reward native content? Some networks actively distribute posts better when they use the platform's own conventions — native video rather than a link, native image rather than a screenshot of another platform's post. Others are format-agnostic and treat a link the same either way. The platforms in the first group need a pass before they are published; the second group can usually take the original with a light edit.

Everything below follows from those two answers.

What can stay the same

A surprising amount of a post is platform-independent. These parts travel well:

• The claim. The actual thing you are saying — the finding, the announcement, the opinion. If it is true on LinkedIn it is true on Threads.
• The voice. Your brand's tone does not change per network. A post that needs a different voice per platform is a post with a brand problem, not a distribution problem.
• The facts and figures. The same numbers appear everywhere, or none of them do. Inconsistency between platforms is the fastest way to lose a technical audience.
• The destination URL, including its UTM parameters. One link, one set of campaign tags, so every platform's traffic lands in the same row of your analytics.
• The approval trail. The post went through review once; it does not need a second approval because it appears on a third network.
• The master asset. The highest-resolution original image or longest video edit. Every platform-specific cut derives from it.

If a piece of the post is not on this list, it needs a second look before it is allowed to cross a platform boundary.

What must change

These are the parts that break when they travel unchanged, roughly in order of how often they cause problems.

The first line. LinkedIn truncates aggressively in the feed; X is a character budget; Threads and Mastodon have their own display rules. Write a first line that works at the shortest reasonable length and expand from there, rather than writing for the longest and hoping the cut lands well.

The character budget. Every network has a different caption limit, and they are not close together: Bluesky sits at 300 characters, Mastodon at 500, Threads at 500, X at 280 — with a pricing wrinkle covered below — Tumblr at 4,096, and Instagram and LinkedIn in the thousands. A post written at Instagram's length needs active trimming to survive elsewhere; one written for X may look thin on LinkedIn.

The call to action. "Link in bio" means something on Instagram and nothing on LinkedIn, where the link can live in the post itself. "Read the thread" works on X and reads as an instruction on a network without threading. Rewrite the CTA per platform rather than pasting the same closing line everywhere.

The media crop and format. A 16:9 video is native on YouTube and badly framed on a vertical-first network. A four-image carousel is Instagram's language and gets flattened or ignored elsewhere. A watermark from one platform's editor is visible evidence that the content was made somewhere else, and some networks demote it for exactly that reason.

The hashtag set. Hashtags are functional on Instagram and largely decorative elsewhere. A post carrying five Instagram hashtags into a LinkedIn feed looks automated, not organised. Trim per platform, or drop them entirely where they carry no discovery weight.

The link placement, including its cost. This one has a number attached. X charges per post at a flat rate for a plain text post, but a post containing a link costs several times more. That is not a reason to never link on X — it is a reason to decide each time; a careless multi-link thread adds up faster than it looks in the composer.

The alt text. If you add alt text for accessibility on one platform and skip it on another, the accessible version is the one that looks like an afterthought. Write it once with the master asset and apply it everywhere the platform accepts it.

The economics you cannot see in the composer

Three costs sit behind the "publish to all" button, and none of them are visible until they are.

Automatic cropping. When an image arrives outside the accepted window, platforms crop it themselves — usually through the middle, sometimes through a face or a logo. A tool can pre-fit the image to the destination's window instead, which is a correction worth having, but the crop decision is still being made by someone. Make it yourself first.

Per-platform quotas. Networks throttle publishing volume per account per day: Threads caps posts per rolling day, YouTube allows only a handful of uploads, TikTok allows a larger but still finite number. A calendar that schedules eleven posts across three networks in one day may find the last few refused. Plan around the quota rather than discovering it in a failure notification.

The attention cost. The audience that sees the same post three times in a day is not three times more convinced. If your networks do overlap, staggering identical posts across days — or editing them into genuinely different angles — protects the goodwill that the overlap is spending.

Where cross-posting is the wrong answer

Some situations should end the conversation before it starts.

When the platform's culture rejects it. A link-dump that works as a newsletter promo on LinkedIn will read as low-effort on a community-first network. The audience can tell the difference between a post written for them and a post routed through them.

When the content is platform-native by nature. A poll belongs where polls live. A thread belongs where threading works. A short vertical video with on-screen captions belongs on the networks that distribute it. Forcing a native artefact into a generic text-plus-image post strips the thing that made it work.

When the same audience will see both versions. If a meaningful slice of your followers are on two of your networks, two near-identical posts in one day is a tax on the people who like you most. Stagger, rewrite, or pick one network per idea.

When the post is a screenshot of another platform's post. It works as a deliberate meta-post occasionally and reads as laziness as a habit. If the content is worth sharing, write it fresh for the network you are sharing it on.

A decision table you can reuse

For each post, before publishing to a second network, run this:

• Same claim, different audience, platform is format-agnostic — publish the original with a rewritten first line and CTA.
• Same claim, platform rewards native video or native links — rebuild the media in the platform's format; the copy can stay close.
• Same audience across two networks — one network per idea, or stagger the posts across days with a different angle each time.
• Platform has a hard limit below your draft length — trim to the cut rather than letting the platform cut for you.
• Post depends on a native feature the second network lacks — do not cross-post it; write a companion post instead.

The table takes thirty seconds per post and saves the rework that follows a careless cross-post.

Where PostHub fits, and where it does not

PostHub is built for exactly this workflow. One composer, one draft, then per-platform text overrides so each network gets its own caption without forking the entire post into separate drafts. A live preview shows how the post will render on each destination before it goes out. Media is automatically fitted to each platform's accepted window — the Meta crop range, Dribbble's exact dimensions — rather than arriving at the platform's mercy. The cross-posting guide walks through the mechanics of the one-draft-many-networks model in full.

What PostHub does not do is make the judgement. It cannot tell you that the LinkedIn version should open with the metric rather than the anecdote, that this particular idea is better as one strong post than three adequate ones, or that your Instagram and Facebook followers overlap enough to justify staggering. The overrides hand the decision back to you; the discipline is using them rather than publishing the original everywhere because the button was there.

Key takeaways

• Write once, decide per network: the claim, voice, facts, URL and master asset travel; the first line, CTA, media format, hashtags and alt text do not.
• Know each platform's character budget before you write, and trim deliberately rather than letting the platform cut for you.
• X charges more per post when a link is included — a real cost worth deciding on consciously.
• Watch the invisible ones: automatic cropping, per-platform quotas, and the attention tax on overlapping audiences.
• Cross-posting is the wrong answer for platform-native content, community-first cultures, and posts that depend on a feature the second network lacks.

FAQ

Should I write a different post for every platform?

No. Write the claim once, then adjust the parts that travel badly — first line, CTA, media format, hashtags. Full rewrites per platform rarely justify the time unless the audiences are genuinely disjoint.

Does cross-posting hurt reach?

Not inherently. What hurts is identical posts arriving at overlapping audiences in the same day, or media that is auto-cropped into an unflattering frame. Stagger, reformat, or pick one network per idea when the overlap is real.

How do I keep track of what I have already posted where?

The calendar view shows every scheduled post with its destination platforms, so a post queued for three networks is visible as one item rather than three. The content calendar playbook covers the full planning workflow.