How to write an X thread, from opening to useful ending
Write an X thread around a specific task: open with what you will show, give each post a job, and finish with something the reader can try. Use the annotated draft below to turn an idea into a sequence before you publish.
Short answer
Draft the whole thread before publishing. Start with a specific promise, show a worked example, explain the choices behind it, and end with a next step. Cut any post that does not help deliver the opening promise.
The X Help Center, as captured on 4 September 2026, defines a thread as a series of connected posts from one person. You add posts with the highlighted plus icon, then tap Post all to publish.
Step 1: choose the point before writing the opener
Write this sentence in your draft: “After reading this, you can ____.” Pick a task small enough to explain with one worked example. The example in this guide: “turn a vague project update into a question about a specific screen.”
Leave out anything that does not help with that task. If your draft tells your whole product history before it reaches the screen, start later and save the history for another post.
Step 2: make the opening specific
Name the reader’s situation and what you will show. A pattern to start from: “Working on [specific task]? Here is [example or method] for [specific outcome].” It is a writing prompt, not a promise of reach.
For the example below: “Working on a signup screen? Instead of posting ‘Any feedback?’, ask about the exact decision you’re stuck on. Here’s a draft you can adapt.” Now the rest of the thread has one job: show the draft and explain the question.
Step 3: give each post a job
This thread is an illustration, not a published post. Use the sequence as a draft: opening, situation, example, explanation, ending. Swap the signup-screen example for something you are actually working on.
| Post | Example draft | What it does |
|---|---|---|
| 1: Opening | Working on a signup screen? Instead of posting ‘Any feedback?’, ask about the exact decision you’re stuck on. Here’s a draft you can adapt. | Names the task and promises a concrete example. |
| 2: Situation | Start with the decision, not your whole product story. In this example, the decision is whether to ask for a workspace name during signup or after it. | Sets up the choice the next post will show. |
| 3: Worked example | Draft: ‘I’m building a signup flow for a team app. Would you expect to name your workspace during signup or once you’re inside? What would make you choose?’ | Gives the reader wording to adapt. |
| 4: Explanation | The draft asks about one choice: when to name the workspace. Keep the screenshot focused on that choice too. Leave unrelated settings out of this post. | Explains the editing decision behind the example. |
| 5: Ending | Try it with your next update: name the screen, describe the decision, then ask about that decision. Which part of your current project would you use this for? | Gives a next action and a question tied to the topic. |
Draft the middle before polishing the opening. If the example does not deliver what the opening promises, change the promise or the example. Do not add posts just to make the thread look longer.
Step 4: read it as a sequence
Read only the first sentence of each post. You should be able to follow the argument from the opening to the ending. Then read the whole draft and cut repeated setup.
- Keep one job per post. Split the example from its explanation if both feel cramped.
- Name what you mean. Replace a vague “this” with “the workspace-name question” when the reference is unclear.
- Make the ending useful. Give the reader an action that follows from the example, not a generic request to follow you.
Step 5: add the posts and publish on X
In the X Help Center instructions, as captured on 4 September 2026, you add another post by tapping the highlighted plus icon and publish the thread with Post all.
- Put your opening in the post composer.
- Add the next part with the highlighted plus icon, following the archived X instructions captured on 4 September 2026. Repeat for the rest of your draft.
- Read the assembled thread in order and check that the example and the ending are both there.
- When you are ready, use Post all, the publishing control named in the X instructions as captured on 4 September 2026.
Common mistakes to cut from the draft
- A big promise with no example. Replace “Everything you need to know about product feedback” with the specific decision your thread explains.
- An unrelated point halfway through. Move it to a separate draft instead of forcing a transition.
- An ending that starts a new topic. Finish the task you opened with. If you want a conversation, ask about that task.
- Turning every idea into a thread. If the useful part fits in one post, try that version first. For ideas aimed at a new account, see what to post while building your first 1,000 followers. For the conversation after publishing, read the X reply strategy.
FAQ
What is an X thread?
The X Help Center, as captured on 4 September 2026, defines a thread as a series of connected posts from one person.
How do I create a thread on Twitter?
The X Help Center instructions, as captured on 4 September 2026, say to tap the highlighted plus icon to add another post and tap Post all to publish. Draft the opening, the middle posts and the ending first.
How should I start an X thread?
Name a specific situation and say what you will show. For example: ‘Working on a signup screen? Instead of posting Any feedback?, ask about the exact decision you’re stuck on. Here’s a draft you can adapt.’ Then deliver that example in the next posts.
How should I end an X thread?
Give the reader a next action tied to the example. In the signup-screen draft, that means picking a screen and asking about one decision. If you ask a question, keep it on the same task instead of opening a new topic.
More free guides
- Your first 1,000 followers on XFrom 4 to 1,000 followers in ten days without ads: connect posts, replies, follow-backs and question posts, day by day.
- The reply game on XX Analytics numbers for 933 replies: reach, profile visits and followers, and why the replies that asked to connect won.