How to Schedule Tweets in 2026: Native Limits, API Pricing, and the 18-Month Trick

Short answer: yes, X still lets you schedule posts for free, natively, up to 18 months in advance. That part hasn't changed in years. What has changed is everything around it: the API now charges per post with no free tier at all, and the native scheduler quietly refuses to touch anything longer than 280 characters.

If you're looking for how to schedule tweets in 2026 without getting burned by either of those two facts, here's the complete, current picture.

What you need

• An X account, logged in on web or desktop. The mobile apps cannot schedule posts natively, full stop.
• An X Premium subscription if you want to write and schedule posts longer than 280 characters, and even then, read the long-form section below before you assume that works.
• A Developer Portal project and a paid API tier if you want to post programmatically instead of through the composer. There is no free way in anymore.
• A tool like TimeToPost if you want scheduling that isn't limited to one browser tab, one account, or one platform.

Native scheduling: 18 months ahead, web only, the long-form gap

X's native scheduler lives inside the normal composer. Click the clock icon, pick a date and time, and the post drops into a queue X calls Unsent posts. You can schedule as far out as 18 months, which is more headroom than almost any other platform's native tool offers, and it's genuinely free.

The catch is where it works. Scheduling is a web and desktop feature only. Open the composer on the iOS or Android app and the clock icon simply isn't there. If your workflow is "write it on my phone at 11pm," native scheduling was never built for you.

The second catch is length. If you're on Premium and writing a long-form post over 280 characters, the native scheduler currently will not schedule or draft it on web. You can publish a long post immediately, but you can't queue one up ahead of time through X's own tools. For long-form content on a calendar, you're back to either posting live or handling it through the API yourself.

So: schedule tweets free and native, yes, up to a year and a half out, as long as you're on a computer and staying under 280 characters. Outside those lines, native scheduling stops helping you.

Scheduling through the API and what it costs now

This is the part that changed hardest in 2026. On February 6, 2026, X moved posting on the API to pay-per-use pricing, and there is no free tier left for it. Every post you send through POST /2/tweets now costs $0.015, or $0.20 if the post includes a link.

The older subscription tiers didn't disappear cleanly either. Basic ($200/month) and Pro ($5,000/month) are both closed to new signups, and existing Basic subscribers were migrated onto the pay-per-use model starting June 1, 2026. If you built an integration on the old Basic tier expecting a flat monthly rate, that rate is gone.

The endpoint itself is unchanged: POST /2/tweets still takes a JSON body with your post text, and the rate limits are still 10,000 requests per 24 hours per app and 100 requests per 15 minutes per user. What's different is that every one of those requests now has a line-item cost attached to it.

If you want the full build-it-yourself path, auth flow and all, that's covered step by step in how to post to X (Twitter) via the API. This post is about the scheduling decision, not the integration code, so I'll leave the wiring to that guide.

See how TimeToPost can help you implement these strategies.

Scheduling with TimeToPost

If the per-post API pricing above made you wince, that's the honest reaction. It's why most people scheduling more than a handful of tweets a week don't want to own that billing relationship directly.

TimeToPost connects to X in about two clicks, no developer account or Developer Portal project required on your end. Once it's connected, you get a real calendar for your X posts alongside every other platform you're on, a live character counter so you're not guessing whether you're over 280, and optimal-time suggestions built from actual engagement data rather than a blog post from 2019. You write once, schedule it into the calendar, and it fires at the right time whether that's tonight or six months out, on desktop or from your phone, which native scheduling still can't do.

There's a dedicated X (Twitter) scheduler page if you want the specifics of how the connection works, and the character counter is free to use standalone if you just want a quick length check before you post.

Limits: 280 free, 25,000 Premium characters, and the posting rate limits that matter

Here's the full set of x native post scheduling limits and API limits in one place:

| Limit | Value | |---|---| | Post length, free account | 280 characters | | Post length, Premium (long-form) | up to 25,000 characters | | Native scheduler, how far ahead | up to 18 months | | Native scheduler platform | web/desktop only, no mobile app | | Native scheduler and long-form posts | not supported, can't schedule or draft over 280 chars on web | | API posting cost (since Feb 6, 2026) | $0.015/post, $0.20/post with a link | | API rate limit, per app | 10,000 requests/24h | | API rate limit, per user | 100 requests/15 min |

The gap worth remembering: Premium buys you up to 25,000 characters to write with, but it doesn't buy you the ability to schedule those longer posts natively. That mismatch trips up a lot of people who assume paying for Premium unlocks the full feature set everywhere in the product.

Best time to post on X

Timing on X is less forgiving than most platforms because the feed moves fast and older posts fall out of view within hours, not days. There's no single "best hour" that holds across accounts, industries, or audiences, so treat any chart claiming otherwise skeptically. What actually works is looking at when your own followers are active and posting into that window consistently. We break down how to build that picture properly, including the data sources worth trusting, in best time to post in 2026.

FAQ

Can I schedule tweets from my phone? No. Native scheduling through X's Unsent posts feature only appears in the web and desktop composer. The mobile apps don't expose it.

Can I schedule a thread? X's native scheduler is built around single posts. If you're assembling a full thread, most people write and schedule the first post through native tools and add replies manually near the fire time, or use a scheduling tool built to hold a full thread together and post it as a sequence.

Is there still a free tier for the X API? No. As of February 6, 2026, every post sent through the API is billed per post, at $0.015 (or $0.20 with a link). The old free tier and the flat-rate Basic and Pro subscriptions are closed to new signups.

Can I schedule long posts over 280 characters? Not through X's native scheduler, even with Premium. Long-form posts over 280 characters can be published immediately but currently can't be scheduled or saved as drafts on web. Scheduling long-form content ahead of time means routing it through the API yourself or through a scheduling tool that handles that for you.