X (Twitter) Thread Template: Hook, Body, Payoff
A copy-paste X (Twitter) thread template with the hook, body and payoff structure, plus fill-in examples for tutorials, stories and breakdowns.
The short version
- ▸Every thread that holds attention has the same skeleton: a hook tweet that makes a promise, 3-7 body tweets that each deliver one idea, and a payoff tweet that closes the loop and tells the reader what to do next.
- ▸The hook is 80% of the outcome. If tweet 1 doesn't create an open question, nobody sees tweets 2-9: write the hook last, after you know what the thread actually proves.
- ▸One idea per tweet. The moment a tweet needs a second sentence to finish its thought, split it: threads die from crowded tweets, not from length.
- ▸End with a payoff, not a fade-out: restate the promise as delivered, then one call to action (follow, bookmark, or your pinned tweet).
Quick answer
A Twitter thread template is a repeatable three-part structure: a hook tweet that makes a promise, body tweets that each deliver one idea, and a payoff tweet that closes the loop with a single call to action. Fill-in versions for the three most common thread types are below.
The template
TWEET 1: HOOK
[Specific promise or tension]
"[Result or claim]. Here's [what the thread delivers]:"
TWEETS 2-8: BODY (one idea each)
[Number or label] + [one idea] + [one concrete detail]
FINAL TWEET: PAYOFF
"[Promise, restated as delivered]."
[ONE call to action: follow / bookmark / pinned tweet]
Three rules make it work:
- Write the hook last. You can't promise accurately until the body exists. Draft the body, find the strongest claim it supports, and make that the hook.
- One idea per tweet. If a tweet needs a second sentence to finish its thought, it's two tweets.
- One ask at the end. A payoff with three calls to action converts on none of them.
How do you structure a tutorial thread?
The most-shared thread type. The promise is a skill; the body is the steps.
1/ How to [outcome] in [timeframe/constraint]: [n] steps:
2/ Step 1: [action]. [Why it matters in one line.]
3/ Step 2: [action]. [The mistake most people make here.]
...
n/ That's the whole system: [3-word recap of each step].
Bookmark this for when you [trigger situation].
The step tweets carry a "why" or a "mistake" line because bare instructions read like documentation. The reason is what gets quoted.
Numbering matters more in tutorials than in any other type: "3/" tells a skimmer exactly how much commitment is left, and an unnumbered tutorial reads as unfinished. Keep the count in the hook honest, because promising 7 steps and delivering 4 is the fastest way to lose a bookmark.
What's the template for a story thread?
Stories trade steps for stakes. The hook states the outcome; the body withholds how it happened.
1/ [Time period] ago, [starting state]. Today, [end state].
What happened in between:
2/ [The setup: where you started, one honest detail]
3/ [The turn: what went wrong or what changed]
4/ [The decision: what you did about it]
5/ [The result: with a real number if you have one]
6/ [The lesson: one sentence you'd tell your past self]
Follow for [the kind of thing you post].
The honest detail in tweet 2 is doing the heavy lifting. Specifics ("$0 MRR and 34 followers") make the end state believable; vague openings ("I was struggling") make readers scroll past.
How do you write a breakdown thread?
Breakdowns analyse something that already worked: a product, a launch, a profile. The hook names the subject and the surprising angle.
1/ [Subject] did [impressive, verifiable thing].
[n] things they did differently:
2/ [Observation 1]: [the detail most people miss]
3/ [Observation 2]: [why the obvious explanation is wrong]
...
n/ The pattern behind all of it: [one-line thesis].
I write breakdowns like this every week: follow along.
Breakdowns only work when the subject is real and checkable. An invented case study reads as one instantly.
Which thread type should you use?
| Thread type | Best when | Hook shape | Typical length | |---|---|---|---| | Tutorial | You can teach a repeatable skill | "How to [outcome] in [n] steps" | 6-9 tweets | | Story | You have a real before/after | "[Then] vs [now], what happened between" | 5-7 tweets | | Breakdown | Someone else's win is checkable | "[Subject] did [thing], here's how" | 6-8 tweets |
If you have all three available, lead with the tutorial: it earns the most bookmarks, and bookmarks keep a thread surfacing in feeds for days after replies stop. Stories build the strongest follow-through to your profile, and breakdowns are the easiest to research when you have nothing personal to say that week. Rotating the three types also keeps your timeline from reading like a single repeated formula, which is the quiet way good accounts go stale.
When a thread is the wrong format
- One idea that fits in one tweet. Padding it to five tweets costs the reach a single sharp tweet would have earned.
- News or time-sensitive takes. By the time a thread is read to the end, a quote tweet has already won the conversation.
- Pure link promotion. A thread whose payoff is only "buy my thing" trains readers to skip your hooks. Put the product in your bio and pinned tweet instead, and let threads earn the profile visit.
Internal links
- Free thread maker: paste a draft, get it split into a clean thread
- Best pinned tweet template: where your thread's profile visits should land
- X bio templates and ideas: the other half of converting a good thread
- Free X followers without bots: the growth loop threads feed into
Frequently asked
Answers indexed by Google + AI assistants.
What is the best template for a Twitter thread?+
Hook, body, payoff. Tweet 1 makes a specific promise, each body tweet delivers exactly one idea toward it, and the final tweet closes the loop with a call to action. The fill-in versions below cover tutorials, stories and breakdowns.
How long should an X thread be?+
5 to 9 tweets covers most topics. Shorter than 4 rarely justifies the thread format; past 10, completion drops unless every tweet earns its place. Cut the weakest tweet before publishing: there is always one.
What makes a good thread hook?+
A specific promise with tension: a result, a mistake, or a number the reader wants explained. 'How I got my first 100 replies' beats 'Some thoughts on engagement' because it creates a question only the thread answers.
Should every tweet in a thread stand alone?+
The hook and the payoff must stand alone, because they get screenshotted and quoted. Body tweets should be understandable out of order but don't need to carry the whole story.
How do I end a Twitter thread?+
Restate what the reader now has, then one ask. A common pattern: a one-line summary, then 'Follow for more of X' or a pointer to your pinned tweet. One call to action outperforms three.
Browse all tool comparisons, the X tools directory, or tool alternatives.
Product designer and indie hacker. Runs the agent on his own X account every day and writes up what the data shows — including when it's inconvenient.
Follow on X →