How to Fix Mastodon Error ‘Maximum Number of Boosts Reached’

When you try to boost a post on Mastodon, the system may stop you with the error message: Maximum number of boosts reached. This error appears because Mastodon enforces a daily rate limit on the number of boosts a single user account can perform within a 24-hour window. The limit exists to prevent spam and excessive server load. This article explains why the limit exists, how to check your current boost count, what the exact limit is on most instances, and what to do if you need to boost more posts.

Why Mastodon Limits Boosts Per Day

Mastodon instances apply a rate limit to boosts to protect server performance and reduce spam. Each boost creates a new copy of the original post on your server. When one user boosts hundreds of posts in a short time, the server must replicate and distribute those posts to followers on other instances. This consumes bandwidth and database resources. The limit also discourages automated accounts or bots from amplifying content at scale. Instance administrators can adjust the boost limit in the server configuration file. The default value on most instances is 50 to 100 boosts per account per rolling 24-hour window. The count starts from the moment you perform your first boost of the day.

The limit applies only to boosts, not to original posts or replies. You can still create new posts and reply to others without restriction. The error message appears only when you try to boost a post after exceeding the limit. The system does not warn you before you reach the limit. You will see the error as a red banner at the top of the web interface or as a plain text message in third-party apps.

Boost Limit vs Other Rate Limits

Mastodon also applies rate limits to other actions. Following many accounts in a short time, posting too many messages, or sending too many direct messages can also trigger separate limits. The boost limit is independent of these. Exceeding the boost limit does not affect your ability to post, reply, or follow accounts.

Steps to Check Your Current Boost Count and Wait for Reset

1. Open Mastodon web settings
   Log in to your Mastodon instance using a web browser. Click the gear icon in the right sidebar or navigate directly to Preferences.
2. Go to Moderation > Account notes
   In the left navigation menu, click Moderation. Then click Account notes. This page shows a log of your account actions, including boosts, follows, and other activities. The number of boosts you have performed today appears in the list.
3. Identify your boost count
   Look for entries labeled boost. Count how many boost entries appear within the last 24 hours. Each entry represents one boost. If the count is 50 or higher, you have likely reached the limit.
4. Note the time of your first boost
   Find the earliest boost entry in the list. The limit resets 24 hours after that timestamp. For example, if you boosted your first post at 9:00 AM, the limit resets at 9:00 AM the next day.
5. Wait for the reset or stop boosting
   After you confirm you have reached the limit, wait until the 24-hour window passes. During this time, do not attempt to boost any more posts. The error will disappear automatically after the reset.

If the Error Persists After Waiting

I waited 24 hours but still see the error

The limit resets relative to your first boost timestamp, not at midnight. If you boosted a post at 3:00 PM, the limit resets at 3:00 PM the next day. Check the exact time of your earliest boost in the Account notes log. If you still see the error after the reset, the instance may have a lower limit configured by the administrator. Contact your instance admin to confirm the current limit.

I need to boost more posts than the limit allows

There is no official way to bypass the boost limit on Mastodon. You can ask the instance administrator to raise the limit in the server configuration file. The setting is called max_reblogs_per_day in the Mastodon configuration. Administrators can set any positive integer. Alternatively, you can create a new post that links to the original content instead of boosting it. This does not count toward the boost limit.

Third-party apps show the error incorrectly

Some third-party Mastodon clients do not display the error message correctly. If you see the error on a mobile app but not on the web interface, the app may have a bug. Check the web interface to confirm the actual error status. If the web interface does not show the error, the app is misreporting the limit.

Mastodon Boost Limit vs Other Instance Rate Limits

Item	Boost Limit	Follow Limit	Post Limit
Default daily limit	50 to 100 boosts	30 to 60 follows	300 to 500 posts
Resets after	24 hours from first boost	24 hours from first follow	24 hours from first post
Affects original posts?	No	No	Yes
Configurable by admin?	Yes	Yes	Yes

You can now identify the cause of the Maximum number of boosts reached error, check your current boost count using the Account notes log, and wait for the automatic 24-hour reset. If you frequently need to boost more posts, ask your instance administrator to increase the max_reblogs_per_day setting. As an advanced tip, use the Mastodon API to programmatically monitor your remaining boost allowance by checking the X-RateLimit-Remaining header in API responses.