This is the most common professional cross-posting pair and the one where identical text works least well.
The formats are compatible. The audiences are not, and the gap shows immediately.
The limits
| Platform | Limit | Images | Video |
|---|---|---|---|
| X | 280 | 4 | 512 MB, 140s |
| 3,000 | 20 | 500 MB, 30 min |
LinkedIn allows more than ten times the text and sixty times the video length. Sending it a 280-character post uses a fraction of what the platform is for.
The register problem
A post written for X, published to LinkedIn, reads as clipped and context-free. A post written for LinkedIn, cut to 280 characters, loses the reasoning that made it worth reading.
Concretely:
X rewards compression. One idea, stated directly, no preamble. Threads for anything longer.
LinkedIn rewards context. The same idea plus why it matters and what you’d do about it. The first line is still doing the work, because LinkedIn truncates in the feed, but there’s room behind it.
Hashtag norms differ. A stack of hashtags is normal in some places and reads as spam on LinkedIn.
What to do instead of copying
Write the LinkedIn version first, since it’s the fuller one, then cut the X version out of it. Taking the strongest single claim from the longer post usually produces a better tweet than writing one from scratch.
That’s one thinking step and two drafts, in one composer, rather than two separate pieces of work.
What shouldn’t cross-post at all
Replies and quote posts on X. They depend on context that doesn’t exist on LinkedIn.
LinkedIn’s native formats. PDF Carousels and Articles are LinkedIn-shaped. There’s nothing to send to X.
Anything personal-professional in the LinkedIn register. The tone that works there can read oddly elsewhere, and vice versa.
Use LinkedIn’s formats
Worth saying because cross-posting tends to flatten everything into plain text. LinkedIn supports Posts, Galleries, PDF Carousels and Articles. The PDF Carousel in particular gets people to stop and interact, and it’s the sort of thing a cross-posting workflow quietly stops you from doing if you only ever send text everywhere.
The workflow
- Write the LinkedIn version, up to 3,000 characters
- Cut the sharpest claim from it for X, within 280
- Select both
- Fix mentions per platform, since handles differ
- Pick a time and queue it
Character counts are enforced per platform, so the LinkedIn version can be long without the X version being truncated.
Plan limits
BulkPublish publishes to LinkedIn, X and 13 other networks.
- Channels: Free: 3 (1 per platform). Pro: 30 (2 per platform). Business: 75 (5 per platform).
- Posts: Free: 3/day. Pro: 30/day. Business: unlimited.
X publishing is priced differently from other platforms because its API carries a real per-request cost: pay-as-you-go credits on the free plan, an included monthly budget on paid plans.
The short version
Same idea, two versions. Write LinkedIn first and cut X out of it, because compressing is easier than padding. Drop the hashtags on LinkedIn, don’t cross-post replies, and keep using LinkedIn’s own formats rather than flattening everything into text.