Guide
How to Write an X (Twitter) Thread That Gets Read
Most threads die at post one — not because the content is bad, but because the reader was never given a reason to tap “show more.” A thread is a chain of micro-decisions: every post either buys the next tap or loses the reader. Here's how to structure one that gets read to the end, without the growth-hacker clichés that audiences have learned to scroll past.
The first post is 80% of the work
Your opening post competes in the feed like any standalone post — nobody has committed to a thread yet. It needs a specific promise and a reason to believe it's worth seven taps. Compare “Some thoughts on ad copy 🧵” with “I've written 200+ ad scripts. The ads that converted all shared 4 beats — and the ones that flopped always skipped the same one.” The second names the payoff, quantifies the experience behind it, and opens a loop (which beat gets skipped?). Skip the throat-clearing, skip “a thread on…” — the promise is the hook. Spend as long on this post as on the rest of the thread combined; that ratio matches where the attention is lost.
One idea per post — let it breathe
The unit of a thread is one complete thought per post. Cramming two points into one post to save space does the opposite of what you intend: dense posts read as work, and readers don't do work at 8am on a phone. Short lines. Line breaks between sentences. A post that's one strong sentence is fine — sometimes ideal, because it changes the rhythm. The test for each post: if it appeared alone in the feed, quoted out of context, would it still make sense and still be interesting? Threads get their reach from individual posts being quoted and screenshotted; every post is a potential front door.
Engineer momentum between posts
Readers decide post-by-post whether to continue, so each post needs a forward edge. The mechanics are simple: end posts on mild open loops (“That works — until it doesn't.”), use numbered steps so progress is visible (3/7 tells the reader the investment remaining), and sequence your points so the strongest material isn't all spent in the first two posts. Put your second-best point early, your best point around two-thirds in, and something genuinely useful at the end — readers who finish and feel rewarded are the ones who follow, and the algorithm reads completion as quality.
Concrete beats clever, every time
The threads that get bookmarked share a trait: they contain things a reader can use without you. Real numbers instead of “a lot.” The actual example instead of “for example, imagine…” The exact phrasing instead of “say something like…” Abstract advice (“provide value!”) is unfalsifiable and unmemorable; concrete advice (“write ten hooks, keep one — the good ones show up after post seven”) can be applied this afternoon, which is why it gets saved. Bookmarks and saves are quiet signals, but they're the strongest ones for distribution — write for the reader who's taking notes.
End with one ask, not a menu
The final post is where accumulated goodwill converts, and most writers waste it on a menu: “follow me, RT the first post, check my newsletter, reply with thoughts.” Four asks, zero conversions. Pick one, matched to your goal. Building an audience? “Follow for more like this” plus a one-line recap of what you post about. Driving to a product? One link, one sentence on what's behind it. The recap-post pattern works because it's screenshot-able — a clean summary of the whole thread in one post travels on its own. And skip the engagement-bait sign-offs; audiences in 2026 pattern-match them instantly.
Draft fast, edit ruthlessly, read it on a phone
Write the thread top to bottom without editing — momentum in drafting produces momentum in reading. Then cut 30%: every post survives only if deleting it would break the chain. Then the step almost everyone skips: read it on your phone, formatted, before posting. Threads are consumed on phones, and a paragraph that looked tight on desktop reads as a wall on a 6-inch screen. If drafting is where you stall, ScriptFlow will take a pasted brief or source page and draft the thread — hook, numbered body, closing ask — free, no signup, and you spend your time on the edit, which is where threads are actually made.
Skip the blank page
Paste a brief or a product page into ScriptFlow and get hooks, TikTok scripts, threads, and ad copy in seconds — grounded in your sources. Free, no signup.
Try ScriptFlow free →Frequently asked
How long should an X thread be?
Five to nine posts covers most ideas. Under five, consider a single long post instead; over ten, attention decays sharply unless every post independently earns its place. Length should follow the idea, not a target.
What makes a good first post in a thread?
A specific promise plus a reason to believe it: name the payoff, quantify the experience behind it, and open a loop the thread resolves. It competes in the feed alone, so treat it like a standalone hook, not an introduction.
Do threads still work on X in 2026?
Yes, but the bar is higher: readers pattern-match growth-hack formats and skip them. Threads with concrete, bookmark-worthy substance and one clear ask still outperform single posts for reach and follower conversion.