How to schedule posts on X: the complete guide

You wrote a good post at 11 p.m., and it would land better at 9 a.m., when your followers are awake and you are not at your desk. So you search for how to schedule posts on X and find guides that disagree. One says only on a laptop, another says the app does it now, a third is selling a tool.

This guide sorts that out as of 1 October 2026. You will learn:

• Where X lets you schedule, surface by surface, and what we could and could not confirm.
• How to edit or delete a scheduled post, and what changes once it is live.
• Which clock a scheduled post runs on, and why a slot can drift by an hour.
• What a third party scheduler really does through the X API.
• A weekly routine and the mistakes that break it.

A note on sources. X's own help pages block automated reading, so some facts below come from excerpts of those pages, from news reports and from tool vendors' guides. We say which each time, and where X has not written a rule down we say that too. Choosing a tool? Our buyer's checklist for X schedulers lists what to test, and scheduling a thread has its own traps.

How do you schedule a post on X?

Open x.com in a browser, start a post, click the calendar icon in the composer, pick a date and time, and press Schedule where the Post button used to be. That is X's built in route. Tool vendors' guides describe the same steps, and the news coverage we read says X has offered scheduling on the web for years.

1. Sign in to the right account

   Scheduling happens in the account you are signed in to. If you use more than one account, check the avatar before you write a word.

2. Write the post and add media

   Write it as you would for an immediate post. Attach images, a GIF or a video now, because you cannot check them once you walk away.

3. Click the calendar icon

   Guides describe it as a calendar icon with a clock in the composer's toolbar, in the same row as the image, GIF and poll icons.

4. Pick the date and time, then confirm

   Read the time zone the picker shows before you confirm. Part of this guide is about why.

5. Press Schedule

   The Post button now reads Schedule. The post goes into your list of unsent posts instead of the timeline.

How far ahead can you go? Tool vendors report that the web composer accepts dates up to 18 months out. The X pages we could read do not state a maximum, so treat 18 months as a report, not a rule. X's Ads API caps scheduled posts at one year, which is a different surface. We suggest you plan a week or two at a time.

Where can you schedule posts on X?

Six places, and they are not equal. The web composer works for most people. The others serve specific accounts, and the iOS app only started in September 2026. For the steps inside X's own app, see how to schedule a post in the X app.

X Ads schedules posts too. In ads.x.com, under Creatives and then Posts, an advertiser can schedule an organic post or a promoted only post up to a year ahead. Five planning questions have their own guides: a queue or fixed time slots, quiet hours at night, weekend posting, scheduling for a global brand and scheduled vs live posting.

What about a team? X's Delegate page says contributors and admins can act on behalf of the delegated account, including scheduling posts. That lets an agency schedule without a shared password. Our guide to managing X for clients covers the approval side.

How do you edit or delete a scheduled post on X?

Open the composer on the web, choose Unsent posts, and switch to the Scheduled tab. Click a post to change its text, media or time, or delete it. Do it before the send time, because after that it is no longer scheduled. Brandwatch's guide describes the same route.

1. Open the composer

   On x.com, click Post to open the composer, as if you were writing a new post.

2. Go to Unsent posts

   Guides place the Unsent posts link at the top right of the composer. It holds two tabs: Drafts and Scheduled.

3. Open the scheduled post

   Click the post. You can change the text, swap the media or move the time, then schedule it again. Or delete it.

4. Check the time before you leave

   If you moved the time, read the zone name once more. Most mistakes happen on the second visit, not the first.

In X Pro, you add a Scheduled column to your dashboard and edit from there, according to X's help page. In Media Studio, X warns about one trap. If you modify a Media Studio scheduled post on x.com, X says it creates a new, lower quality copy of the media and loses the metadata you set in Media Studio. So finish edits where you made the post.

After the send time, the post is an ordinary post, so ordinary rules apply. According to X's Edit Post page, X Premium subscribers get a 1 hour window and up to five edits, on original posts and quotes only. Once you reply to your own post it can no longer be edited. Without Premium, delete the post and publish a corrected one.

Which time zone does a scheduled post use?

The one you chose, if you looked. The X pages we could read do not say which zone the web composer uses. Media Studio's page says its date picker shows your current time zone. Either way, the safe habit is the same: read the zone name in the picker before you confirm, and write it next to every slot in your plan.

Tools add a second layer. Buffer's help centre says it publishes a post by the channel's time zone, and that the calendar and queue may show times in your browser's time zone for reference. Two clocks on one screen is how people end up an hour out. Ask any tool you use which clock it publishes on and which it displays.

Then there is the quieter problem: clock changes. A slot can be saved as a wall clock time ("9:00 in New York") or as a fixed instant ("13:00 UTC"). They agree for half the year and disagree for the other half. Two failure cases have their own guides: daylight saving time and what happens when a scheduled post fails.

The dates that matter this autumn are below. Hawaii and most of Arizona do not change their clocks.

If your audience spans the Atlantic, the gap between London and New York is 4 hours instead of 5 for the week between those dates.

Our guide to the best time to post on X shows how to work out which hours suit your audience. Here we only need the habit: after every clock change, open your queue and read the times. When the news turns serious, know when to pause scheduled posts.

Can you schedule threads, polls and media on X?

You can schedule one post with media. Threads are the gap. Tool vendors say the web composer's scheduler handles single posts and not threads, and we found no X page that says otherwise. Polls we could not confirm from any X page, so test one on a spare account.

Why does media need care? Through the API, X's reference says a post can include up to 4 photos, 1 animated GIF or 1 video, and that media is uploaded first and attached by its ID. If a tool fails to upload your image at 9:00, it may send the post without it or not send it at all. Ask which.

A scheduled post cannot be checked by you at the moment it goes out, so the checks move to the day before. Three guides cover them:

• Length. How X counts characters explains why a link, an emoji or a script can cost more than it looks.
• Images. X image sizes lists the shapes and file limits so a crop does not surprise you.
• Threads. How to write an X thread covers the structure; schedule it only with a tool you have tested.

Add the image description (alt text) while the image is open in front of you. It is the step people skip when they batch a week of posts, and it is far easier now than at 9:00.

What do third party schedulers do through the X API?

They keep your post themselves, wait, and send an ordinary create post request for your account at the right moment. X's API reference for creating posts has no field for a publish time, so the clock lives in the tool, not at X.

Three numbers explain what that means for a tool and for you.

X bills API access by use, and a post with a URL costs more per request than one without. Who absorbs that cost depends on the tool, so ask before you assume it is free at scale. The 30 in the third box applies to the Ads API's scheduled posts, a separate surface, but it shows that X treats a burst of scheduled posts as something to limit.

So a scheduler depends on four things working at the same moment:

• The tool is running. If it is down at 9:00, X will not send the post for it.
• The connection is valid. The tool posts with the permission you granted through X's sign in. If that permission is revoked or expires, the request fails.
• There is room under the limits. X's API answers 429 when a rate limit is exceeded, and X's account limits apply on top.
• The rules allow it. X's developer guidelines list scheduled content from an automated account as allowed. Our X automation rules guide covers what is not allowed, including duplicate content across accounts.

Threads need one more question. A tool builds a thread by posting the first post, then sending each next post as a reply to the one before, which is what X's reference shows the reply field for. X changed what API replies are allowed in February 2026, so ask any vendor how it publishes threads today. Our automation rules guide explains the change.

Should you use X's scheduler or a tool?

Use X's scheduler for a few single posts on one account. Use a tool when you need threads, several accounts, a calendar, approvals or protection from your own mistakes. It is a fit question, not a quality one.

Whatever you pick, put it through the same short test.

Kairo Post's scheduling page describes schedules that follow each account's time zone, quiet hours and daily limits per account, and a missed slot rule for downtime, which skips a missed post or sends it once within a window you choose. Read it against the checklist like any other tool.

Why do scheduled posts fail?

Almost always the cause is the connection, a limit or the tool, not the post itself. These are the failures X's own documentation lets us name.

If you disconnect a tool in X's Apps and sessions settings, you remove its access. That is the right move when you leave a tool, and the usual cause of a sudden queue of failures when someone else does it by accident.

On limits, news reports from May 2026 said free accounts may publish 50 original posts and 200 replies a day, and that apps connected to an account count towards the same limits. The numbers have changed during 2026, so check X's limits page before a busy day rather than trusting a blog.

The rule is simple: open the tool's log before you reschedule anything, so you know whether the post failed or never left.

A weekly scheduling routine that holds up

Write once a week and check every morning. A batch is efficient, and the check is what makes it safe. Without it, a full queue becomes a list of posts that were right when you wrote them.

1. Friday, one sitting

   Plan and write next week

   Pick the week's slots, write the posts and attach media and descriptions. Put the time zone beside each slot.

2. Friday, same sitting

   Schedule and read it back

   Schedule everything, then open the list and read each time aloud. Check the first and last post twice.

3. Every morning, 5 minutes

   Read the next two days

   Look at today's and tomorrow's posts. Ask whether anything has changed since you wrote them. Edit or delete what no longer fits.

4. Midweek

   Reply and adjust

   Answer replies when they arrive, not on the schedule. Move a slot if the news has.

5. After a clock change

   Recheck every slot

   Open the queue and read the times against the new offset.

Read tomorrow's queue today. A full queue is comforting and risky in the same way. Scheduled posts rarely go wrong because they are badly written. They go out on the wrong day because something happened after you scheduled them. Read the next two days of the queue every morning.

How many posts a week? That is your call and your limits. The content calendar generator is a free tool that lays out a month of slots so you can see a rhythm before you commit. For the hours themselves, use the method in our best time to post guide instead of copying a list.

Write posts that survive being scheduled

A scheduled post is read at a time you chose in the past. Words that depend on the moment, such as today, tonight or this morning, are the first to break.

The second post is fine at 4 p.m. on the day. If the plan changes, or the post is edited into the wrong slot, it is wrong for everyone who reads it.

Some posts should never be scheduled far ahead. News, replies to events and anything about people in a bad week belong in the moment. Schedule evergreen and planned posts, and keep a rule that anything time sensitive is posted by a person.

Mistakes we see when people schedule posts

Most scheduling mistakes come from trusting the queue more than it deserves.

• Time words in a scheduled post. "Today", "tonight" and "right now" age badly.
• A slot saved on the wrong clock. It works until the clocks change, then it is an hour out.
• Scheduling and forgetting. No morning check means nobody notices the post that went stale.
• The same post in two slots. It looks like reach. It looks like duplicate content to X.
• Skipping the dry run. The first time you learn where the button is should not be launch day.
• A queue that cannot be paused. When something goes wrong in the world, you need one step to stop it.
• A tool that asks for your password. Walk away.

Your scheduling setup, step by step

You can do this in an afternoon. Do it in this order and the rest of the guide becomes habit.

Start with next week. Schedule the posts you can write in one sitting, read the list back, and look at the queue tomorrow morning. If the routine holds for a month, add more posts. If it does not, schedule fewer.