How to schedule a thread on X: native options and tools

X documents scheduling in X Pro, Media Studio and the Ads Composer, but none of the X help pages we checked says you can schedule a whole thread there. So if you want a thread to go out on its own at a set time, use a scheduler that supports X threads: Buffer does it on its free plan, and Typefully, Tweet Hunter, Fedica and PlanPost do it too.

A quick note on the name: this page is about a thread on X, a chain of connected posts. For Meta's Threads app, see how to schedule Threads posts.

Can you schedule a thread on X with X's own tools?

X's Help Center covers this much:

• X Pro (formerly TweetDeck) can schedule posts. It comes with X Premium, which cost $8 a month on monthly billing when the X Pro page was checked on 9 November 2026.
• Media Studio and the Ads Composer can schedule posts too. Ads Composer posts don't have to be ads.
• Posts over 280 characters can't be scheduled on the web.

None of these pages describes scheduling a thread. X's help pages block automated reading, so we couldn't check them again for this article. If you already pay for Premium and see a thread option in X Pro's scheduler, try it with a short test thread before you rely on it.

You may also have read about a calendar icon in the regular x.com composer. As our guide to scheduling posts on X explains, we couldn't find that documented by X either.

How to schedule Twitter threads with a scheduler

Most tools work the same way: you write the first post, add more posts below it, then schedule the whole set. The tool publishes the first post at your chosen time and chains the rest under it. Three tools spell out the steps in their help pages:

Buffer

1. In the composer, select your X channel and write the first post.
2. Click + Start Thread to add a post. Keep adding with the + button, or press Enter three times.
3. Schedule the thread or save it as a draft.

Buffer allows up to 25 posts in a thread. You can only create threads in Buffer on the web. The mobile app can only reschedule or delete them.

Typefully

Write your thread in the editor, click the orange Schedule button and pick a time, or use Next slot to drop it into your queue. Scheduled posts appear in the Queue tab and on the calendar. Typefully allows up to 50 posts in a thread.

Tweet Hunter

In the writing module, write the first post, then press Enter three times to start the next one. A preview of the thread shows on the left. Auto-retweet and auto-plug also work on threads, but only on the first post.

Tools that schedule X threads, compared

Plan figures come from each vendor's pricing page, on the dates shown on the linked tool pages. PlanPost is this site's own product and is held to the same criteria as the others.

Which one to pick:

• You want it free and post to several networks: Buffer. Its free plan is the only one here that says threads are included.
• Threads are most of what you write: Typefully is built around them and allows the longest threads in this table.
• You only use X and want growth tools around your threads: Tweet Hunter, which works only on X.

Two tools you might expect here aren't in the table. Hypefury's pricing page, read today, lists six platforms and X isn't one of them. CoSchedule's support docs say it can't publish multi-post threads on X.

A long post instead of a thread?

If you pay for X Premium, one long post can stand in for a thread. You can't schedule it in X's own tools, though, since X doesn't allow scheduling posts over 280 characters on the web. Some schedulers can:

• Publer says any X Premium tier, Basic included, can schedule long posts through Publer.
• Buffer supports up to 25,000 characters for paid X accounts. Only the first 280 show on the timeline, so put any link inside them.
• Typefully lets Premium users publish threads in which each post holds up to 25,000 characters.

How threads work through the X API

This part is for developers. In the X API a thread has no special type. It is your first post plus replies: each later post is created with POST /2/tweets and a reply.in_reply_to_tweet_id pointing at the post it continues. X's Manage Posts docs name "create threads" as one of the things these endpoints are for. All the posts share the first post's conversation_id.

For anyone building this:

• Every post in the thread is its own request. On pay-per-use, X's pricing page lists $0.015 per created post, $0.20 for a post containing a URL, and $0.010 for a summoned reply. The docs don't say which rate a reply to your own post gets. More in our X API pricing guide and the April 2026 repricing entry.
• The reply restriction. Since 23 February 2026, self-serve apps may only reply when the original post's author has summoned the replying account, by @mentioning it or quoting one of its posts (changelog entry). The docs list only those two cases and don't mention replies to your own post. Test your thread flow before you promise it to users.
• Rate limits. The create endpoint allows 200 requests per 15 minutes per user, and there's a separate limit of 300 posts per 3 hours.

These rules apply to every tool above. The API changelog and the X network page track new changes.

What to do next

• Business owners: Try a thread on Buffer's free plan first. Before you schedule, run each post through the character counter, which counts the way X does.
• Marketers and agencies: Check how each tool limits threads on the plan you'd actually use, especially Buffer's one-thread-per-queue cap on Free. Then compare paid plans on the X network page.
• Developers: Build threads as reply chains, count one create request per post, and test the summoned-reply rule against your own account before launch.