Long social posts usually fail after the draft is good.
The fix is not to cut the whole thing down to the smallest platform. I split the post into a thread, keep each part useful on its own, then schedule or copy the result from there.
Use TheBlue.social's thread splitter when you have one long draft and need clean pieces for Bluesky, X, Threads, LinkedIn, Mastodon, Instagram, or Pinterest.
Start with the platform that has the tightest limit
If the same idea is going to several platforms, start with the strictest one.
For most cross-posting work, that means X or Bluesky.
X's character-counting docs say posts can contain up to 280 characters, but the count is weighted. Emojis, URLs, and some Unicode characters do not all behave like plain Latin text. X also counts every detected URL as 23 characters.
Bluesky is usually the next tight check. Its post model uses rich text facets for links, mentions, and tags, with byte ranges attached to plain text. The official Bluesky rich text guide is worth reading if you are building tooling around links or mentions, because the visible text and the decorated link target are separate.
My simple rule: split for the smallest realistic limit first, then adapt upward.
If a part fits X and Bluesky, it usually fits Threads and Mastodon. LinkedIn can take much longer posts, but that does not mean the LinkedIn version should be one giant paragraph.
Split by ideas, not by raw length
A bad split cuts wherever the counter hits zero.
That gives you thread parts like this:
...which means the launch page needs three checks before
Then the next post starts mid-thought.
I prefer this structure:
1. The problem
2. The rule or decision
3. The example
4. The practical next step
Each post should have a reason to exist. If someone sees only part three in the feed, it should still make sense.
This is the part a splitter helps with. Paste the draft into the tool, pick the platform limit, then review the suggested breaks. I still edit the pieces. The tool removes the counting work; it does not make the editorial call for me.
Keep links out of the middle
Links are where thread splitting gets messy.
On X, URLs are counted as 23 characters no matter how long they are, according to the same official character-counting docs. Mastodon's posting docs say links also count as 23 characters and recommend not using link shorteners just to save space.
That means shortening the URL is usually the wrong fix. It may not save characters, and it can make the post look worse.
I usually put the link in one of three places:
- The first post, if the whole thread is pointing to one page
- The last post, if the thread needs context first
- A reply after the main thread, if I want the posts to read cleanly
For product posts, I usually pick the first or last option. If the post is a mini-guide, the last post often works better.
For example:
6/6
If you already have the draft, run it through the thread splitter before scheduling:
https://theblue.social/tools/thread-splitter
Nothing clever. Clear destination, no chopped sentence.
Do not number too early
I add numbering after the split feels right.
If I start with 1/7, 2/7, and 3/7, I get annoyed when the edit turns seven parts into five. It also makes each part a little longer before I know whether the text fits.
My order:
- Split the draft
- Rewrite the awkward breaks
- Remove weak parts
- Add numbering only if the thread needs it
- Preview the final version
Some threads need numbering. Some do not. A launch announcement often benefits from it because people know there is more to read. A casual thought can feel better without labels.
Adapt the long-platform versions
Thread splitting is not only for short platforms.
LinkedIn's help page says posts have a 3,000-character limit. That gives you room, but a long LinkedIn post still needs readable breaks. I often turn the same source draft into a tighter thread for Bluesky/X and a longer post for LinkedIn.
Threads is different again. Meta's Threads API post docs state that text posts are limited to 500 characters. That is roomier than X or Bluesky, but still short enough that one long paragraph can become hard to scan.
Pinterest has its own shape. The official Pin specs list a 100-character title max and descriptions up to 800 characters. For Pinterest, I write a summary, choose an image, and send people to the link.
Same source idea, different output:
Bluesky/X:
Short thread with one idea per post.
Threads/Mastodon:
Fewer parts, slightly more context per part.
LinkedIn:
One post with line breaks and a stronger opening.
Pinterest:
Title, description, image, and link.
The draft is shared. The format is not.
My quick thread-splitting workflow
This is the workflow I use before a post goes into the scheduler:
- Write the full draft without counting
- Paste it into the thread splitter
- Start with the tight platform limit
- Rewrite any part that starts or ends mid-thought
- Move the link to the first or last post
- Add numbering only after the structure is stable
- Check the final draft in the multi-platform post previewer
- Schedule the cleaned-up thread in TheBlue.social
The important part is the order. I do not want to think about counters while writing. I want to think about counters while editing.
Example split
Original draft:
I used to write one launch post and then trim it seven different ways. That always made the strongest version worse. Now I write the complete thought first, split it into platform-sized pieces, then adapt the output for each network. The original stays useful, the shorter versions stay readable, and I do not have to pretend every platform wants the same format.
Thread version:
I used to write one launch post and then trim it seven different ways.
That always made the strongest version worse.
Now I write the complete thought first, split it into platform-sized pieces, then adapt the output for each network.
The original stays useful, the shorter versions stay readable, and I do not have to pretend every platform wants the same format.
That split is not complicated. It just keeps the argument intact.
Review the thread as a reader
After the split, I read the thread from top to bottom without looking at the original draft.
That catches different problems than a character counter.
I check:
- Does the first post say enough for someone to keep reading?
- Does each next post answer the natural follow-up question?
- Did I repeat the same setup sentence in three different ways?
- Is the link attached to the part where the reader is ready for it?
- Would the thread still make sense if someone saw post three first?
The last check matters because social feeds do not always show people the start of the thread. A reply, repost, quote, or search result can drop someone into the middle. I want each part to have context without turning every post into a recap.
I also remove the weak bridge posts.
These usually look useful while drafting:
Here is why that matters.
There is one more thing.
Now let us look at the next part.
Most of the time, they can go. A good next post already shows why it matters.
For cross-platform threads, I do one more pass for platform language. I do not write "tweet" in a Bluesky post unless I am talking about X. I do not say "link in bio" on a platform where the link is right in the post. Small wording mismatches make recycled posts feel recycled.
When the thread is for a launch, I save the strongest version before cutting anything. That original draft is useful later for the blog, newsletter, LinkedIn, or a product changelog. The short thread should come from the long draft. It should not destroy it.
I keep a small note next to the final thread with the original hook, the final link, and the platform-specific versions I changed. That sounds fussy, but it helps when I need to reuse the campaign next week. I can see which line worked as the short hook, which version was written for LinkedIn, and which one was only meant for a tight X or Bluesky thread.
That also makes scheduling less fragile. If I spot a typo after splitting, I can fix the shared source and then check the affected platform versions instead of hunting through seven unrelated drafts.
The thread splitter is useful because it gets the mechanical part out of the way. After that, the writing job is the same as always. Each part still needs to be worth reading.
Last updated: June 19, 2026