How-toFoundation/5 min read

How to schedule posts on X, and where they hide once you have

Scheduling from the X composer, where scheduled posts actually live, what the native scheduler cannot do, and when a third-party tool earns its place.

Kavish Shah

Founder of Cadencz. Writes the Academy from the work of building it.

Published Updated

Class notes

What you will be able to do

  • Scheduling is in the composer: write the post, click the calendar icon in the toolbar, pick a date and time, then Confirm and Schedule.
  • Scheduled posts do not appear in drafts. They live behind the same calendar icon, under Scheduled Posts — which is why so many people think theirs vanished.
  • The native scheduler is web-only in practice and handles one account at a time. If you run several accounts or publish to other platforms as well, that is where it stops being enough.
  • A scheduled post is not a queued post. X publishes at the exact minute you set; it will not shift the time to a better slot or space your posts out for you.

Scheduling on X lives inside the composer rather than in a separate section, which is why it is easy to miss entirely. Open the composer as normal, write the post, and look at the row of icons under the text field — image, GIF, poll, emoji, and a calendar. The calendar is the scheduler.

Pick a date and time, confirm, and the post moves out of the composer into a queue. These steps were checked on September 5, 2026; X moves this control occasionally, so the linked help page is the authority if the toolbar looks different.

Where the scheduled post goes

This is the part that generates most of the confusion, and it has a simple answer: scheduled posts are not drafts and are not in the drafts list. Open the composer again, click the same calendar icon, and there is a Scheduled Posts tab alongside the date picker. Everything waiting to publish is in there, and you can edit or delete from that view.

The reason it feels hidden is that there is no entry point from the main navigation. If you have closed the composer, there is no obvious route back to your own queue.

  • Editing a scheduled post keeps its slot; deleting it does not put the content back in drafts, so copy the text first if you want to keep it.
  • A scheduled post that fails at publish time — a deleted image, a revoked permission — fails quietly. Check the queue after a batch rather than assuming.
  • Time is set in your local timezone, which is a trap when your audience is somewhere else. Convert deliberately.

When the built-in scheduler runs out

For one account and a handful of posts a week, the native scheduler is genuinely fine and costs nothing. It stops being enough at three specific points, and it is worth recognising them rather than tolerating the friction indefinitely.

  • More than one account. There is no cross-account view, so you are logging in and out to see what is queued where.
  • More than one platform. The same idea has to be written natively for each platform anyway, but doing it in four separate composers means four separate queues and no shared calendar.
  • Anyone else in the loop. There is no approval step. If a co-founder or client sees posts before they ship, the native scheduler cannot express that at all.

Choose an X scheduler with the right plan

When comparing a Twitter scheduler or X post scheduler, check whether the account is included in the plan and whether the format is supported. Cadencz requires a paid plan for X. Its free scheduling offer applies to other supported accounts, so do not treat it as a free tweet scheduler.

Sources used

Sources and freshness

Sources were reviewed on . Product features, prices, and platform rules change; follow the source links before relying on a volatile detail.

  1. 01How to schedule postsX Help Center
  2. 02Counting charactersX Developer Platform

Keep learning

01Where X drafts are saved, and why yours disappearedFind your X drafts, and stop losing the ones that matter.
02The X (Twitter) character limit, and the counting rules nobody mentionsKnow what X counts before you hit send, not after it truncates.
03X content strategy for founders building in publicRun an X presence on claims, build notes, and replies instead of a thread calendar.