Schedule your toots without spending a cent

Let us clear up the thing everyone trips on first. Mastodon’s API has accepted a scheduled_at parameter on the normal status-posting endpoint for a long time. You hand it an ISO 8601 timestamp at least five minutes in the future, and instead of publishing straight away, your server holds the post and fires it for you at that moment, even while your laptop is shut. Pending posts can be listed, edited, or cancelled through the scheduled-statuses endpoints. That is the engine underneath every free method we are about to describe, and it is worth understanding because it explains both the generosity and the limits of what you get for nothing.

Here is where it gets confusing, so we will hedge honestly. Whether you ever see a schedule button depends entirely on which client you open. Some third-party Mastodon apps and web clients surface a clock or calendar icon in the compose box that writes to that API for you. The official web interface and official mobile apps, in our experience, have not reliably exposed it, so do not assume the feature is missing just because your app hides it — and do not assume it is present just because a blog post shows a screenshot. Check your own compose window before you conclude anything.

The free picture, then, is a small toolkit rather than a single product. You can reach the native scheduler through a client that exposes it, through a few lines of script if you are technical, or through the free tier of a scheduling service that talks to the same endpoints on your behalf and adds a calendar you can actually read. Each is free in a different way, and each stops at a different wall. The rest of this guide is really about matching those walls to how often you post.

Start with the lowest-effort option: a Mastodon client that already carries scheduling. If the app you prefer shows a scheduling control in its composer, you are done — write the toot, pick a time, and it lands in your scheduled queue. This costs nothing beyond the app itself and keeps you inside the Mastodon ecosystem, which many people here value on principle. The trade-off is that you are limited to whatever that one client chose to build, and scheduling tends to be bare: one post, one time, no recurrence.

The second path is the raw API, for people who do not mind a terminal. Because scheduled_at is a documented parameter, a short script or a scheduled job on your own machine can queue toots and even clear out pending ones. We would reach for this only if you enjoy that sort of thing; it is powerful, free, and completely unforgiving of a mistyped timestamp. Treat it as a hobbyist’s route rather than a team workflow.

The third path, and the one most small accounts settle on, is the free tier of a scheduling tool. A service like SocialBlaze connects to your Mastodon account and gives you a visual calendar, a composer, and a queue that publishes automatically — the things native scheduling leaves out. SocialBlaze is an organic scheduling and analytics tool, so what you are buying (or in this case, not buying) is time and tidiness, not reach. The free tier will cap something — typically the number of connected accounts or scheduled posts in flight — so read the current limits before you lean on it, rather than trusting a number you read in an old guide.

The honest test of a free setup is not what it can do on day one but whether it quietly starts costing you time. For a while, scheduling a single post from a client or a free tier feels like a win. Then you notice the friction: you are opening three different places to plan a week, you cannot see your upcoming toots on one calendar, or you keep forgetting the five-minute minimum and watching a post fail. Those are the signals that free has done its job and you have outgrown it.

We would watch three things specifically. First, volume — the moment you are scheduling more posts than a bare client comfortably lists, a calendar view stops being a luxury. Second, consistency — if you are missing days because planning is scattered, a single queue that publishes on its own is worth more than the money it costs. Third, measurement — native scheduling tells you nothing about what landed; if you want to see which toots actually drew replies and boosts, you need a tool that reports it. SocialBlaze pairs organic scheduling with analytics for exactly that reason.

None of this means you should pay before you need to. The right order is to run free until it pinches, then upgrade the one thing that pinches — usually the calendar and the automatic queue — and leave the rest alone. A small account that posts a few times a week may never need more than the free tier, and that is a perfectly good outcome. Spend the money only when the time you save is worth more than the money you keep.

A free setup rewards rhythm over volume. Here is a light week we would actually keep up, anchored on Tuesday because that is when we find Mastodon timelines are busy but not frantic. Nothing here needs a paid plan.

Week 1: Set the foundation

Spend this week getting the free machinery working rather than posting a lot. Connect your Mastodon account to whichever free path you chose — a scheduling client or a free-tier tool like SocialBlaze — and send one test post scheduled ten minutes out to confirm it fires. Write and pin an intro post that says who you are and what you post. Fill in your bio, add a header image, and put your link in the profile fields where Mastodon lets you verify it. Follow fifteen accounts in your niche so your timelines have life. By Friday you should have one scheduled post land successfully; that single proof is the whole goal of the week.

Week 2: Build the rhythm

Now use the schedule in earnest. Queue your anchor post for Tuesday and two lighter toots across the week, exactly as the seven-day plan lays out. The point is to feel what it is like to plan a few days ahead rather than posting on impulse. Pay attention to the five-minute minimum — if a post ever fails, this is almost always why. Keep replying and boosting daily; scheduling handles your output, but the network rewards presence, and a queue cannot fake that. End the week by glancing back at which toot drew the most replies, even if you are only eyeballing it for now.

Week 3: Tighten and observe

Keep the rhythm steady and start paying attention to timing. Try moving your anchor post an hour earlier or later and see whether replies shift. Add alt text to every image as a habit, not an afterthought — Mastodon’s culture takes accessibility seriously, and it widens who can engage with you. If you are on a free tool with a calendar, use this week to plan all of next week in one sitting so you can see gaps and clusters at a glance. If you are on a bare client, notice how much harder that planning is; that friction is data about whether you will want more later.

Week 4: Decide what free is worth

By now you know whether your free setup is carrying you or quietly costing you time. Review honestly: are you posting consistently, or missing days because planning is scattered across apps? Can you see your week on one screen, or are you guessing? If free still fits, wonderful — keep going and do not pay for capacity you are not using. If it pinches, upgrade the single thing that pinches, usually the calendar and the automatic queue, and leave the rest. A paid organic tool like SocialBlaze earns its place only when the time it saves beats the money it costs; this week is where you make that call with evidence instead of a hunch.