Twitter scheduler: schedule tweets, schedule Twitter posts, and what automated X posts really cost

Can you schedule posts on Twitter?

Yes, and it is free. X has a built-in scheduler in the post composer: write the post, click the clock icon under the text box, pick a date and time, and confirm. Scheduled posts collect in an unsent-posts drawer where you can edit or delete them before they go out. It costs nothing and it does not require a developer account.

The catch is what it will not do. The clock icon appears only in the web composer on a desktop browser. It takes one post at a time, so there is no bulk upload and no CSV import. It will not queue a thread. And it covers exactly one network, so if you also post to LinkedIn or Instagram you are doing the same job twice in two places. Those four gaps are the honest reason to pay for a social media scheduler rather than a Twitter-only workaround.

Can you schedule tweets from your phone?

Not in the official X app. The schedule button is a web-composer feature and the mobile app does not show it, which is why so many people search for this and conclude the feature was removed. It was not removed; it was never added to mobile.

There are two workarounds that cost nothing. Open x.com in your phone's browser and request the desktop site, which usually restores the composer's clock icon, though it is fiddly on a small screen. Or use any third-party scheduler with a real mobile app, which is the reason a large share of paid Twitter scheduler signups happen at all. If you draft posts on a phone during a commute, this single gap is worth more than every other feature on a vendor's comparison chart.

Can you schedule a thread on X?

Not with X's own scheduler. It accepts a single post and nothing more, so a thread has to be posted live, in order, by hand. Every thread you see published at 6am was either typed at 6am or sent by a third-party tool.

Threads are the clearest paid-tool use case on X, and they are where the X-native products earn their keep. Typefully, Hypefury and Tweet Hunter are all built thread-first, with numbering, previews and the ability to queue a whole thread as one unit. General schedulers such as Buffer and Publer support threads too, but the writing experience is built for a single post first. If threads are your format, write them somewhere designed for them, then let our Twitter thread generator turn a long source asset into the thread in the first place.

What does it cost to post to X automatically?

More than most people expect, and the rate depends on something nobody thinks to check: whether the post contains a link. X's live pricing endpoint returns $0.015 to create a post and $0.200 to create a post containing a URL. That is not a typo and it is not a rounding difference. A link makes the same tweet cost 13 times more to publish through the API.

Read that against how marketers actually post. A plain-text tweet ten times a day costs about $4.50 a month in API fees. Ten link-bearing tweets a day, which is an ordinary cadence for a company driving traffic to a blog, costs $60 a month before anyone has built or maintained the tool that sends them. The table below runs the arithmetic at several cadences, and our X API pricing breakdown publishes the full rate card behind it.

One honest qualification, because it matters. These are the self-serve rates you would pay building your own posting integration or running on pay-per-use. Established vendors negotiate their own agreements with X, so you should not assume Buffer pays $0.20 every time you queue a link. What these rates do explain is the market behaviour you can see from outside: why X is the one network sold as a paid add-on, why several tools quietly dropped X support after 2023, and why a $5 a month flat-rate plan that absorbs variable API cost is a genuinely good deal rather than a commodity.

Why is a scheduled Twitter post not working?

Because of an architectural fact almost no troubleshooting article mentions: your post was never handed to X in advance. Search X's API documentation for the word schedule and the only results concern audio Spaces. There is no scheduling parameter on post creation at all.

So when you set a tweet for Tuesday at 9am in any third-party tool, nothing is stored at X. Your post sits on the vendor's servers, and at 9am on Tuesday their system wakes up and makes a live API call. If the vendor is having an incident at that minute, or your account token has expired, or the post breaks a rule the API rejects, the tweet does not go out and you usually find out later. The practical consequences are worth knowing: check that your account connection has not silently expired after a password change, treat vendor status pages as relevant to your publishing calendar, and for genuinely time-critical posts such as a launch, consider posting by hand.

How do you bulk schedule tweets?

You cannot do it natively. X's scheduler takes one post at a time, so filling a month of posts means opening the composer roughly thirty times. Bulk upload is a paid feature everywhere it exists.

In practice bulk scheduling means one of two things, and vendors are careless about the difference. The first is CSV import: you prepare a spreadsheet with the text, the date and optionally a media URL, and the tool creates the queue in one pass. Publer, Zoho Social, Sendible and SocialBee all support this. The second is a recurring queue, where you fill time slots once and drop posts into them, which suits evergreen content and is how SocialBee's category system and Publer's recycling work. If you are producing the posts as well as scheduling them, our URL to social media posts tool turns one source asset into a batch you can paste straight into either workflow.

Is there a free Twitter scheduler?

Yes, several, and the best of them is X's own. It has no post limit, no trial clock and no upsell, which is more than any free vendor tier offers. Buffer's free plan covers three channels, Publer's covers three accounts, and both keep working indefinitely.

The reason people still pay is that free tiers are shaped to make you upgrade at exactly the point the tool becomes useful: a second person, a second brand, an approval step, analytics that survive a client meeting, or simply the mobile app X does not provide. Typefully's free plan, for instance, allows 10 posts a month against 1,000 on its paid tiers, which is a trial in everything but name. If you are one person on one account posting single tweets from a laptop, the honest answer is that you do not need to spend anything.

What is the best Twitter scheduler?

For a single account posting single tweets from a desktop, X's native scheduler, because nothing connects to X better than X and it is free. That answer covers more people than the roundups admit.

Past that the choice splits by what you are actually doing. If you write threads, the X-native tools built around the thread editor are worth the narrower feature set. If X is one of several networks, a general scheduler is the better buy and the decision becomes billing rather than features, because these products are close on capability and far apart on how they meter it. Buffer at $5 a channel is the cheapest credible paid entry. Zoho Social at $10 a month billed annually is the best value if you run several channels for one brand. Sendible at $35 and Planable at $39 suit agencies because both include unlimited users, so adding a colleague costs nothing. Watch for the one genuine trap on this network specifically: confirm X is included in the tier you are buying rather than sold separately, which is not true everywhere.