How to Structure a Thread on X

A good thread is a list of ideas with a promise at the top. The first post says what the reader will get, each following post delivers one piece of it, and the last post wraps up. That sounds obvious, but most threads that don't work break one of those three parts: a vague opener, posts that cram in two ideas or none, or an ending that just stops.

Here's how to build each part.

Decide whether it should be a thread at all

Before you start, check that the idea needs more than one post. A thread makes sense when you have several connected points, steps in an order, or a story with a few beats. It doesn't make sense when you have one idea and a lot of words around it. Edit that down into a single post instead. Our guide to editing a post down to fit shows how.

Subscribers to X's paid plans can write long posts of up to 25,000 characters, which is another option for text that doesn't break into parts naturally. A thread is better when each part stands on its own and could be quoted or shared alone.

The opening post

The first post does most of the work, because it's the only one most people see. It needs four things, though not always in this order:

1. A promise: what the reader will know or be able to do by the end.
2. A reason to trust you: one line of experience, if it's relevant.
3. A sense of what's coming: the parts, or how many there are.
4. A cue that there's more, such as "Here's how:" or a downward arrow.

Here's an opener built that way:

How to plan a vegetable garden for a small yard, from someone who got it wrong for three years.

Covering: sun, spacing, what to plant first, and what to skip.

Here's the plan:

The formula builder's "Thread opener" option builds this structure for you. Fill in the promise, your experience and the parts, then compare the variants.

One idea per post

Each post after the opener should carry exactly one idea. It can be a step, a tip, an example or a story beat. When you put two ideas in one post, the second gets lost. When a post has no idea in it ("Let's get into it!"), readers start skimming.

A simple way to check: write a three-to-five-word label for each post before you write the posts themselves. If you can't label a post, it doesn't need to exist. If a label has "and" in it, split the post.

Writing the labels first is also the fastest way to spot a thread that's too long. If you have twenty labels, you probably have two threads.

Make each post readable on its own

People don't always arrive at the top. A post can be quoted, shared or surfaced in search by itself. Write each one so that it makes sense with no context. That usually means naming the subject again instead of saying "this" or "it" at the start.

"It matters more than spacing" means nothing on its own. "Sunlight matters more than spacing" works anywhere.

Use transitions sparingly

A few words at the start of a post can carry the reader from one idea to the next: "Next:", "The catch:", "Then the part nobody mentions:". Use them where the order matters or where you're changing direction. Don't put one on every post. Numbering already tells people they're moving forward.

Numbering

Numbers like 1/6 or 1/ help readers know how long the thread is and where they are in it. They also make it easy to refer back ("see 4/6"). The cost is a few characters per post, which matters when you're close to 280.

Pick one style and stick to it within a thread:

• "1/6" at the end tells readers the total, but you have to know the total before you post.
• "1/" at the start is flexible if you might add posts later.
• No numbers suits short threads of three or four posts.

The thread splitter on our home page adds either style and reserves room for it, so no post goes over the limit once the numbers are on.

The closing post

End with a post that gives readers something to take away. A one-line recap of the main points works well. So does one action they can take today. If the thread was useful, people will want a way to save or find it again, and a clear final post makes that easier.

You can mention where to find more of your writing in the last post, but keep it to one line. A closing post that is entirely a pitch undercuts the useful posts before it.

Posting the thread

On X you build a thread by writing your first post and then tapping the plus button to add the next. You can write the whole thread before posting anything, which is the best approach: you can reread it as a whole and move posts around before anyone sees it.

After posting, read it once on your phone. Line breaks, emoji and links can look different there than in a draft. If something's wrong in an early post, fixing it quickly matters more than for later posts, since the opener gets the most views. Subscribers can edit posts for a short window after publishing. Everyone else has to delete and repost, which breaks the thread at that point.

A thread checklist

Before you post, check that:

• the opener makes a specific promise and fits within the first lines
• every post has one idea you could label in a few words
• each post makes sense if read alone
• numbering is consistent and no post is over 280 characters
• the last post wraps up instead of just stopping

Write the opener with the builder, paste the full draft into the splitter, and read the result once out loud. That last step catches more problems than any checklist.

Questions

How many posts should a thread have?

As few as the idea needs. Five to eight posts covers most how-to threads. If you're past fifteen, consider whether it should be two threads or a longer piece somewhere else.

Should I number the posts in a thread?

Numbering such as 1/7 helps readers know how long it is and where they are. It costs a few characters per post. For short threads of three or four posts it's optional.

Can I add to a thread later?

Yes. Open the last post in your thread and reply to it yourself, or use the option to add another post. The new post joins the thread for anyone reading it.