Mastodon post scheduler

Write it now. Post it later.

Queue posts and publish them at the time you choose.

Sign in with your instance

No sign up. Just your existing Mastodon login.

Why nothing gets stored

  • Official Mastodon API

    Every scheduled post is saved and queued on your own Mastodon instance through its official API.

  • Nothing stored on our end

    There's no TootScheduler database. Your posts and session stay local in your browser, or on your Mastodon instance's own scheduling API once a post is queued.

  • No extra account

    No sign up, no new password. Your existing Mastodon login is all you need. Signing in uses Mastodon's own OAuth flow.

Frequently asked questions

What exactly does TootScheduler store, and where?

Everything lives in your browser's local storage: your session, saved account list, cached instance settings, and any draft that didn't finish saving. There's no TootScheduler server database.

Do my posts or images ever pass through a TootScheduler server?

No. Every request, including scheduling a post and uploading an image, goes straight from your browser to your own Mastodon instance's API. The scheduled post itself is queued and published by your Mastodon instance too, not by TootScheduler. TootScheduler never sees or holds the content.

What happens when I sign out?

Your session is removed from your browser. There's nothing to delete on our side, because nothing was stored there.

Which Mastodon servers work with TootScheduler?

Any server that implements the standard Mastodon API, including scheduled statuses and media upload. If your instance runs plain Mastodon, it should work out of the box.

What if my instance blocks third party apps?

TootScheduler needs your instance to allow OAuth app registration, the same permission any Mastodon app needs. Check with your instance admin if sign in is not allowed.

Can I use more than one account?

Yes. TootScheduler remembers multiple signed in accounts and lets you switch between them from the account menu.

What happens if I revoke access from my instance's settings?

TootScheduler's session for that account stops working right away. Sign in again whenever you want to reconnect.

How far in advance can I schedule a post?

As far ahead as your instance allows. Mastodon requires at least five minutes of lead time for any scheduled post.

Can I edit or cancel a scheduled post?

You can edit the content, time, or any other setting right up until about fifteen minutes before it's due to go out. From twenty to fifteen minutes before, you'll see a warning but editing still works normally. Inside that final fifteen minute window, editing locks so a save can't collide with the post firing. Canceling is different: deleting a scheduled post works at any time, even inside that final window, since removing it doesn't carry the same risk.

What time zone are scheduled times in?

The time you pick uses your device's local time zone.

Is there a limit to how many posts I can schedule?

Yes, set by Mastodon itself, not by TootScheduler. The default is 300 scheduled posts total and 25 per day, per account. TootScheduler shows this as an informational hint, not a hard rule, since exact limits can vary by server.

Is TootScheduler really free?

Yes, and there are no plans to charge for it.

What do "instance," "OAuth" and "content warning" mean?

An instance is the Mastodon server your account lives on (e.g. mastodon.social). You sign in with the one you already use. OAuth is the standard, secure sign-in method it uses: you approve TootScheduler on your instance's own site, and TootScheduler never sees your password. A content warning is optional text shown before a post's content, so readers can choose whether to expand it.

Ready to plan your first post?

Enter your instance domain and you're ready to queue your first post.

Sign in with your instance