SkyyCast

Home / Blog / Bluesky Platform & Feeds / Bluesky Follow Limits and Rate Limits, Explained

Social Media

Bluesky Follow Limits and Rate Limits, Explained

Bluesky has no hard limit on how many accounts you can follow, and no daily follow cap. What it has is a rate limit — a shared hourly budget for actions — that a person using the app normally will never reach. Most of the “Bluesky follow limit” advice online is either copied from old Twitter or invented. Here is the actual mechanism, and which numbers to ignore.

Two-panel explainer of Bluesky limits: there is no follow cap, only one shared hourly rate limit, and the kinds of automated use that actually reach it.

There is no follow cap

Bluesky's documentation does not define a maximum number of accounts you can follow, or a limit on follows per day. The “5,000 follows” figure that turns up in guides is Twitter's old rule; a community proposal to add a similar cap to Bluesky was raised in late 2024 and never adopted. The “10,000” number some posts cite is not a Bluesky limit either. The design reason is consistency with the rest of Bluesky: it limits how fast you can act, not how much you can accumulate, so a large, slowly built account is never penalised for its size.

What actually limits you: the rate limit

Bluesky's rate-limit documentation defines a points system for creating records. Each new record costs 3 points, and your account gets 5,000 points an hour and 35,000 a day. That works out to roughly 1,666 new records per hour and about 11,666 per day. A follow is a record. So is a like, a repost, a post, a reply, a block, and a list edit — each one costs the same 3 points, and they all draw from the same bucket. Bluesky describes the thresholds as set to “accommodate high-activity human users while restricting prolific automated bots” — the ceiling is aimed at scripts, not people.

There are a couple of other limits alongside it: about 3,000 requests every five minutes from a single IP address, and small dedicated caps on sensitive actions — roughly thirty logins per five minutes, and ten handle changes per five minutes with fifty per day. Cross any limit and the response is an HTTP 429, “Too Many Requests”; you wait for the window to reset. Unless you are scripting sign-ins, you will never see the sensitive-action caps.

You will not hit this by hand

Sixteen hundred actions an hour is one action roughly every two seconds, kept up for the full hour. Ordinary posting, liking, and following does not come close — a normal week of activity is a rounding error against the daily budget. Even someone doom-scrolling and liking everything for hours is spending a few hundred points, not thousands. The accounts that see a rate-limit error are, almost always, running something automated.

A heavy human day, in numbers

Say you have an unusually active day: forty original posts, two hundred likes, sixty reposts, thirty replies, and eighty new follows. That is 410 new records, or about 1,230 points — against a daily budget of 35,000. You have used roughly three and a half percent of it. To exhaust the daily limit by hand you would need to create a record every seven or eight seconds, without stopping, for eight hours.

When people actually hit it

The common causes are all tools doing many things quickly:

  • A scheduling or cross-posting tool firing a large batch of queued posts, threads, or reposts at once. If a scheduling tool returns a rate-limit error, it queued too much too close together.
  • Importing a big list — subscribing to a large block or mute list adds a record for each account, and a very large one can spend your hourly budget in a burst.
  • A growth tool mass-following hundreds of accounts to farm follow-backs.
  • A misbehaving client polling the API far more often than it needs to.

In every case the fix is the same: slow the tool down, or wait an hour for the budget to refill. There is nothing wrong with your account, and nothing to appeal.

If you want to know how long to wait, the API returns headers on every response showing how much budget is left and when it resets; a well-built tool reads those and backs off on its own. In the app, an hour is always enough.

Follow limits and the spam question

Even with no hard cap, mass-following is a poor tactic. It spends your whole rate budget on one activity, and Bluesky's Community Guidelines prohibit artificially manipulating social signals to gain unearned reach — which is a moderation matter, decided case by case, not a number you can stay under. Some third-party guides state that 50 to 100 follows in an hour triggers a temporary block; that figure is not in Bluesky's documentation, so treat it as an unverified rule of thumb rather than a real threshold.

If you have a legitimate reason to do a lot at once

Migrating an account, cleaning up years of follows, or importing a curated list are all fine reasons to perform a lot of actions. Do them in chunks spread across a few hours rather than one run, and if you get a 429, stop and wait for the hourly window to reset instead of retrying straight away — repeated retries just keep you rate-limited.

Bottom line

There is no follow cap on Bluesky. There is a shared hourly action budget of a few thousand records that only automated tools reach. The limits exist so a bot cannot drown the network, and for anyone posting like a person they are invisible. If you ever see “rate limit exceeded,” it is the tool, not your account — slow down, wait an hour, and carry on.

Schedule your next Bluesky post

Write it once, pick a time, and let SkyyCast publish it for you.

Get Started