Most threads fail before anyone schedules them. The writing is fine, but the cuts are in the wrong places, the first part gives nothing away, and part five is a stray sentence nobody needed. The scheduling is the easy bit.
This guide is about the planning. We will take one realistic piece of writing and turn it into a thread, then cover the mistakes that show up most and a checklist to run before you queue it. For the mechanics of the composer itself, the Scheduling threads page is the place to start.
A worked example
Say you run a small bakery and you have written 1,300 characters on why your sourdough takes three days. It has an opening claim, four short reasons, and a closing note about ordering by Thursday. You want it on X and Bluesky.
Step 1: find the tightest limit. X allows 280 characters per part and Bluesky 300. When a thread goes to both, every part has to fit the smaller number, so you plan for 280. Planning for the loosest platform and cutting later is how people end up rewriting at midnight.
Step 2: count the ideas, not the characters. You have a claim, four reasons and a close. That is six ideas, and 1,300 characters is already more than four parts of 280 can hold. So six parts, some of them short. Short is fine. A part that holds one idea and 90 characters beats one that holds two ideas crammed to the limit.
Step 3: put the whole text in and let the composer cut it. Paste the draft into part one. When it is over the limit the composer offers a split, and it breaks at paragraph boundaries first. If you want control, type a line containing only --- between ideas. Text on either side of that line never ends up in the same part, so your six ideas stay six parts.
Step 4: read part one on its own. This is the part most people will see, and many will never tap through. It should carry the claim and a reason to continue. “Why our sourdough takes three days (and why we will not rush it)” works. “A thread on bread” does not.
Step 5: number it, or do not. By default the first part is left unnumbered and the count starts at 2, which keeps the opening post clean. Numbering helps most when a reader lands on part four from a quote or a repost and needs to know there is more above it.
Step 6: attach media where it earns its place. One photo of the loaf on part one, perhaps a second on the part about the long rise. Images on every part make a thread feel like a slideshow.
Step 7: schedule it for one time. The whole chain goes out together. See the best time to post on X if you are choosing a slot.
Deciding how many parts
There is no right number, but there are useful bounds.
- Two or three parts suit a point with one supporting example. If it nearly fits in a single post, make it one post.
- Five to eight parts suit a list, a short story or an argument with steps. Most lists and short stories fit comfortably.
- Ten or more only works when each part earns the next tap. If you are padding to reach a round number, cut.
A thread needs at least two parts. Past that, the only test is whether a reader who stops at any part has still got something.
One thread, different platforms
If you send the same thread to several platforms, you can have a version per platform, and a platform with its own parts uses those instead of the shared ones. That matters in two cases.
- Different budgets. X is held to 280, Threads and Mastodon allow 500. A 500-character part on Mastodon needs to become two on X. Writing the X version as the master and sending it everywhere works, but gives the roomier platforms choppier text than they need.
- Different media. Video in a thread part works on Threads only, and Threads takes one file per part where X, Bluesky and Mastodon take up to four images. If a part needs a video, that part belongs in a Threads-only version.
Every selected channel is checked before the thread is queued. A part that is too long for one of them stops the schedule and names the platform and the part number, so you find out now and not at publish time.
Common mistakes
- Cutting by character count alone. A cut mid-sentence reads as a glitch. Cut at ideas.
- Spending part one on a link. The opening part should carry the idea, with the link kept for the last part. On X and Mastodon a link counts as 23 characters however long it is, which is also how the splitter measures it.
- Numbering a thread you later edit by hand. The markers renumber themselves when you add, remove, split or drag parts, so there is no need to retype them. Turn numbering off and your text comes back as you wrote it.
- Scheduling without reading the preview. Read each part as it will appear on each channel before you queue it.
- Treating Bluesky like the others. See the next section.
If it fails halfway
A thread is several publishing requests in a row, so one part can fail while the earlier ones are already live. BulkPublish reports which part failed (“Part 4 failed”) with the reason, and keeps the parts that went out.
On X, Threads and Mastodon, a retry carries on from the failed part, so parts 1 to 3 are not posted again. Bluesky cannot do this. A partly published Bluesky thread is not resumed automatically, and the message tells you to add the remaining parts by hand to avoid duplicates. For a long Bluesky thread, look at it shortly after it publishes.
Before you schedule
- Part one makes sense alone and says what the thread gives the reader
- Each part holds one idea
- Every part is under the tightest limit among your selected channels
- Any part meant for video is going only to Threads
- The link, if there is one, is in the last part
- Numbering is either on for every part you want or off
- You have looked at the preview for each channel
Related reading
- How many characters each platform allows
- Can you schedule tweets on X? and how to schedule a single tweet
- How to schedule Threads posts
- Can you schedule Bluesky posts?
- Bluesky character limit and Mastodon character limit
You can try it on the free plan: start free, connect an account and schedule your first thread.
BulkPublish supports 15 platforms: Facebook, Instagram, TikTok, YouTube, X, Threads, Bluesky, Pinterest, Google Business Profile, LinkedIn, Mastodon, Discord, Telegram, Tumblr and Snapchat. Threads work on X, Threads, Bluesky and Mastodon.
- 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.