How to write an X thread people actually finish

You have seen the pattern. A thread opens with "I spent 6 months studying this. Here's what I learned 🧵", gets a wave of likes on the first post, and then the engagement falls off a cliff at post three. The hook did its job. The thread did not.

A thread that gets finished is a writing problem, not a growth hack. This guide walks through how to structure one, how to write a hook you can actually pay off, how to pace 280-character posts so people keep scrolling, and how to prepare and schedule the thing without losing a line to the character limit.

Why most threads get abandoned

Before the fixes, the failure modes. Nearly every unfinished thread does at least one of these:

• The hook promises more than the body delivers. "Everything I know about pricing" turns out to be four generic tips.
• Posts do not stand alone. Someone sees post 5 in their feed, understands nothing, and scrolls on.
• Padding. Eight posts that should have been four. Readers feel it.
• No visible structure. Without numbers or a clear sequence, the reader cannot tell how much is left, so they leave.
• The payoff is in the last post. By the time they get there, nobody is left.

Each fix below targets one of these.

Step 1: Decide the one thing a reader should walk away with

Write a single sentence: "After this thread, the reader will know how to ___." If you cannot fill the blank, you do not have a thread yet. You have notes.

This sentence is not your hook. It is the test you hold every post against. If a post does not serve it, cut the post.

Step 2: Outline before you write a word

A thread that reads cleanly almost always has this skeleton:

1. Hook (post 1): the promise.
2. Setup (post 2): why this matters or what you tried. One post, not three.
3. Body (posts 3 to 7): one idea per post, in a deliberate order.
4. Recap (second-to-last): the body in three lines.
5. Close (last): what to do next, and your link if you have one.

Five to nine posts covers most topics. If your outline runs past twelve, you have two threads or a blog post.

Step 3: Write a hook you can pay off

The hook has two jobs: stop the scroll, and set an expectation the thread will meet. Most people over-index on the first.

Patterns that work when they are true:

• Specific outcome. "We cut our churn in half in one quarter. Here is exactly what we changed." Specific beats big.
• Contrarian but defensible. "Most 'best time to post' charts are useless. Here is how to find your own." Then prove it.
• Process reveal. "Here is the exact checklist I run before scheduling any thread."
• Numbered promise. "7 things I wish I knew before launching on Product Hunt." The number sets a length expectation, which helps completion.

Patterns to avoid:

• A hook that is only "A thread 🧵". That is a label, not a reason.
• Vague superlatives ("the ultimate guide", "everything you need").
• A question the reader can answer with "no" and leave.
• Any claim you cannot back up in post two.

Write the hook last if you have to. It is easier to promise what you have already written.

Step 4: Pace each post for 280 characters

280 characters is roughly two short sentences or one medium one with a line break. The limit is a feature: it forces one idea per post.

Rules of thumb:

• One idea per post. If a post has "and also", split it.
• First line carries the post. Readers see the first line in the feed. Make it the point, not the setup.
• Use line breaks. A 270-character wall reads slower than two 120-character chunks with air between them.
• Vary length. A run of five maxed-out posts is exhausting. Follow a dense post with a short one.
• Make posts stand alone. Assume someone lands on post 6 cold. Can they get something from it? If not, add two words of context.
• End some posts with a pull, not all. "But that was not the real problem." works once or twice. Every post ending in a cliffhanger feels like a sales funnel.
• Number them if the thread is longer than five. "3/" or "3/8" tells the reader how much is left, which keeps them reading.

If you have X Premium, you can write posts up to 4,000 characters. That is a different format: a long post reads like an article, a thread reads like a sequence. Use a thread when the ideas benefit from being separated and ordered. Use a long post when they do not.

Step 5: Use images where they replace text

A screenshot, a chart or a before-and-after often saves two posts of explanation. Put images in the body where the idea is visual, not in the hook for decoration.

Keep image text legible on a phone. If the reader has to zoom, they will not. Add alt text; it is good practice and it helps people who cannot see the image.

Step 6: Land the ending

Two posts, not one.

The recap. Restate the body in three or four lines. People who skimmed get the value; people who read get the reinforcement. This is the post that gets bookmarked.

The close. Tell the reader what to do next: follow for more on this topic, reply with their experience, read the longer version. Put your link here, or in a reply to the first post.

Many people believe links in the body of a post reduce its reach. Whether that applies to you is something only your own numbers can show, so test it on your own account: run the same thread with the link in the last post versus in a reply, and compare.

Step 7: Edit, then split

Write the whole thing as one document first. Then cut.

• Delete any post that does not serve the sentence from Step 1.
• Read it aloud. Anywhere you stumble, the reader will too.
• Cut filler openers: "So,", "Basically,", "Here's the thing:".
• Replace adjectives with specifics. "Big improvement" becomes "from 12 to 4 support tickets a week" if you have the number. If you do not, say what changed, not how impressive it was.

Then split it into posts. Doing this by hand means counting characters in your head and discovering post 4 is 291 characters at 11 p.m. A free thread splitter takes a long draft, breaks it into parts that fit the 280-character limit, and shows the count for each one so you can rebalance. It also helps if you cross-post: Bluesky allows 300 characters per post, Mastodon 500 by default and Threads 500, so the same draft splits differently per network.

Step 8: Post or schedule it

You have two main options.

Post it live from X. The X composer lets you add posts to a thread with the plus button and publish them together. This is fine if you are at your desk at the right time and want to reply as the comments come in.

Schedule it with a tool. X's own web composer can schedule single posts, but as of this writing, scheduling a complete thread needs a third-party tool. Several schedulers support threads: Typefully is built around them, Postfree supports multi-part threads on X, Bluesky, Mastodon and Threads from one composer, and others have added it too. Check that the tool publishes parts as replies to each other, not as separate posts, and that it tells you clearly if a part fails midway.

Whichever you pick, be around for the first hour after it goes out. Replies to early comments are where threads grow.

A worked skeleton

Here is the shape of an eight-post thread on, say, pricing experiments:

1. Hook: "We ran 4 pricing tests this year. 3 failed. The one that worked was the one we almost skipped. Here is all four, with numbers."
2. Setup: what the pricing looked like before, in two lines.
3. Test 1: what, result, one-line lesson.
4. Test 2: same.
5. Test 3: same.
6. Test 4 (the winner): what, result, why it worked.
7. Recap: the four lessons as four short lines.
8. Close: "Full write-up with the dashboards is in the reply. If you are running pricing tests, reply with yours; I read every one."

Every post stands alone, the number in the hook sets the length, and the payoff arrives in post 6, not post 8.

FAQ

How long should an X thread be?

Long enough to deliver the promise in the hook and no longer. Five to nine posts covers most topics. If your outline passes twelve, split it into two threads or write a long post instead.

Should I number the posts?

If the thread is longer than about five posts, yes. "4/9" tells the reader how much is left and makes individual posts understandable when they show up out of context.

Where should the link go?

The last post or a reply to the first post are the two common choices. Opinions differ on which performs better, so run both versions on your own account and compare.

Can I schedule an X thread for free?

Some schedulers include threads on their free plan or trial. Postfree, for example, supports multi-part threads on every plan, including its free plan (no credit card). Check the vendor's free tier before assuming; some reserve threads for paid plans.

Try it

Pick one idea you have explained to a colleague more than twice. Write the one-sentence takeaway, outline eight posts, draft it as a document, and run it through a thread splitter to see the counts. If you want to schedule it across X, Bluesky, Mastodon and Threads from one place, sign up for Postfree's free plan at https://postfree.app/signup (no credit card).