Bluesky Post Limit Per Day: The Real Numbers Are Published (Just Not Where You Looked)

You searched "bluesky post limit per day" because you wanted one number, and every blog you opened gave you a paragraph about how Bluesky is decentralized. The number exists. It is published. It is just written in a unit nobody translates for you: points.

Bluesky's own infrastructure documentation lists the ceilings in plain text. Here they are, and here is what they mean the moment you have more than one account to run.

The limit is not counted in posts — it is counted in points

Bluesky's protocol services documentation states the write budget for a single account as 5,000 points per hour and 35,000 points per day. Every write action has a price:

Do the division and the headline number falls out: about 1,666 creates per hour and 11,666 creates per day. That is the answer to "how many posts per day on Bluesky" — and it is so far above human behaviour that if you are asking the question as a creator, the honest answer is you will not hit it.

If a platform's published ceiling is eleven thousand actions a day, that ceiling was not written to stop you. It was written to stop a script that follows every account on the network.

This matters because it reframes the question. The thing that will actually interrupt your day on Bluesky is not the posting cap. It is one of the quieter numbers underneath it.

The number that actually stops multi-account operators: sessions

Buried in the same documentation is a limit almost nobody quotes: session creation is capped at 30 per 5 minutes and 300 per day, per account. A "session" is a login. Every time a tool authenticates as you, that is a session.

Think about what that means in practice. One person posting from the app burns a handful of sessions a week. A tool that re-authenticates before every action burns them by the hundred. If you run a dozen accounts through something that logs in fresh each cycle, the wall you hit is not "too many posts" — it is too many logins, and the error message will not say so in those words.

Two more ceilings from the same page are worth knowing before you scale:

• Handle updates: 10 per 5 minutes, 50 per day, per account. Renaming accounts in bulk is metered.
• Account creation: 100 per 5 minutes — by IP, not by account. This is the one line in the whole document that is about your network rather than your identity.
• Overall API requests: 3,000 per 5 minutes by IP. Again: your connection, not your account.
• Blob upload: 52,428,800 bytes (50 MB) maximum per file.

Notice the split. Post-shaped limits are per account. Creation and request limits are per IP. That is the same architecture you see on Threads' published rate limits and on TikTok's daily post cap, and it is the single most useful thing to internalize: platforms meter identity and infrastructure on separate meters.

The 300-character limit is a protocol rule, not an app rule

The other Bluesky number people search for is the character limit. It is 300 — and it is defined at the AT Protocol level rather than inside the Bluesky app. That distinction is not pedantry. It means no third-party client, scheduler, or "pro" tier can raise it, because the constraint lives below the app.

Practically, 300 characters is shorter than an X post's current allowance and much shorter than a LinkedIn one. If you repurpose the same copy everywhere, Bluesky is the platform that will silently truncate your thinking. Writing a Bluesky-native version — not a trimmed version — is the difference between a post that lands and one that reads like a fragment. It is the same discipline covered in cross-posting to multiple platforms: same idea, re-shaped per platform, not one file broadcast everywhere.

What to do with these numbers if you run more than one account

Here is the take-away checklist, in the order the limits will actually reach you:

1. Stop worrying about the daily post cap. At 11,666 creates a day it is not your constraint, and treating it as one leads people to under-post out of vague fear.
2. Count your logins, not your posts. If a tool authenticates per action rather than holding a session, 300/day/account is a real ceiling. Ask any tool you use how it handles sessions.
3. Treat the IP as a shared resource. Account creation and request budgets are per IP. Many accounts behind one address share one budget — and share one reputation.
4. Write to 300, don't trim to 300. The protocol will not bend for you.

If you are running a set of accounts across Bluesky and elsewhere, the practical problem is rarely the ceiling — it is that every platform meters a different unit, so a single "post everywhere on a timer" habit trips a different wire on each one. One approach is a tool like NoobClaw, which runs each account in its own local browser profile with its own fingerprint and IP, posts on randomized human-paced intervals rather than fixed clock ticks, and generates different content per account instead of broadcasting one file. That does not raise any published limit — nothing does — but it keeps you far from the meters that are actually watching, which on Bluesky are sessions and IP, not posts.

Why the points system exists at all (and why that is good news)

Most platforms meter you with a hidden counter and an error message that says nothing. Bluesky meters you with an arithmetic model it publishes. That difference is worth dwelling on, because it changes what you can plan.

A points budget lets one number cover every kind of write. Posting, liking, following and reposting all cost the same 3 points to create, so the platform does not need a separate cap per action type — and you do not need to memorise five different numbers. Deleting costs 1 rather than 3, which quietly tells you something: Bluesky treats cleanup as cheaper than creation. If you are mass-deleting old posts, you have roughly three times the headroom you would have creating them.

It also means the budget is genuinely shared. An account running an aggressive follow strategy is spending the same pool as one posting heavily. If you have ever wondered why a bot that follows thousands of accounts a day suddenly goes quiet, this is the mechanism: the follows ate the posting budget. Bluesky's engineering notes are explicit that the point limits were introduced to constrain prolific bots rather than ordinary users, and the arithmetic bears that out — no human behaviour comes close.

For anyone building a routine, the useful consequence is that you can budget in advance. Decide how many follows, likes and posts a day an account should do, multiply the creates by 3, and check it against 35,000. If you are under a few hundred points, you are operating at roughly one percent of the ceiling and the limit is simply not part of your planning.

FAQ

How many posts can I make per day on Bluesky?

Roughly 11,666 create-type actions per day under the published 35,000 points/day budget, since each create costs 3 points. Posts, likes, follows and reposts all draw from the same pool, so heavy engagement activity spends the same budget as posting does.

Does Bluesky rate limit by IP or by account?

Both, on separate meters. Write points, session creation and handle updates are metered per account. Overall API requests (3,000 per 5 minutes) and account creation (100 per 5 minutes) are metered per IP. If several accounts share one connection, they share the IP-side budget.

Why do I get rate limited on Bluesky when I have barely posted?

Almost always sessions or requests rather than posts. Session creation is capped at 30 per 5 minutes and 300 per day per account, and API requests at 3,000 per 5 minutes per IP. A tool that logs in repeatedly, or several accounts on one connection polling at once, will hit those long before the write budget.

Sources: Bluesky Protocol Services rate limits documentation (bsky.network/docs/rate-limits/), retrieved 2026-09-07; AT Protocol 300-grapheme post limit. Verify current figures against the docs before building against them — published limits change.