How to schedule a thread on X (Twitter) in 2026
Schedule real native threads on X: per-tweet media, first comment, and auto-retweet. What X's own scheduler can't do, and the tools that can.
X's own composer can schedule a single tweet, but it cannot schedule a thread. To schedule a real native thread (each segment its own tweet, published as a connected chain) you need a scheduling tool. Here is how to do it in Eden, what to know about media and character limits, and the two X-specific automations worth turning on: the first comment and the auto-retweet.
Full disclosure: we make Eden, and the walkthrough uses it. The limits and mechanics apply to any tool publishing through X's API.
Why threads need a scheduler
X's native scheduler stops at one tweet. Threads are where the depth lives (and where profile visits and follows come from), and writing them at 7am to post at 9am defeats the point of batching. A scheduler lets you write a week of threads in one sitting and publish them at the times your audience is actually online, from the tool's servers, with your laptop closed.
Scheduling a thread in Eden
- Connect X once. Settings, then Scheduling, then Connected accounts. You approve on X's own login page; Eden never sees your password.
- Write the thread. In the composer, each segment becomes its own tweet. Add a segment per point. The 280-character count applies per segment, not to the whole thread.
- Add media per tweet. Each tweet in the thread can carry up to 4 images, or exactly 1 video, or 1 GIF. Those never mix inside a single tweet, which surprises people coming from other platforms.
- Pick a slot and schedule. Choose a time or let your queue's default slots place it. Eden publishes the chain server-side, tweet by tweet, in order.
The same composer cross-posts the idea to other platforms with per-platform editing, so the thread's LinkedIn version can be a different shape without writing it twice.
The two automations worth turning on
- First comment. Auto-post a comment right after the thread goes live: immediately, after a delay, or once the post hits a like threshold. This is where your link or CTA belongs, since links in the post body measurably reduce reach.
- Auto-retweet. X-only: Eden reposts your own post to your timeline a few hours later (up to twice), catching a second timezone, with an optional auto-remove so your profile stays clean. It is the lowest-effort reach multiplier X allows.
You can also schedule reposts and quote posts of other creators' posts by pasting the post's link into the composer, which makes curation schedulable too.
Deciding what the thread should say
The scheduling part is mechanical. The hard part is upstream: which threads are worth writing. That is what the research half of Eden is for: study the outlier threads in your niche, save the ones with hooks that stopped you into a swipe file, and draft with a Custom AI trained on your own voice.
Frequently asked questions
Can you schedule a thread with X's own scheduler?
No. X's native scheduler handles single tweets only. Threads require a third-party tool that publishes the chain through X's API.
What are the limits per tweet in a scheduled thread?
280 characters per tweet on a standard account, and per tweet either up to 4 images, or 1 video, or 1 GIF. Media types do not mix within one tweet.
Will scheduled threads perform worse than posting live?
No. The thread publishes through X's API as a normal native thread; readers cannot tell it was scheduled. What matters is the content and the timing, and scheduling usually improves both because you write in batches and publish at peak times.
What is the best tool to schedule X threads?
Typefully has the nicest minimal thread editor, and our Typefully alternatives guide compares the field honestly. Eden's case: threads plus first comment plus auto-retweet, in the same tool that researches what to write and schedules seven other platforms.
Write one thread tonight and schedule it for tomorrow's peak. Start free, no card, and see what batching does to your consistency.