PostRite

Mastodon

Connect your Mastodon account with an application access token to schedule posts to your profile, on any instance.

How It Works

PostRite connects to Mastodon through an application you create on your own instance. The application's access token lets PostRite publish on your behalf. Your account password is never shared, and the token does not expire: access lasts until you delete the application.

Creating an Application

  1. Sign in to your instance (e.g. mastodon.social)
  2. Open Preferences → Development → New application
  3. Name it (e.g. "PostRite") and grant these scopes: write:statuses, write:media, read:accounts
  4. Save, open the application, and copy Your access token

Keep Your Token Secret

Anyone with the access token can post as you. If it leaks, delete the application on your instance. That revokes the token immediately.

Connecting to PostRite

  1. Create the application (see above)
  2. Go to the Connected accounts page in PostRite
  3. Click Connect on the Mastodon card
  4. Enter the instance domain (e.g. mastodon.social) or any URL from it, such as your profile page or the applications page. PostRite keeps only the instance address. Then paste the access token
  5. Click Connect Account to save

Any Instance Works

mastodon.social, fosstodon.org, a regional server, or your own self-hosted instance all work. PostRite talks directly to the instance you connect, so federation limits never get in the way.

Supported Features

  • Text posts up to 500 characters (the fediverse default)
  • Up to 4 images, or one video per post (images and a video cannot be mixed)
  • Links, hashtags, and mentions, parsed natively by Mastodon
  • Scheduled and immediate publishing
  • Retry-safe publishing (a retried post is never duplicated)
  • Post visibility (public, unlisted, followers only, mentioned only)
  • Content warnings
  • Post language
  • Alternative text on images, written once in your media library
Mastodon options appear in the editor once the account is selected.
The post editor with a Mastodon account selected, showing visibility, content warning and language next to the Mastodon preview

Best Practices

  • Post consistently: Mastodon feeds are chronological, so regular posting is what builds reach
  • Use hashtags generously: they are the main discovery mechanism across the fediverse
  • Add alt text culture: the fediverse values accessibility, and image posts with descriptions perform better
  • Mind your instance's limits: some instances raise or lower the 500-character default and media size caps

Troubleshooting

Connection fails

  • Check that the instance is the one where your account lives
  • Check that the instance address is spelled correctly. PostRite cannot connect if the instance is unreachable or is not a Mastodon server
  • Make sure the application has the read:accounts scope (used to validate the token)
  • If you deleted the application, create a new one and reconnect

Post fails to publish

When publishing fails, PostRite shows the specific reason on the failed post. Common causes:

  • Missing scopes: the application needs write:statuses and write:media
  • Instance limits: the instance rejects posts over its character limit or media size cap. The error message shows the exact limit
  • Video processing: videos are transcoded by the instance after upload; if processing is slow, PostRite retries automatically
  • Rate limited: instances limit how fast an account can post. PostRite waits and retries automatically
BlueskyProfile Settings