50 Hook Examples for Threads (Sorted by Reaction)
Swipe 50 thread hook examples, sorted by reaction type. Includes a repeatable how to write a hook process and a test plan for winning lines.
ThreadMaster Team · About the founder · 8 min read
A lot of “viral hooks” fail because they’re built for everyone. The fix is simpler: write hooks that aim at one reaction first, then earn the rest.
This is a swipe file for how to write a hook for Threads. You’ll get 50 fill-in-the-blank hook examples for threads, grouped by the reaction they trigger. You’ll also get a practical workflow to test them with the same topic so you can pick winners.
If you want a framework for selecting between options, use Thread Hook Lab: Write 20 Variants, Pick 1 Winner.
How to write a hook: pick the reaction, then fill the template (10 minutes)
Before you touch wording, choose one reaction target.
Use this quick rule:
- If you want replies, pick a question or warning.
- If you want saves, pick a confession, list promise, or before/after.
- If you want shares, pick a contrarian or specific number.
Then run the 3-step fill process:
- Choose a template from the reaction group.
- Fill the bracket with a real detail.
- Keep the first line under 100 characters.
Worked example (2 minutes):
- Template: “I stopped [doing X] after [Y]. Here’s what changed: [Z].”
- Fill: “I stopped rewriting intros after 12 revisions. Here’s what changed: my threads got saved.”
- Output: “I stopped rewriting intros after 12 revisions. Here’s what changed: my threads got saved.”
Reaction Type 1: Curiosity gap hooks (9 examples)
Curiosity gaps tease a payoff without giving it away. They work when the reader already cares about the topic.
“I thought [X] mattered. It didn’t—until I tried [Y].”
“The reason your [topic] feels hard: you’re doing [mistake].”
“I tracked [metric] for 30 days. The result surprised me.”
“Most people miss this part of [topic]. It’s why [outcome] fails.”
“I used to say [common advice]. Then I saw [evidence].”
“There’s a simple switch for [topic] that nobody mentions.”
“I copied [successful creator] for a week. One thing broke.”
“I changed one line in my threads. My saves jumped.”
“Want better [topic] without more work? Do this instead: [X].”
Reaction Type 2: Contrarian hooks (8 examples)
Contrarian hooks flip a common belief. Keep it grounded. No rage. Just a clean reversal.
“Hot take: [X] isn’t your problem. Your [Y] is.”
“Stop chasing [A]. Start measuring [B].”
“Your [topic] isn’t boring. Your hook is too polite.”
“The best time to post isn’t [belief]. It’s when [condition].”
“You don’t need more ideas. You need fewer [steps].”
“Threads don’t need to be long to work. They need [thing].”
“If your thread gets views but no saves, check [X].”
“Most ‘advice’ about [topic] ignores [real constraint].”
Reaction Type 3: Specific number hooks (8 examples)
Numbers give the reader an anchor. Use numbers that imply proof: counts, days, percentages, and budgets.
“I rewrote my hooks 20 times. The winner was #7.”
“After 14 days of testing, [X] doubled my replies.”
“I spent $0 on [tool]. Still got [result] by doing [X].”
“Here’s my 3-part hook checklist (use it on any topic).”
“One change cut my thread from 2,000 to 900 words.”
“My best thread had 1 clear promise and 0 fluff.”
“I tested 5 intros. Only 1 earned saves.”
“I added one sentence about [thing]. Saves went up 38%.”
Reaction Type 4: Confession hooks (7 examples)
Confessions lower the reader’s guard. Make them specific, not self-pity.
“I used to think [X]. Then I embarrassed myself with [Y].”
“I missed the basics for months: my hooks lacked [X].”
“I stole my own advice—and it still didn’t work. Here’s why.”
“I deleted 30 drafts because the hooks didn’t say [thing].”
“My first threads got engagement. My later ones didn’t. Cause: [X].”
“I overcomplicated my hook. It performed worse by 2x.”
“I thought [tool/process] would fix everything. It fixed one part.”
Reaction Type 5: Before/after hooks (8 examples)
Before/after hooks show transformation. The “after” must include a measurable or observable outcome.
“Before: my threads got likes. After: people started saving them.”
“Before I used [X], my hooks blended in. After: they got replies.”
“Before: I guessed. After: I tested 20 hook variants.”
“Before I changed my opening sentence, my CTR was 0. After: 4%.”
“Before: long intros. After: 1 clean promise. Results: [X].”
“Before: ‘thoughts?’ After: ‘here’s the exact template I used.’”
“Before: generic hooks. After: specific details about [topic].”
“Before: I wrote for approval. After: I wrote for saves.”
Reaction Type 6: Warning hooks (5 examples)
Warnings create urgency without sounding like fear-mongering. Use them when the reader is about to waste time.
“Warning: if your hook says [X], you’re training silence.”
“Don’t post a thread until you remove this one mistake: [X].”
“If your intro is [X], expect low saves. Fix it with [Y].”
“Stop doing [Y]. It makes your hook feel like spam.”
“Warning sign: your thread gets replies from beginners only.”
Reaction Type 7: List promise hooks (4 examples)
List promises are reliable because they promise structure. The reader knows what they’ll get.
“Steal my 7-step process for writing [topic] hooks.”
“5 hook examples for [topic]—and when each one works.”
“Here are 9 ways to write social media hooks that earn replies.”
“I’ll show you 3 edits that make your thread sound human.”
Reaction Type 8: Question hooks (9 examples)
Questions pull the reader in. The trick: don’t ask “thoughts?” Ask a precise question they can answer in their head.
“What if your hook is the reason nobody saves your threads?”
“Which one gets you more: views, replies, or saves—right now?”
“Why do you think your [topic] threads stall after day 2?”
“Are you writing a hook for a reader—or for your ego?”
“What would you do if you only had 1 sentence to sell value?”
“Have you tried writing the hook last, then rewriting the first line?”
“What detail would make your thread instantly more believable?”
“If you had to cut your hook by 50%, what would you keep?”
“Which template are you using: curiosity gap, confession, or before/after?”
How to write a hook that actually wins: a 20-variant test plan (12 minutes)
You asked for concrete tactics. Here’s the exact test loop.
Goal: test hook examples for the same topic, same thread outline, different first lines.
- Pick one topic you can post today.
- Write one outline with 5-7 messages.
- Generate 20 hook variants per topic.
- Post 5 variants across 5 days (or schedule if your platform allows it).
- Track: saves + replies, not just views.
Use a tool to keep wording tight. Two practical options:
- ThreadMaster.ai to generate 20 hook variants per topic.
- A text editor search for character count: remove anything that pushes the first line over 100 characters.
Quick instruction for your drafting workflow:
- Copy each hook candidate into a note.
- Append “(first line only)” and enforce the 100-character limit.
- Pick the best 5 by gut feel, then post the rest as A/B tests.
One worked example: turn a weak hook into a reaction-targeted hook (6 minutes)
Start hook (weak):
- “Here are some tips to write better threads.”
Rewrite it using a specific reaction type.
Option A (specific number, save-focused):
- “I tested 20 hooks. The winner earned 3x more saves.”
Option B (question, reply-focused):
- “Which part of your threads do you skip: hook, proof, or CTA?”
Option C (warning, attention-focused):
- “Warning: if your hook is generic, your best content won’t matter.”
Use the one-line rule:
- If the reader can’t tell what they’ll get in the next 10 seconds, rewrite.
Common mistakes (and fast fixes) when writing social media hooks (8 minutes)
- Mistake: the hook is a topic label.
- Fix: fill the bracket with a real detail.
- Mistake: the hook is too long.
- Fix: keep the first line under 100 characters, then move context to message 2.
- Mistake: the hook promises nothing.
- Fix: choose one reaction target and use a matching template (question for replies, confession for saves).
- Mistake: the hook doesn’t match the thread content.
- Fix: write the hook after the thread outline. Then re-check that the first line is true.
If you want the difference between hook and headline wording, read Headlines vs Hooks: What Makes Threads Different.
Short checklist: your next hook in 60 seconds
Use this before you post.
- Reaction target chosen (curiosity, contrarian, number, confession, before/after, warning, list, question).
- Filled bracket with a real detail (not a vague claim).
- First line under 100 characters.
- Matches the next 1–2 messages (no bait-and-switch).
- You have at least 5 alternates ready to test.
If you want to speed up the “5 alternates ready” part, try ThreadMaster to generate 20 hook variants per topic and pick the line that earns the reaction you want.