How to Make a Thread on X (Twitter), and How to Schedule One

Short answer: to make a thread on X, write your first post, tap the + button that lights up once you have typed something, write the next post, repeat, then tap Post all. To add to a thread you already published, open it and use Add another post. To schedule a whole thread ahead of time, you need a tool that posts each part as a reply to the one before, because that is how a thread exists on X: a chain of replies from the same account.

Below: the steps for app and web, how a thread is built under the hood, and what made scheduled threads fail in our own logs.

Make a thread in the X app or on the web

1. Tap or click the compose button.
2. Write the first post. This is the one people see in their feed, so it has to work on its own.
3. Tap the + icon. X highlights it only after you type some text.
4. Write the next post. Repeat for each part.
5. Tap Post all.

X's Help Center describes the same flow. Each part follows the normal post rules: 280 characters unless you have Premium, and each part can carry its own images, video or poll.

Add to a thread you already posted

Open the thread and look for Add another post under your last post. Only you, the author, see that prompt. Whatever you add becomes a reply to your own last post, so it joins the chain.

The same trick works by hand: reply to your own latest post in the thread. Reply to an earlier post instead and you start a branch, which readers see as a separate conversation.

How a thread actually works

There is no "thread" object on X. A thread is your first post plus a series of replies, each one replying to the post before it. When a tool publishes a thread through the X API, it does exactly that:

1. POST /2/tweets with the first post's text. X returns its id.
2. POST /2/tweets with the second part and reply.in_reply_to_tweet_id set to that id.
3. Repeat, each time replying to the id of the part just published.

That is how TimeToPost's X publisher works today. It also waits about 1.1 seconds between parts so the chain does not hit X's rate limiter, and if one part fails it stops there and reports how many parts went out, so you never end up with a reply chain that skips a step. The X API charges per post, so a 6-part thread costs 6 posts.

Schedule a thread on X

X's own scheduler (web only, in the composer's calendar icon) handles single posts. To put a full thread on a calendar you need a scheduler that supports threads. In TimeToPost:

• In the composer: write the first post, add the follow-up parts as thread items, pick the X account and a time.
• From an AI assistant over MCP: the publish_thread tool takes segments (the first post, then up to 24 more, so 25 in total, each 280 characters or less) and an optional schedule_at time. Leave out the time and it goes out on the next scheduler tick, about a minute later. get_post then returns the published post ids.

An example call:

{
  "segments": [
    "How we plan a week of posts in one sitting. 3 steps.",
    "1. Write every post on Sunday, in one document.",
    "2. Put each one in the calendar at the hour our audience replies.",
    "3. Check the queue on Monday morning for anything marked failed."
  ],
  "schedule_at": "2026-11-12T19:00:00Z"
}

What breaks a scheduled thread: our logs

From TimeToPost's production database on 7 November 2026 (all workspaces, counts only):

| Measure | Value | |---|---| | Scheduled threads published in full | 13, with 1 to 5 follow-up parts | | Scheduled threads that failed | 5 | | X failed attempts: "Text exceeds maximum length of 280 characters" | 39 | | X failed attempts: "Failed to upload media to X: no media ids returned" | 75 | | X failed attempts: HTTP 402 (API credits ran out) | 8 | | How late an X post went live after its scheduled minute | median 3.6 seconds, 90% within 57 seconds |

What to take from it:

• Count every part, not just the first. A part over 280 characters is the most common text error we see. On X itself you can see the counter. In a tool or an AI-written thread, check the longest part before you schedule. X itself counts each link as 23 characters, but a tool may count the full URL (TimeToPost checks the raw text), so shorten long links in the part that is close to the limit.
• Media is the fragile bit. Most failed X attempts were media uploads. Keep images under X's size limit and video in MP4, and if a thread does not depend on an image, leave the image off the scheduled version.
• Threads go out on time. The median post went live 3.6 seconds after its scheduled minute. A thread of 6 parts takes about 6 more seconds because of the gap between parts.

Thread tips that hold up

• Put the point in the first post. Most readers see only that one.
• Number the parts (1/, 2/) only if order matters. People skim.
• End with one clear next step: a link, a question, or nothing.
• Schedule threads when your own audience replies, not at a generic best time. Best time to post on X shows how we measure it per account.

For single posts, how to schedule tweets in 2026 covers X's free scheduler and the API costs. The X scheduler page shows TimeToPost's X features, and X MCP server shows the MCP tools with real responses.

FAQ

How do you make a thread on Twitter?

Write your first post, tap the + icon that lights up after you type, add the next post, repeat, then tap Post all. Each part is posted as a reply to the one before it.

How do I add to a thread I already posted?

Open the thread and tap Add another post under your last post, or reply to your own latest post in the thread. Replying to an earlier post creates a branch instead.

Can you schedule a thread on X?

X's built-in scheduler handles single posts. A scheduler that supports threads, such as TimeToPost, can schedule the whole chain and publish each part as a reply at the chosen time.

How long can each post in a thread be?

280 characters per part without Premium. X counts each link as 23 characters. In our logs, a part over 280 characters is the most common text error in scheduled X posts.

How many posts can a thread have?

TimeToPost's publish_thread tool accepts up to 25 parts, the first post plus 24 replies. Long threads are rarely read to the end, so most published threads in our logs had 2 to 6 parts.