How to schedule Mastodon posts on the right instance
Connect your Mastodon instance, preserve visibility and content warnings, and verify a scheduled post without creating duplicates.
A Mastodon scheduler needs to work with the server your account is on, not just with “Mastodon” in general. Before you plan a campaign, find out where the draft waits, who can read it, and how you’ll check the result. This guide gives you a first-post test you can repeat and a record you can reuse.
Identify the account and its server
Write down your full account address (such as @name@example.social) and the server you sign in to. Seeing a profile through another server doesn’t mean it lives there. Open your own profile while signed in and confirm it’s the right account before you connect a publishing tool.
Keep a short connection record: account, server address, tool name and test date. Check the server’s rules and the tool’s list of supported servers. Software that works with Mastodon, and servers with custom settings, can behave differently. A test that works on one server doesn’t prove it works on all of them.
Connect and locate the scheduling queue
Follow the tool’s sign-in steps and check which account is shown before you approve access. Keep passwords and tokens out of your planning documents. After connecting, check that the editor picks the right account, especially if you manage both personal and project profiles.
Find out where the scheduled post is stored. Mastodon itself can hold scheduled posts through its publishing API, while other tools may keep their own queue and send the post later. These work differently. Find out where you can edit or cancel the scheduled post, and whether your device needs to stay on.
Preserve the audience and context
Prepare a useful test, such as a workshop reminder with a working registration link. Check its visibility, language, content warning and image description one by one. Mastodon’s posting guide explains the network’s options; then check which ones your scheduler actually offers.
Don’t assume your account’s default settings apply to this draft. If you need a limited audience or a warning that your tool can’t keep, use an app that can. Check mentions against the full account address. Preview custom emoji and formatting on your actual server, too.
Save an explicit date and timezone
Write down, for example, 16 October 2026 at 09:00, Europe/London, next to the event time in your post. When the post goes out and when the workshop starts are two different things. Make both clear for your audience instead of writing a vague “tomorrow morning”.
Save the schedule, close the editor and open the post again. Check the date, timezone, account and attachment. If the event details change later, update both the scheduled post and the linked page. A correct schedule won’t help if the registration page is out of date.
Run one complete publication test
Use a low-risk post with the same kind of content as your planned campaign. After the scheduled time, check it on your account’s own server. Save its link, check the image description and open the registration link. For a public post, also check what someone who isn’t signed in can see. For a post with limited visibility, ask someone in the intended audience to check it.
Compare what you see with the saved draft. Note any layout changes, unexpected warnings or missing attachments. Fix your process before you add a week of posts. Write down the tool and test date, so you have something to compare against if the server or app changes later.
Troubleshoot the missing result
If the post doesn’t show up on another server’s timeline, check your own profile and the post link first. Posts can take time to reach other servers, so that alone doesn’t mean publishing failed. If the post is also missing from your profile, check the right queue, the connection and any media or server error. Check before you retry, so you don’t post twice.
Use the failure checklist when you’re not sure what happened. Studio by Reunified schedules posts to Mastodon alongside Bluesky, Misskey and other networks, with the wording adjusted for each one. It isn’t available yet, but you can join the waitlist. To adapt the same idea for other networks, continue with the cross-posting guide.
