As of November 2026, the hard API posting caps are: Instagram 100 posts per rolling 24 hours, Facebook Page Reels 30, Threads 250 posts plus 1,000 replies, YouTube 100 uploads per day from a separate quota bucket, X 100 posts per 15 minutes per user, and Bluesky about 1,666 record writes per hour. Mastodon's default server code allows 300 statuses per 3 hours. TikTok gives a creator roughly 15 Direct Post uploads a day. LinkedIn, Facebook Page feed posts and Pinterest publish no fixed number at all. The full table is below, with text and media limits, followed by the places where our production code disagrees with the docs.
What are the posting limits for each social media API?
The table below has the documented number for each platform, as of November 2026. I read every cell off the platform's own docs in the last week of October 2026. Where a platform publishes no number, the cell says "not published".
| Platform | Posting cap | Text limit | Media and carousel limits |
|---|---|---|---|
| Instagram (Graph API) | 100 API-published posts per 24 h moving window; carousel counts as 1 | 2,200 characters, 30 hashtags, 20 @ tags | Carousel up to 20 items; Reels 3 s to 15 min, 300 MB; feed images JPEG only, 8 MB; Stories video up to 60 s, 100 MB |
| Facebook Pages | Reels: 30 per 24 h. Feed and photo posts: not published | Not published | Reels 3 to 90 s, 9:16; photos 4 MB, JPEG, PNG, GIF, BMP or TIFF |
| Threads | 250 posts and 1,000 replies per 24 h | 500 characters, at most 5 links | Carousel 2 to 20 items; video up to 5 min, 1 GB |
| Not published; per-app and per-member daily limits shown in the Developer Portal | 3,000 characters (Help Center) | MultiImage 2 to 20 images; video 3 s to 30 min, MP4, 75 KB to 500 MB | |
| YouTube (Data API v3) | Uploads: 100 per day at 1 unit each, own bucket; all other calls: 10,000 units per day | Title 100 characters, description 5,000 bytes, tags 500 characters | File up to 256 GB |
| X (API v2) | 100 posts per 15 min per user, 10,000 per 24 h per app; billed per post | 280 weighted characters; 25,000 with Premium | 4 photos, or 1 GIF, or 1 video; image 5 MB, GIF 15 MB; video 20 min and 8 GB (Premium: 125 min, 16 GB) |
| Mastodon (default server) | 300 statuses per 3 h per account; 300 API calls per 5 min; 30 media uploads per 30 min | 500 characters, each URL counts as 23 | 4 attachments, at most 1 video; 16 MB image, 99 MB video in the current source |
| Bluesky | 5,000 points per hour and 35,000 per day; a create costs 3 points | 300 graphemes (3,000 bytes) | 4 images at 2 MB each; video 300 MB |
| Telegram (Bot API) | About 30 messages per second overall, 1 per second per chat, 20 per minute per group | 4,096 characters per message, 1,024 per media caption | Album of 2 to 10 items; uploads 10 MB for photos, 50 MB for other files |
| Discord (webhooks) | Not published per route; read the rate limit headers. 50 requests per second per bot globally | 2,000 characters | Up to 10 embeds; files up to 20 MiB by default |
| Pinterest (API v5) | Not published in the API description | Title 100, description 800, alt text 500 characters | Multi-image pin 2 to 5 images |
| TikTok (Content Posting API) | About 15 posts per day per creator; 6 init requests per minute per token | 2,200 UTF-16 runes | Video up to 10 min and 4 GB via upload; photos 20 MB, JPEG or WebP |
Two cells need a footnote. Meta's content publishing guide says 100 posts in its rate limit section and 50 in its carousel section. And the YouTube upload number changed twice in a year: the revision history records an upload dropping from about 1,600 units to about 100 in December 2025, then a move to its own bucket on June 1, 2026. If your quota math is from 2024, redo it.
Which limits will you hit first?
The first limit most people hit is not a daily cap. It is a format rule: a 281-character post on X, a 4.5 MB photo on a Facebook Page, an eleventh carousel slide. Daily caps only bite when you automate at volume, and at that point quiet failures cost more than the cap does.
A few rules sit outside the table and catch people anyway.
- X does not count the way
string.lengthdoes. Per the counting characters guide, every URL counts as 23 characters and every emoji as 2. A tweet with a long tracking link can be shorter than it looks, and one full of emoji can be longer. - X bills per call. On pay-per-use pricing, a post costs $0.015 and a post containing a URL costs $0.20. When the credits run out, every request fails until you top up (in our logs, as HTTP 402).
- TikTok hides posts from unaudited apps. The content sharing guidelines restrict an unaudited app to private (
SELF_ONLY) posts and to 5 posting users per 24 hours. - Mastodon limits belong to each server. 500 characters and 4 attachments are the defaults in Mastodon's source, but an admin can change them. Read
configuration.statusesfrom the instance entity before you trust a number.
What do the docs get wrong in practice?
Some limits only show up when you publish for real. These come from running pendpost's own lanes every day.
Instagram's resumable upload gives up at about 35 seconds. The docs allow Reels up to 15 minutes, and that is true, just not for every upload path. In October 2026 we timed the resumable upload (rupload) on a live account, with containers we never published. Uploads that passed returned within 26 seconds. Longer reels failed at 35 to 37 seconds with HTTP 400 ProcessingFailedError, whatever the file size or encoding, and the container then stayed IN_PROGRESS for good. The same 102 MB, 70-second file sent through video_url (a public HTTPS link Meta fetches itself) finished in 64 seconds. My reading: the resumable path processes the video inside the request and Meta cuts the request off. A long reel needs video_url. For weeks it looked like random Meta flakiness.
The "25 posts per day" Instagram figure is out of date. It still circulates, but the current guide says 100. We dropped our own conservative default (2 posts, 6 hours apart) for that reason.
X refuses over-length posts from the API too. The long posts you see on x.com are a Premium feature, and the API gives a non-Premium account no way around 280. A scheduler that skips an over-length post without recording a failure leaves it overdue forever with no error anywhere. We shipped exactly that bug once.
YouTube quota errors look like permission errors. A quota 403 (quotaExceeded, rateLimitExceeded) has the same status code as a missing OAuth scope. Telling the user to reconnect fixes nothing; waiting for the midnight Pacific reset does.
How does pendpost encode these limits?
pendpost keeps each limit in one place that the pre-approval check and the publish engine both read, so a post that fails the limit is flagged before you approve it, not after it is due. The numbers live in lib/caption.mjs, lib/carousel.mjs and the scheduler in the open-source repo.
| Lane | What pendpost enforces | Where it differs from the docs |
|---|---|---|
| Instagram and Facebook | One shared cap of 100 posts per rolling 24 h, with a warning at 80 percent; a capped post waits, it is never dropped | The cap is shared across both, and Facebook Reels have their own lower cap of 30 |
| Instagram carousel | 10 items in pendpost 2.8.0; 20 from the next release | Meta documents 20; the fix is on the main branch and ships in the next release |
| Facebook photos | 4 MB and JPEG, PNG, GIF, BMP or TIFF, checked before any upload; 10 photos per album | Meta documents no album count, so 10 is our own cautious cap |
| X | 280 is a hard error at approval time; over-length text can be split into a thread | Matches X for non-Premium accounts; Premium long posts are not supported. In 2.8.0 approval counts URLs as 23 but publish counts raw length; the next release uses X's own count (URLs 23, emoji 2) in both places |
| YouTube | Description capped at 5,000 characters in 2.8.0 | YouTube counts 5,000 bytes, so accented text can pass our check and be refused. The next release counts bytes, checks the 100-character title, < and >, and tags the way YouTube does |
| Mastodon | 500 characters including the content warning; 4 attachments, one video | Matches the default server; a custom instance limit is not read |
| Telegram, Discord, Pinterest, TikTok | 1,024 caption or 4,096 text; 2,000; title 100 and description 800; 2,200 | Match the docs |
Writing this table turned up three gaps in pendpost 2.8.0: the carousel cap, the YouTube byte count, and X text counted two different ways. All three are fixed on the main branch and ship in the next release; the shared Meta cap is still open. I would rather list them here than have you find them in production. Beyond the limits, a Meta action block (error 368) or an X credits error halts that lane until you clear it, instead of retrying into a suspension. The approval and circuit breaker docs cover how that works, and the Meta credentials page covers the Instagram and Facebook setup.
How should you plan around platform limits?
Check limits when a post is created, not when it is due, and read live quotas where the platform offers them. In practice that comes down to this:
- Validate at draft time. Count characters the way each platform counts them, and check media size, format and carousel length before anyone approves the post.
- Read live quotas. Instagram exposes
content_publishing_limitand Threads exposesthreads_publishing_limit; LinkedIn shows usage in the Developer Portal. Trust those over any table, this one included. - When a cap is reached, keep the post due and try again later, and log one row for it instead of one per retry.
All of this matters more once an agent does the scheduling. An agent will happily queue 40 posts in a minute and never wonder about Meta's carousel section. The guide on letting an AI agent post safely covers the approval side. pendpost runs these checks on every lane it supports; the capabilities page lists which lanes publish from the cloud and which stay local, and you can try the whole flow without real accounts in mock mode.
Originally published on pendpost.com. pendpost is a free, open-source (MIT), local-first social media planner where an AI agent drafts posts behind a human approval gate.
