How to write a Threads hook that stops the scroll
The first line decides whether anyone reads the second. Patterns that work on Threads, and a few that quietly don't.
Threads sits in an odd spot: it has Instagram's visual DNA but a text-first, conversational feed closer to X. That combination means hooks that work great on either parent platform can fall flat here, because Threads' audience expects something a little more personal and a little less polished than both.
What works
- A conversational opener, like you're mid-thought. "Okay so this happened today" works on Threads in a way it wouldn't on LinkedIn — the platform's tone is inherently more casual.
- A specific, small observation. Threads rewards posts that feel like a genuine notice-and-share, not a crafted piece of content. "The thing nobody tells you about [specific topic]" works if it's followed by something genuinely specific.
- A question that invites a quick reply. Since replies are a major driver of Threads' distribution, a hook that's easy to respond to in one line tends to get more reach than one that only invites silent agreement.
What quietly doesn't work
- Overly polished, caption-style openers ported from Instagram. What reads as "on brand" on a feed post reads as stiff on Threads.
- X-style hot takes with no room for reply. A definitive, closed statement gets less engagement here than one that leaves an opening for someone to respond.
- Thread-length setup before the point. Threads posts have room to breathe, but burying the actual hook under two sentences of preamble still costs you readers.
A few starting patterns
- "Something I've been thinking about: [specific idea]."
- "Unpopular take, but [specific opinion] — anyone else?"
- "[Small, specific observation]. Is it just me?"
- "Today I learned [specific fact] and I'm still thinking about it."
Why replies matter more here than elsewhere
Because Threads' algorithm weighs reply activity heavily, a hook that invites a one-word or one-line response — not just a like — tends to compound: each reply resurfaces the post, and each resurfacing brings a chance at more replies. Writing your hook with that specifically in mind (what's the easiest, most natural reply someone could leave?) is a genuinely different exercise than writing a hook meant only to be read.
The tone check
Before posting, read your hook and ask if it sounds like something you'd actually say out loud to a friend, casually. If it sounds like copy — even good copy — it's probably tuned for the wrong platform. Threads' audience notices, and polished-but-impersonal hooks tend to underperform here relative to how they'd do on Instagram or LinkedIn.