Guide · 9 min read
How to write a thread on X (Twitter) that people read to the end and share: when to use one, how to structure it, the first post, and a template.
A thread is a chain of connected posts. Use one when your idea needs steps, a story or several examples, and each part can stand as a short post on its own. Good thread material: a how-to, a breakdown of something you did, lessons from an experience, a story with a turn, a curated list of resources.
If the idea fits in one post, post it as one. Threads that pad a single point into eight parts lose readers by the third post.
Premium accounts can also write one long post. A thread is still better when each part is a self-contained point people might reply to or share on its own.
Most readers decide from the first post whether to open the thread. It needs to make a clear promise and make people want the rest. Strong first posts usually do one of these:
These are invented examples. Keep the first post readable on its own: it should make sense to someone who sees only that post, and contain the core idea even if they never open the rest.
A dependable shape for five to ten posts:
Write the whole thread before you publish, in a notes app or X's composer, which lets you add posts with the + button. Read it once on your phone.
Publish when your audience is active, then stay for the first hour to answer replies. Put any links in the last post or in a reply, not the first post. If the thread does well, pin it to your profile: it becomes the best proof of what you know.
A good thread is a stock of material. Each body post can become a standalone post weeks later, the summary can become a short post, and the thread itself can be rewritten with a new angle in a few months for the followers who missed it.
If you want a fast first draft of a thread to edit, ReplyKit can write blank-line-separated threads on X and insert them post by post into X's own thread composer, so you only have to edit and publish.
As long as the idea needs, usually five to ten posts. Every post should carry its own point; if you are adding filler to reach a number, it is too long.
Yes, for how-tos, breakdowns, lessons and stories. They keep readers on your content and give them several posts to reply to or share. For a single idea, one post works better.
Write your first post in the composer, then tap the + button to add the next post, and repeat. Publish them all at once with Post all. You can also reply to your own post later to extend a thread.
It helps in long step-by-step threads so readers know where they are. In stories and short threads, numbers are optional and can be left out.
Built by · One person
There is no company behind this, just one developer who reads every message. If ReplyKit does not fit how you work, a feature, a platform, a different style of reply, say so. Requests from users decide what ships next.
Prefer email? contact@replykit.eu