Reuse the idea, not necessarily the post. To cross-post to LinkedIn and Twitter (now X), make a separate version for each network: a short X post or thread, a LinkedIn post with enough context to stand alone, and, for TikTok, a video or photo story with its own caption. A scheduler can deliver those versions; it can't make a pasted handle, link card or crop correct everywhere.
Checked on October 26, 2026 against the networks' own help and developer pages and the tools' own documentation, linked below. Native upload rules, API rules and a scheduling tool's restrictions are not interchangeable. This is a documentation check, not a test of reach or a real-account publishing walkthrough.
What changes per network
| Check | X (Twitter) | TikTok | |
|---|---|---|---|
| Text length | A standard post has 280 weighted characters; eligible paid accounts have longer posts. A thread is several posts, not one long caption. | A feed post has up to 3,000 characters. That is the posting limit, not how much the collapsed feed shows. | Write a caption for the media, not a LinkedIn article pasted beneath it. Native and API fields have different limits; check the publishing route. |
| Links and cards | A URL uses 23 characters through t.co, regardless of its original length. Inspect any card that appears. | Paste the URL and wait for the preview. A clickable link and a preview card are different things. | Don't assume a caption URL becomes a clickable article card. Use a supported profile-link destination where the account is eligible. |
| Hashtags | Hashtags categorize searchable topics; spaces and punctuation break them. | Relevant topic words can be hashtags; keep them readable and in plain letters. | Choose tags relevant to this video or photo story, not a copied block from another network. |
| Mentions | Use the person's actual X @username. | Select the correct person or Page identity; pasted @text isn't proof of a linked mention. | Find the actual TikTok account; the same handle on X can belong to somebody else. |
| Media | Up to four photos; standard-account video limits are much smaller than LinkedIn's. | Up to 20 photos, or a native video; a PDF document is another format, not an X thread. | Build a video or photo post. Text alone isn't a substitute for the visual story. |
Length: count each final version
X's posting help gives the standard 280-character limit. Longer posts are a separate paid feature: X's post-types help lists up to 25,000 characters, while some general help text still mentions 4,000. Don't assume a subscription feature is available in every third-party composer. X's link help says a URL counts as 23 characters; simply counting the visible letters will give the wrong answer.
LinkedIn's sharing help gives 3,000 characters. The feed still hides long text behind “see more,” and line breaks change what fits. Put the point before the expansion, not beneath a copied X thread's numbering. Use the free X counter, LinkedIn counter and LinkedIn previewer on the final versions. These are Flaghand's own counters/previews; the help pages don't publish their counting or pixel-layout algorithms.
TikTok's video Direct Post API
allows 2,200 “UTF-16 runes” in its caption field, post_info.title. Its
photo-post API has a separate
90-unit title and 4,000-unit description, using the same documented UTF-16 terminology. These aren't byte
counts or necessarily visible-letter counts. The official help checked here didn't establish a numeric native-app
caption allowance: don't present the API limits as a universal TikTok composer limit.
Links: change the call to action, not just the URL
A link that works in X or LinkedIn doesn't make the same call to action useful on TikTok. “Read the link below” is poor copy when that surface doesn't provide the same clickable destination. TikTok's profile-link help sets website-link eligibility at 1,000 followers or a Registered Business Account. Don't broaden that to every business account or promise everyone a “link in bio.” The help checked here documents the profile field, not a universal clickable-caption-URL feature.
On LinkedIn, link-sharing help says to wait for the preview image and allows posting the link even if one doesn't load. Its URL troubleshooting help says card titles, descriptions and images come from the destination's oEmbed or Open Graph metadata. Metadata changes can take two days to refresh. Check the card separately on each network; copying your opening sentence doesn't change the site's metadata.
Keep the essential result in the post itself, then give that network's readers an appropriate next step. There is no evidence here for a universal “external links kill reach” rule or a magic first-comment workaround.
Hashtags and mentions: rebuild them
X's hashtag help recommends no more than two hashtags, but that's advice, not a posting limit. LinkedIn's own feed-writing advice suggests a few relevant hashtags and capitalizing each word for readability. Neither is evidence that the same bundle of tags improves performance on TikTok. Keep topic tags intentional, not an automatic footer.
A mention is an identity, not portable text. X's
mention help describes @usernames. LinkedIn's
mention help asks you to choose
the correct profile from suggestions; people can disable mentions. Re-select accounts on the destination network,
and check whether your tool supports that kind of tag. A scheduler may support company tags but not people tags.
If it can't make the intended mention, use the person's plain name rather than silently tagging someone else.
TikTok's mention help
similarly describes searching or selecting the person with @ Mention, subject to their mention settings. Its
Direct Post API recognizes # hashtags and @ mentions in the caption, separated by spaces or newlines. That isn't
a guarantee that a handle copied from a different service identifies the right account.
Media and video: keep a master, export for each destination
Start from an original file you have rights to reuse, not a downloaded social post. Keep an editable master, then check the export against both the network and the route your tool uses. A native app accepting a large file doesn't mean a third-party API accepts it.
- X photos: X Help supports up to four photos, up to 5 MB each, and GIF, JPEG and PNG. An animated GIF has separate upload rules; don't treat it as a still photo.
- X video: X video help lists 140 seconds and 512 MB for accounts without the eligible paid subscription. Paid-account allowances differ. A video that fits LinkedIn can still be too long for a standard X account.
- LinkedIn photos: LinkedIn Help allows up to 20 photos, with a 5 MB upload limit and a suggested 1080 px width. It lists ratios from 3:1 to 4:5 and describes centered cropping outside the permitted ratio. Inspect a multi-photo layout instead of assuming it looks like X's four-image grid.
- LinkedIn video: its native video help lists 75 KB to 5 GB, up to 15 minutes, 256 × 144 to 4096 × 2304, 10–60 fps and aspect ratios 1:2.4 to 2.4:1. The minimum duration is 3 seconds on desktop or 2 seconds in the mobile app. These are organic native-sharing rules, not video-ad specs or a promise about every publishing tool.
- TikTok through the API: its
media-transfer guide recommends
MP4 and H.264, also accepts MOV/WebM and other listed codecs, and specifies 23–60 fps, each video dimension
360–4096 px, and a 4 GB maximum. Photo uploads are JPEG or WebP, up to 20 MB each; the photo-post
reference allows up to 35 images. These are API constraints, not native-app upload specifications.
For Direct Post, check the creator's current
max_video_post_duration_sec: the allowance varies, so don't publish the example's duration as everyone's limit.
For a short clip reused across the three, a vertical master with readable captions is a practical starting point, not a universal required aspect ratio. Check where each feed crops it and where interface controls cover it. Put important text away from the edges, review the first frame and cover, and add alt text to photos where supported. Don't carry burned-in “swipe up” or “link below” instructions onto a destination where they don't work.
TikTok's posting help describes adding
sounds and effects in the app. The documented video Direct Post request doesn't provide a native sound picker or
effect-selection field; photo Direct Post's auto_add_music adds recommended music, not a chosen track ID.
If the post depends on an editing feature the tool can't express, use an explicit phone handoff. TikTok's
Upload Content workflow
delivers media to an inbox notification so the owner can finish and post in TikTok. It isn't publication.
Availability of a TikTok sound also doesn't establish rights to reuse it on X or LinkedIn.
Why a straight copy can underperform
The mismatch is concrete before any algorithm is involved:
- A LinkedIn explanation can exceed X's post limit; cutting it mechanically can remove the point or the link.
- An X thread pasted into LinkedIn keeps reply numbering but loses the conversation's structure.
- A text-and-link announcement gives TikTok viewers no visual demonstration and may point at an unusable link.
- A copied @handle can mention the wrong person, and the same image can crop important words differently.
- “Watch with sound,” “read the thread” and “download the PDF” make sense only when that version supplies the thing.
Those are reasons to adapt, not a measured claim that every duplicate gets penalized. These sources don't establish a universal reach penalty, an optimal hashtag count or a guaranteed lift from rewriting. Read each network's own results separately rather than adding unlike view counts together.
One idea, three versions
Suppose the original idea is: “We made exporting a project faster and easier to understand.”
- X: Lead with the specific change and a short screen clip. Use one post if it fits; make a thread only if the explanation needs distinct parts. Put a real destination link in the version that needs one.
- LinkedIn: Explain the problem, what changed and what another team could learn. Keep the opening useful before “see more.” Attach a screen clip, photos or a document appropriate to that explanation, then inspect the link card if using one.
- TikTok: Show the old friction, then the new export, with legible on-screen text. Write a caption describing what viewers just saw. Choose the account's supported next step, not a copied promise of a clickable caption URL.
Don't invent a percentage improvement for the hook. Reusing one factual brief is the efficiency; the three exports and captions are the publishing work.
Tools that cross-post
These are examples, not a ranking. Check the exact post type, account type and automatic-publish versus handoff support before choosing. No one tool makes every native feature portable.
| Option | Where it fits | What to check |
|---|---|---|
| Buffer | A shared composer with per-network edits; its guide includes X, LinkedIn and TikTok. | Customize copy, media and time per channel. Confirm whether the selected TikTok feature can auto-publish or needs the app. |
| Postiz | A broader publishing tool with X, LinkedIn and TikTok integrations, including API-driven workflows. | Network-specific requirements still apply. Its TikTok direct and upload-to-inbox modes are different outcomes. |
| Typefully | Text-first cross-posting to X and LinkedIn, with separate content per enabled platform. | TikTok isn't in the destinations listed by this API reference; don't choose it here as a three-network video publisher. |
| Flaghand | A desk for people whose own AI agent drafts X and LinkedIn personal-profile posts, with owner approval over the exact snapshot. | Sign-up isn't open yet. TikTok inbox drafts are beta; public Direct Post awaits TikTok's audit, and TikTok scheduling isn't currently offered. |
Flaghand's agent can draft, upload, check and request one approval for the plan. No agent token can approve, schedule or post. The owner approves in Flaghand with a passkey. Limited X read-back is available; LinkedIn read-back isn't. See the agent documentation for that boundary and the TikTok API guide for inbox versus Direct Post. If you need an available all-three auto-publisher today, evaluate the other tools' current capabilities rather than treating Flaghand's beta as a shipped equivalent. Join the Flaghand waitlist.
Before sending the plan
Check the destination account, final text count, selected mentions, links and cards, crop, video length, captions, cover and media rights separately for each version. Name any phone work explicitly. Then review the three versions as one plan, with their actual times and who does each step. A saved draft or an inbox upload is not a published post; afterwards check each network's live link, not just the scheduler's “sent” label.
Sources and verification scope
All checked on October 26, 2026. The linked X Help pages were checked through indexed first-party text where direct retrieval refused access; no bot check was bypassed. TikTok Help's article bodies were also checked through indexed official help text, including translated versions, because direct requests returned a JavaScript shell. LinkedIn Help, TikTok's developer references and the tools' own public documentation were read directly. No real account was connected, no post was approved or published, and no reach experiment was run. Recheck native limits and the chosen tool's supported fields before changing a publishing workflow.