Mastodon Scheduling, Properly Explained

Mastodon has a scheduler. You have probably never seen it, because the official web interface and the official apps do not expose it. The capability sits in the API, has done for years, and accepts a publish time with a minimum lead of five minutes. Whether you can reach it depends entirely on which client you use.

That gap is the whole reason this guide exists. Scheduling on Mastodon is not a missing feature you work around, it is an existing feature you route around. Understanding that changes how you pick a tool, and it changes what you can reasonably expect once you have one.

There is no single Mastodon. There are thousands of independently run servers, each with its own administrator, its own moderators, its own rules and its own configuration. When people talk about Mastodon behaving a certain way, they usually mean their server behaves that way. Two things this changes immediately:

Five hundred characters is the default, not the law. Administrators can raise it, and many do, with some instances running to a thousand or considerably more. Before you build a writing habit around a number, check what your own server actually allows. If you cross-post to networks with tighter limits, write to the tightest one and you never have to think about it again.

Links are the exception worth memorising: Mastodon counts every URL as a flat twenty-three characters regardless of how long it really is. Link shorteners buy you nothing here, and they make a post look faintly like spam, so paste the full address.

Some instances welcome automated posting. Some ban it. Some permit it only if you also participate in conversation, and some prohibit accounts that broadcast without ever replying. These are enforced by volunteers who will not be persuaded that your marketing calendar is an exception. Read the rules of your home server before you queue a month of content, and if your posting style genuinely conflicts with the culture there, move to a server that fits rather than argue.

Because the official clients will not help you, every practical route goes through something that speaks to the API directly.

PostSpoke connects this way: you give it your instance domain and it registers dynamically against your server, so there is no developer account to apply for and no waiting on anyone to approve an app. That matters more on Mastodon than elsewhere, because a tool that only supports a handful of big instances is no use if you are on a small one.

Mastodon gives you a free-text content warning field. You write a short label, the post collapses behind it, and readers choose whether to expand. There is a strong tradition of using one for emotive subjects such as politics and religion, on top of the obvious cases: distressing news, spoilers, and anything not safe for work.

Treat it as an accessibility feature rather than a punishment. A content warning makes your post readable by people who would otherwise scroll straight past, and it costs you a few words. Worth knowing if you cross-post: this field has no equivalent on most other networks, so it will not survive an automated pipeline. If your subject matter regularly needs one, write the Mastodon version by hand.

The Fediverse treats image descriptions as a baseline courtesy, not a bonus. The norm is strong enough that there is an established convention where people who cannot write their own descriptions ask publicly for help and strangers write one for them. Posting undescribed images repeatedly gets noticed.

The practical warning for anyone automating: many pipelines drop alt text silently. If an image carries the meaning of the post rather than decorating it, and you have not confirmed your tool passes descriptions through, publish that one by hand.

Most instances do not index full-text search by default, which makes hashtags the actual discovery mechanism rather than decoration. Two or three relevant tags, written in CamelCase so screen readers can pronounce them properly. This is the opposite of the advice you would give for a network with real search, where a stack of hashtags just looks like imported marketing.

If you also publish to Bluesky, Ghost, Substack, Dev.to or Telegram, PostSpoke will queue Mastodon alongside them from one composer and one calendar, which removes the retyping without removing your judgement about what each place should see. It is free during the current public beta.

None of this is complicated, but it is specific. Mastodon rewards people who learn the local conventions and quietly punishes people who arrive with a content calendar and no interest in the neighbourhood. The scheduling is the easy half.