Schedule toots across the fediverse
A Mastodon scheduler is coming to PostQued. Queue toots to any instance — with content warnings, alt text, and per-post visibility — then let us auto-publish through Mastodon's official API. Join the waitlist and we'll email you the moment it's live.
TikTok is live today — schedule TikToks now. Mastodon is next.
What you'll be able to do
Built for how the fediverse actually works
Any instance, one queue
Connect accounts from mastodon.social, fosstodon.org, your own self-hosted server — and schedule toots to all of them from a single calendar.
Content warnings built in
Set a CW on any scheduled toot so sensitive topics stay folded behind a spoiler, the way the fediverse expects.
Alt text on every image
Write descriptive image descriptions when you schedule. Mastodon's accessibility-first culture is a feature here, not an afterthought.
Per-toot visibility
Queue public, unlisted, or followers-only posts. Plan a thread for everyone and a reply for your followers — all in advance.
Official Mastodon API
Publishing runs on Mastodon's standards-based REST API with a token you authorize yourself. No scraping, no password sharing.
Bots, scripts & MCP
Automate toots from a backend job, a feed bot, or an AI agent with one static API key — fediverse automation done cleanly.
Why schedule Mastodon
A chronological, decentralized network rewards planning
Reach a global, timezone-spread fediverse
Mastodon has no algorithmic feed — toots surface chronologically. Scheduling lets you land posts when your followers' home timelines are actually awake, across servers and timezones.
Stay consistent without living in the app
Privacy-minded communities reward steady, thoughtful posting over engagement-bait. Queue a week of toots, boosts of your own threads, and announcements so you show up reliably.
Cross-post your fediverse presence
Run a project account, a personal account, and a community server account at once. Schedule each from one place instead of logging into three different instance web UIs.
FAQ
Mastodon scheduling questions
Will I be able to schedule toots across different Mastodon instances?
Yes. Because the fediverse is decentralized, your account can live on mastodon.social, fosstodon.org, your own self-hosted server, or anywhere else. PostQued will let you connect accounts from any instance and queue toots to publish on whichever home server you belong to.
How will PostQued publish to Mastodon?
Through Mastodon's official REST API using an application access token you authorize on your own instance. No password sharing, no scraping — just native, standards-based publishing to your timeline.
Can I schedule a content warning, alt text, and visibility per toot?
That's the plan. Mastodon culture takes CWs, descriptive image alt text, and post visibility (public, unlisted, followers-only) seriously. PostQued will let you set all three when you schedule, so every queued toot respects fediverse norms.
Does Mastodon have a built-in scheduler already?
Mastodon's API supports scheduled statuses, but managing them across multiple accounts and instances from a web client is clunky. PostQued gives you one calendar for every account, plus bulk scheduling and an API — no jumping between instance web UIs.
Will there be a Mastodon scheduling API for developers?
Yes. PostQued is API-first. When Mastodon support ships, you'll be able to queue toots from scripts, backend jobs, no-code tools, or AI agents with a single static API key — including over MCP.
How much will PostQued cost when Mastodon goes live?
A flat $20/month for unlimited accounts and unlimited scheduled posts across every platform we support — no per-instance or per-toot fees. Join the waitlist and you'll be the first to know when Mastodon launches.
Coming soon to PostQued
Be first to schedule on Mastodon
Mastodon scheduling is on the way — one queue for every instance, at a flat $20/month when it launches. Join the waitlist and we'll email you the moment it's live.