To write a thread people finish: put the real claim in the first post, give every post after it exactly one idea, keep the link out of the opening, and end on a decision rather than trailing off. Four to twelve posts is the range that holds together. The first of those four rules matters more than the other three combined, because the first post is the only one most people will ever see.
Everything below is about structure rather than mechanics. Posting a thread is a reply chain and takes no explaining; writing one somebody reads to the bottom is a craft problem.
Should this be a thread at all?
One test, and it takes a second. Does the order matter?
A thread is the right shape for a sequence of dependent steps: an argument where point three only makes sense after point two, a story where the ending needs the setup, a walkthrough where each stage builds on the last. The reader is carried, and the form does the carrying.
A list that can be read in any order is not a thread, it is a list, and it publishes better as one post or as a graphic. Seven unrelated tips across seven posts asks the reader to keep tapping for what one glance would have given them, and the usual outcome is that they read two and leave. Shuffle your points: if the piece survives it, you do not have a thread.
The first post is the whole thread
Most of the people who see your thread will see exactly one post of it, in a feed, between two other things, for about a second. That post is not an introduction. It is the entire piece of communication, and everything after it is optional reading for the minority who wanted more.
Which rules out the opening most threads use. A thread on something I have been thinking about tells the reader nothing and asks for a tap in exchange for a promise. An opening that states the conclusion outright has already delivered something, and the tap is for the reasoning.
Three properties make a first post work. It stands alone, so somebody who never opens the rest still got a complete thought. It is specific enough to disagree with, because a claim nobody could argue with is a claim nobody needs. And it leaves an obvious gap, a visible how or why that the rest of the thread fills.
It also has to survive being cut. The timeline shows a limited amount of a post before it stops and offers a Show more link, so a claim sitting in the final line is hidden from everybody who did not tap. Where that cut lands is worth ten minutes if your openers run long.
One idea per post
The reason a thread reads better than the same words in one block is pacing, not length. Each post is a beat, and a beat carrying two ideas reads as neither. In practice that is an editing rule with a simple tell: if a post has an and also in the middle of it, that is usually two posts.
The other half of the rule is where you break. A post that ends mid-sentence because the 280 character limit arrived there reads as broken, and it is the clearest sign that a document went through a splitter untouched. Break at sentence ends, and let the posts be uneven.
Writing a thread, step by step
- Write the conclusion before the thread. Put the single claim the thread is making into one sentence first. If you cannot, what you have is a collection of observations and it will read like one. That sentence usually becomes the first post.
- Draft it as continuous prose. Write the whole argument as one piece of text, without thinking about post boundaries. Writing straight into boxes makes you pad the short posts and amputate the long ones, and both show.
- Break at the ideas, not at the character count. Cut where one idea ends and the next begins, then check each piece fits. A post with an "and also" in the middle of it is usually two posts.
- Rewrite the first post until it stands alone. Read it with nothing after it. It should state the claim, make sense to somebody who never opens the rest, and leave a visible gap. Most of the editing time goes here.
- Add numbering only if the order matters. Use 1/8 numbering when the sequence is load-bearing and you know the count. Reserve the characters before you split: "12/15 " is six characters off every post.
- End on a decision, and put the link there. The last post closes the argument or asks for the one thing you want, usually a reply or a follow. Any link belongs here, never in the opening post.
How many posts should a thread be?
X publishes no ceiling on thread length, so the real limit is attention. Threads that hold together tend to run four to twelve posts.
Under four is usually one post that has been stretched, and it reads that way. Past about fifteen you are writing an article: twenty posts is twenty taps and twenty chances to stop. That material deserves a page, and the thread deserves to be the two posts that make somebody want the page.
Numbering, and what the numbers cost
Three conventions are in common use. 1/8 at the front is the clearest, because a reader arriving at post six knows immediately where they are and how much is left. 1/8 at the end keeps the opening words of every post clean, which is what a scroller reads. And a plain 🧵 on the first post signals a thread without committing to a count.
Whichever you pick, the numbers are ordinary text and they are charged like it. "12/15 " is six characters out of your 280, on every single post, and it gets a character wider the moment the thread crosses from nine posts to ten. That is the most common way a thread fails at publish time: split at exactly 280, numbered afterwards, and now X refuses most of the posts one at a time.
The fix is to reserve the width before splitting rather than after. If you are counting by hand, the arithmetic behind the limit, including why a link costs 23 whatever its length, is laid out in how many characters is a tweet.
Where the link goes, and how to end
Keep the link out of the first post. It offers people somewhere else to go at the exact moment you have least earned it, and the ones who take it leave before the thread has made its case. Last post, or a reply to it, where a reader who got that far has already decided they want more. It costs 23 characters wherever it lands.
And end the thread on purpose. A thread that simply stops reads as abandoned, and the last post is where the reader who stayed is most willing to act. Close the argument, or ask for the one thing you want, usually a reply or a follow.
Thread or X Premium long post?
X Premium raises the limit to 25,000 characters, which makes the thread look like a workaround for a problem that has been solved. It has not been, and the reason is distribution rather than length.
Every post in a thread is a separate item in the timeline. Each can be seen, replied to, quoted and reposted on its own, and each is a fresh chance to reach somebody who missed the first. An eight-post thread is eight openings. A long post is one, and it still shows only about 280 characters in the timeline with a Show more underneath, so the hook problem has not gone anywhere either.
Long posts do earn their place. Something that has to be read in one sitting, where breaking it up would damage it, is better as one page than as twelve fragments. If you are unsure which you have, try splitting it: if it comes apart cleanly at paragraph boundaries, it was always a thread.
The harder question is usually what to put in a thread at all. That one is answered in what to post on X, and the rest of the format mechanics are in the X guides.
Frequently asked questions
How do I write a Twitter thread?
Decide the single claim the thread is making, then write the first post so it states that claim and works on its own. Give every post after it one idea, break at sentence ends, keep the link out of the opening, and end on a post that closes the argument or asks for something.
How many tweets should a thread be?
There is no published ceiling, and attention runs out long before the platform does. Threads that hold together tend to sit between four and twelve posts. Under four is usually one post that has been padded; past about fifteen you are writing an article, which is better served as a link.
Are threads or long posts better on X?
A thread, for most things. Every post in a thread is its own item in the timeline with its own chance to be seen, replied to and quoted, so an eight-post thread has eight openings and a long post has one. The 25,000 character long post also shows only about 280 characters in the timeline with a "Show more" link. Long posts suit a piece meant to be read in one sitting.
Should I number the posts in a thread?
Numbering helps when the order matters: it tells a reader arriving at post six that there are five above it. Use 1/8 style numbering when you know the final count, or a plain 🧵 on the first post when you do not. The numbers are ordinary text, so "12/15 " costs six characters out of your 280 on every post.
Where should the link go in a thread?
Not in the first post. The opening has to earn the read, and a link in it offers people somewhere else to go before they have a reason to want to. Put it in the last post, or in a reply to it. Wherever it lands it costs a flat 23 characters, because X rewrites every link through t.co.
How do I start a thread so people actually read it?
State the conclusion rather than announcing the thread. "A thread on something I have been thinking about" tells the reader nothing and asks for a tap anyway. The opening post should make a claim specific enough to disagree with, and it should work as a standalone post even if nobody opens the rest.