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 tokens don't 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 Platforms page in PostRite
  3. Click Connect on the Mastodon card
  4. Enter your instance (e.g. mastodon.social) and paste the access token
  5. Click Connect to save

Any Instance Works

mastodon.social, fosstodon.org, a regional server, or your own self-hosted instance — PostRite talks 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
  • Links, hashtags, and mentions — parsed natively by Mastodon
  • Scheduled and immediate publishing
  • Retry-safe publishing (a retried post is never duplicated)

Best Practices

  • Post consistently: Mastodon feeds are chronological — 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 — descriptive image posts perform better
  • Mind your instance's limits: some instances raise or lower the 500-character default and media size caps

Troubleshooting

Connection fails

  • Check the instance URL is where your account actually lives
  • 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: posts over the instance's character limit or media size cap are rejected by the instance — 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