How to Schedule Mastodon Posts

Step by step

1. 1

   Connect your Mastodon account to SocialKit

   In SocialKit, open the accounts or connections section (look for an "Add account" or "Connect a network" option — exact wording may vary as of June 2026). Select Mastodon from the list of 11 platforms. You will be prompted to enter your instance URL (for example, mastodon.social). SocialKit then redirects you to that instance's official OAuth authorization screen, where you log in and approve the requested permissions.

   Tip: Double-check the instance URL — mastodon.social and mas.to are different servers. If you have accounts on multiple instances, repeat this step for each one; SocialKit can manage them side by side from one dashboard.

2. 2

   Open the composer and write your post

   In SocialKit’s composer, select your connected Mastodon account and write your post. As of June 2026, the default character limit on most Mastodon instances is 500 characters, though many instances raise this — check your specific server’s limit with the free Mastodon character counter if you are unsure. You can attach images (up to four on most instances) and alt text is strongly encouraged in the fediverse community.

   Tip: The fediverse values context: if your post covers sensitive topics, set the content warning (CW) field inside SocialKit’s composer so followers can opt in. Instance behavior for CWs can vary, so confirm your first CW post displays as expected on your instance.

3. 3

   Set visibility and audience options

   Mastodon lets you control who sees each post: Public (federated timeline), Unlisted (followers + direct link), Followers Only, or Mentioned Only. As of June 2026, SocialKit passes the visibility setting you choose in the composer through to the Mastodon API. For scheduled promotional posts, Public is typical; for community-specific content, Unlisted keeps it off the federated firehose.

4. 4

   Pick a posting time using best-time data

   Select a date and time for your post. Because Mastodon does not have a single global algorithm, engagement patterns depend on when your instance’s local timeline is active and when the accounts you want to reach are online. Use SocialKit’s best-time insights as a starting point — visit the Mastodon best-time page for general patterns — then refine based on your own analytics over time.

   Tip: Fediverse audiences tend to skew toward Europe and specific timezone clusters; general social media peak times may not apply. Let two or three weeks of data guide your optimal slots rather than assuming peak Instagram times carry over.

5. 5

   Schedule the post (or add it to your queue)

   Choose "Schedule" to lock in the specific date and time, or add the post to your queue if you have recurring time slots configured. SocialKit will publish the post to your Mastodon instance automatically at the scheduled time via the API. As of June 2026, text and image posts publish automatically; always send a low-stakes test post first to confirm the connection is working on your specific instance.

6. 6

   Optionally cross-post to Bluesky, X, Threads, or LinkedIn

   If you want the same content distributed beyond Mastodon, toggle on additional platforms in the composer before scheduling. Each network has a different character limit — Bluesky is 300 graphemes, X (Twitter) is 280 characters for standard accounts (higher for Premium), Threads is 500 characters — so SocialKit lets you customize the copy per platform before it goes out. Cross-posting does not require leaving the composer.

   Tip: Mastodon posts often use CWs or hashtag conventions that do not translate well to other networks — take a moment to review the per-platform variant and strip fediverse-specific formatting before scheduling to non-Mastodon accounts.

7. 7

   Verify in the calendar and review after publishing

   After scheduling, the post appears on SocialKit’s calendar view. You can drag it to a new time slot, edit the copy, or delete it before the scheduled time. Once published, check the post on your Mastodon instance to confirm visibility settings, alt text, and content warnings rendered as intended.

Best practices

• Write alt text for every image — it is standard fediverse etiquette and improves accessibility, and many Mastodon communities specifically call out posts that skip it.
• Use content warnings (CWs) for anything political, sensitive, or spoiler-adjacent; they are a genuine community norm on Mastodon, not just a feature flag.
• Post at a consistent cadence rather than in bursts — the chronological Mastodon timeline rewards steady contributors, and irregular flood-posting can frustrate followers who follow you for specific topics.
• Include relevant hashtags (typically 2–5 in the post body or at the end) because on default Mastodon, hashtags are the primary discovery axis — full-text search is opt-in and not enabled on every instance as of June 2026.
• Use the free Mastodon character counter to draft within your instance's limit before opening the composer, especially if your instance raises the default above 500 characters.
• Treat per-instance analytics as your benchmark: what performs on a tech-focused instance like fosstodon.org may differ significantly from a general-purpose server — check SocialKit's analytics per account rather than aggregating across instances.

Good to know

Do it in SocialKit