How to Write a Twitter Hook That Actually Stops the Scroll

The first line of a tweet does roughly 90% of the work. The rest of the post barely matters if the first line does not earn the read.

This is uncomfortable for most creators because it means the actual writing skill that determines whether your posts perform is concentrated in a single sentence. You can have brilliant content. You can have years of expertise. If your hook is flat, almost nobody will get to see any of it.

This guide is about how to write hooks that actually work in 2026. The patterns that pull expansions, the ones that quietly kill your reach, and what to do when a post you believe in keeps underperforming.

What a Hook Actually Has to Do

Every hook has one job. Make the reader stop scrolling long enough to read the rest of the tweet.

That is it. The hook is not the main idea. It is not the conclusion. It is not even necessarily the most interesting line. It is the line that earns the read.

This distinction matters because most creators write hooks the way they write the rest of their post, polished, considered, focused on accuracy. Good hooks are different. They are designed for a feed-scrolling audience that decides in under a second whether to keep moving or stop.

A reader scrolling X is not reading. They are filtering. The hook either survives the filter or it does not.

The Hook Patterns That Still Work

A few patterns reliably outperform the alternatives in 2026.

The specific claim. Make a concrete, slightly contrarian statement that creates a question the reader needs answered. "Most founders waste 80% of their X effort on the wrong content." Reader thinks, what is the wrong content, and reads on to find out.

The specific number. Lead with a real number that contradicts what the reader probably believes. "Threads under 8 posts outperform threads over 15 by 3x." The number creates curiosity because it is specific enough to feel credible and surprising enough to feel new.

The personal result. Share an outcome you actually achieved and promise to explain how. "I doubled my newsletter signups in 60 days with one X strategy." The reader expands to get the strategy, not the brag.

The dismissed myth. Take a belief everyone repeats and signal that you are about to dismantle it. "Posting at the 'best time' barely matters. Here is what actually does." This works because it promises to update something the reader already thinks they know.

The mistake confession. Lead with a specific mistake you made. "I spent two years building the wrong feature." The reader expands because mistakes are stories, and stories pull reads.

The common thread across all five is specificity. Generic hooks die. Specific hooks live.

The Hooks That Quietly Kill Your Reach

A few patterns that still get written daily and reliably underperform:

Announcement hooks. "I am about to share something important." "Here is a thread on X." "Read this if you are a founder." These signal that a thread is coming without actually saying anything. Most readers scroll past.

Vague universal claims. "Hard work pays off." "Consistency is key." "Success requires sacrifice." These are technically true and emotionally inert. The audience has heard them a thousand times and feels nothing.

Pure hype hooks. "This is the most important thing you will read today." "This changed my life." Big claims with no specificity. Modern audiences are immune to this and treat it as a tell that the content is weak.

Questions that have obvious answers. "Do you want to grow on X?" Yes, that is why they are on X. The question contains no information and asks for a yes the reader will not bother giving.

Hooks that bury the value. "I have been thinking a lot about content strategy lately and wanted to share a few thoughts." By the time the reader gets to the actual point, they have already scrolled.

If your hooks fall into any of these patterns, the content underneath does not matter. The audience never gets there.

How to Write a Hook That Works

The workflow that produces strong hooks is roughly the same regardless of topic.

Write the body of the post first. The full thought, in whatever shape, with the actual idea you want to convey. Do not worry about the hook yet.

Once the body is clean, ask: what is the single most surprising, specific, or contrarian thing inside this post? That is your hook. Lead with it.

Then test the hook against the scroll. Read it as if you were scrolling past it on your phone. Would you stop? If you would, ship it. If you would not, rewrite.

The mistake most creators make is trying to write the hook first, then build the post around it. This produces hooks that are clever but disconnected from the actual content. The hook over-promises and the body under-delivers, which trains your audience to ignore your hooks over time.

Body first. Hook from the body. Always.

Fixing a Hook That Is Killing Your Reach

When a post you believe in underperforms, the hook is almost always why. A few quick diagnostic moves:

Cut the first sentence entirely. Read what is left. Often the second sentence was the real hook all along, and the first sentence was just throat-clearing.

Replace any vague word with a specific one. "A lot" becomes "8 out of 10." "Most people" becomes "the SaaS founders I talk to." "Recently" becomes "last Tuesday." Specificity is the cheapest hook upgrade available.

Make the claim sharper. If your hook says something is "important," replace it with what specifically the consequence is. "Pricing matters" becomes "wrong pricing kills more SaaS startups than wrong product." Same idea, much sharper edge.

Add a number if there is one anywhere in the post. Numbers stop scrolls because they look like data even before the brain reads them.

Most underperforming posts get rescued by one of these four edits. The post was fine. The hook was not.

Hooks From Existing Content

The fastest way to get good at hooks is to stop generating them from scratch.

Almost every piece of long-form content you have already written contains hook material. The strongest sentence in a blog post is usually a tweet hook in disguise. The most-quoted line in your newsletter is a hook. The surprising paragraph in your client memo is a hook.

The work is recognition, not generation. Read your existing material with hook-hunting eyes and you will find more hooks per document than you can use in a month of posting.

Xposto makes this extraction faster by breaking uploaded documents into semantic chunks and generating posts that preserve the strongest specific claims and numbers. Instead of staring at a blank page trying to invent hooks, you are reviewing hooks that already came out of material you wrote. The How to Repurpose Content for Twitter guide goes deeper on the broader workflow.

The Practical First Step

Look at your three lowest-performing posts from the last month. Read just the first line of each.

Now ask, if you were scrolling and that line appeared, would you stop? Be honest. The answer for most underperforming posts is no.

Rewrite the first line of each post using one of the five hook patterns above. Repost the strongest one. Compare the result.

This single edit, treating the first line as the actual job, usually produces noticeable improvement within a week of practice. Hooks are not magic. They are just a skill that most people never deliberately work on, and the gap between accidental hooks and intentional hooks shows up immediately in the numbers.

For the broader content principles around hooks, the How to Grow on X guide covers the fundamentals, and for how hooks specifically work inside threads, the How to Post a Thread on Twitter guide goes into the thread-opening patterns that decide whether a thread gets read at all.

Stop writing posts and hoping the hook works out. Start writing the body, then designing the hook on purpose. Everything downstream improves.