Publish & grow
Understand posting limits and fair use
How many posts each connected account can send in any 24 hours, why each platform's number is what it is, and where to change your own cap.
Updated
Three limits, and the smallest one applies
Every connected account has a posting limit: the most posts it sends in any 24 hours, counted on a rolling window rather than a calendar day. Three numbers decide it, and the smallest one wins.
| Limit | What it is |
|---|---|
| The platform's own limit | What the network documents for one account, such as Instagram's 100 API posts in 24 hours. Going past it can get the account throttled or blocked, so Krevaya keeps its own posts under it. |
| Your plan's fair-use cap | How many posts a plan includes per account and platform. Higher plans allow more, up to the platform's own limit. |
| Your cap | A number you choose, up to your plan's cap. Until you choose one, your cap follows your plan, so an upgrade raises it on its own. |
A brand's scheduled, sending, and published posts on a platform count toward its limit there. Drafts do not count, and neither does history you imported from the platform.
See and change your limits
- Open Settings → Publishing → Posting limits for the active brand, or a brand's Publishing section on the Brands page.
- Each connected platform shows what the platform allows (with why and a source), your plan's cap, your cap, and how many posts are in the current 24 hours.
- Type a new cap and choose Save, or choose Use plan default to follow your plan again. A number above your plan's cap is refused with the plan that allows it.
- For Threads, LinkedIn, and Bluesky, the Draft for switch decides whether new draft runs write that platform. Connecting the channel turns it on the first time; switching it off stops those drafts without changing the cap.
What happens when a limit is reached
Next free slot skips any time that would go over a limit and finds the next one that fits. Picking a specific time that would go over it is refused, and the message names each limit, how many posts are already in that 24 hours, and the next free time. The composer shows how many posts each channel already has under its pill.
When a post is due, Krevaya checks your plan's cap and the platform's own limit again against what actually went out in the last 24 hours. A post over either one is held, never failed: it stays queued with the reason and goes out on a later pass once the window has room. Your own cap is checked when a post is scheduled, so a post scheduled before you lowered it still goes out.
The numbers by platform and plan
Posts per connected account in any 24 hours. "No set number" means the platform publishes no daily limit for one account, so only the fair-use cap applies. Platform figures were checked on 2026-10-16.
| Platform | Platform allows (per 24 h) | Free | Plus | Pro | Ultra | Max | Agency |
|---|---|---|---|---|---|---|---|
| Beehiiv | No set number | 1 | 3 | 5 | 10 | 15 | 20 |
| Bluesky | 11,666 | 5 | 25 | 50 | 100 | 200 | 300 |
| Buttondown | No set number | 1 | 3 | 5 | 10 | 15 | 20 |
| Circle | No set number | 1 | 3 | 5 | 10 | 15 | 20 |
| Dev.to | No set number | 1 | 3 | 5 | 10 | 15 | 20 |
| Discord | No set number | 20 | 50 | 100 | 200 | 300 | 500 |
| Discourse | No set number | 1 | 3 | 5 | 10 | 15 | 20 |
| Dribbble | No set number | 1 | 3 | 5 | 10 | 15 | 20 |
| No set number | 3 | 10 | 25 | 50 | 75 | 100 | |
| Ghost | No set number | 1 | 3 | 5 | 10 | 15 | 20 |
| Google Chat | No set number | 20 | 50 | 100 | 200 | 300 | 500 |
| Hashnode | No set number | 1 | 3 | 5 | 10 | 15 | 20 |
| 100 | 3 | 10 | 25 | 50 | 75 | 100 | |
| Kit | No set number | 1 | 3 | 5 | 10 | 15 | 20 |
| Lemmy | No set number | 5 | 15 | 30 | 50 | 75 | 100 |
| LINE | No set number | 20 | 50 | 100 | 200 | 300 | 500 |
| 50 | 2 | 5 | 10 | 15 | 25 | 50 | |
| Listmonk | No set number | 1 | 3 | 5 | 10 | 15 | 20 |
| Mastodon | No set number | 5 | 15 | 30 | 50 | 75 | 100 |
| Mattermost | No set number | 20 | 50 | 100 | 200 | 300 | 500 |
| Microsoft Teams | 1,800 | 20 | 50 | 100 | 200 | 300 | 500 |
| No set number | 5 | 15 | 30 | 50 | 75 | 100 | |
| Pixelfed | No set number | 5 | 15 | 30 | 50 | 75 | 100 |
| No set number | 5 | 15 | 30 | 50 | 75 | 100 | |
| Slack | No set number | 20 | 50 | 100 | 200 | 300 | 500 |
| Telegram | No set number | 20 | 50 | 100 | 200 | 300 | 500 |
| Threads | 250 | 5 | 25 | 50 | 100 | 150 | 250 |
| TikTok | 15 | 1 | 3 | 5 | 10 | 15 | 15 |
| Tumblr | 250 | 5 | 15 | 30 | 50 | 75 | 100 |
| Vimeo | No set number | 1 | 3 | 5 | 10 | 15 | 20 |
| Whop | No set number | 1 | 3 | 5 | 10 | 15 | 20 |
| WordPress | No set number | 1 | 3 | 5 | 10 | 15 | 20 |
| YouTube | No set number | 1 | 2 | 3 | 5 | 8 | 10 |
Frequently asked questions
Why is my cap lower than the platform's limit?
Your plan's fair-use cap is often lower than what the platform allows. It keeps accounts at a pace that does not read as spam and leaves room in the quotas every Krevaya customer shares. Higher plans allow more, up to the platform's own limit.
Does a held post need anything from me?
No. A post held for a posting limit stays queued and goes out on a later pass once the 24-hour window or the platform's day has room. Give it a later time if you want it at a specific moment.