How the Instagram API 100 Posts per 24 Hours Limit Works

What is the Instagram API 100 posts per 24 hours limit?

Meta enforces the Instagram API 100 posts per 24 hours limit as a moving window, which means an account can publish 100 posts through the API in any rolling 24-hour period. The exact sentence in Meta's content publishing guide, under the Limitations block in Requirements, reads: "Instagram accounts are limited to 100 API-published posts within a 24-hour moving period."

Two words in that sentence carry most of the weight. "API-published" scopes the count to posts pushed through the Instagram Content Publishing API, which is a different thing from posts made by a human in the Instagram app. "Moving" rules out a midnight reset. Anyone building a queue against this cap needs to read both words before they size the queue.

Does a carousel count as one post or as ten?

A carousel counts as one post against the cap, regardless of how many images or videos it contains. Meta's carousel section states it plainly: "Publishing a carousel counts as a single post." The same section caps a carousel at 10 items, so an account publishing nothing but full carousels moves 1,000 individual images through 100 publishes.

That ratio is the single biggest lever anyone has on this limit. A brand posting 10 separate images burns 10 of its 100 slots. The same 10 images shipped as one carousel burns one. If you are anywhere near the ceiling, the fix is almost always to group images rather than to ask for more headroom.

Same 10 images, different cost

10 single-image posts

• 10 of the 100 daily API slots used

1 carousel post

• 1 of the 100 daily API slots used
• holds all 10 images

Why does the same page also say 50 posts?

The content publishing guide carries a second post-count sentence, in a different section, and it does not say how the two relate. Here is each one, with the section it sits in:

Sentence	Section it appears in	What it says
"Instagram accounts are limited to 100 API-published posts within a 24-hour moving period."	Requirements, under Limitations	100 posts, 24-hour moving period
"Accounts are limited to 50 published posts within a 24-hour period."	Create a carousel container, under Limitations	50 posts, 24-hour period

The 50-post sentence sits between the rule that a carousel holds at most 10 items and the sentence that a carousel counts as a single post. Its neighbors are all carousel rules, which supports reading the 50 as a quota scoped to carousel publishing. It also says "Accounts", not "carousels", and an account-level phrasing left inside a carousel section is what a stale number looks like after a general limit gets raised.

Meta does not say which reading is correct. Nothing elsewhere on the page scopes the 50, retires it, or ties it to the 100. Both sentences are live on the page as of September 10, 2026, and the page leaves the relationship between them open.

The practical answer is to stop quoting either number as the truth for a specific account and go read that account instead. GET /<IG_ID>/content_publishing_limit reports Meta's own count of what an account has used, which is the only figure that reflects whatever the platform is actually enforcing for that account today.

Does Meta still document a 25-post cap?

Meta's content publishing guide does not mention 25 anywhere. The number 25 circulates through scheduler blog posts, Stack Overflow answers, and library READMEs as the Instagram publishing cap, and it has no support in the current documentation. A page checked on September 10, 2026 says 100 in Requirements and 50 in the carousel section, and nothing else.

If you are auditing an integration written a few years ago, the 25 is the thing to look for first. Hardcoded daily caps of 25 are the most common reason an account publishes far below what Meta allows and nobody notices, because the throttle is in your own code and the API never complains.

Is the count applied at container creation or at publish?

Meta's wording counts published posts, not created containers. Publishing through the API takes two calls. POST /<IG_ID>/media creates a container and returns its ID, and POST /<IG_ID>/media_publish with creation_id set to that ID turns the container into a live post. Only the second call produces an "API-published post" in the language the limit uses.

The guide does not spell out the increment point beyond that word, so treat this as a reading of Meta's phrasing rather than an explicit statement. What the page does state explicitly is a second, unrelated 24-hour clock. Query GET /<IG_CONTAINER_ID>?fields=status_code and an unpublished container comes back as EXPIRED, described as "The container was not published within 24 hours and has expired."

Those two 24-hour windows are easy to confuse and behave nothing alike. One is a rolling account budget for publishes. The other is a shelf life on a single container. A queue that builds containers in a nightly batch and publishes them the next evening can hit the second one while nowhere near the first.

What error does Instagram return when an account is over the limit?

Meta's content publishing guide does not document an error for exceeding the publishing limit. Its Troubleshooting section covers container status values (EXPIRED, ERROR, FINISHED, IN_PROGRESS, PUBLISHED) and a short table of partnership ads label errors such as "Creator is not eligible for branded content" and "Maximum number of sponsors exceeded. Limit is 2". No entry names the rate limit.

That gap matters more than it looks. Error handling written against a documented string is stable; error handling written against whatever your integration happened to observe once is a guess that breaks quietly. Until Meta documents the response, the reliable signal is the usage count you read before publishing rather than the failure you catch after.

The guide also advises polling container status "once per minute, for no more than 5 minutes", which is a useful shape for any retry loop you build around the publish step.

What does the cap mean for a scheduling tool?

The 100-post ceiling belongs to Instagram, and every tool that publishes through the official API works inside it. This is a platform quota, not a plan feature, so no scheduler raises it, and any tool claiming to publish past it is either using an unofficial route or counting something other than API publishes.

Where a scheduler earns its keep is in the shape of the queue underneath the cap. Grouping images into carousels stretches 100 slots a long way. Spreading a launch across several days keeps a rolling window from filling. Seeing the whole week at once is what stops a burst from being scheduled in the first place, which is the job of a content calendar. For teams uploading a month of posts in one sitting, bulk scheduling is where the spread gets decided.

AdaptlyPost publishes to Instagram through the official API, so the same 100-post window applies. You can read more about how that connection works on the Instagram posting API page, or see the scheduling side on the Instagram scheduling tool page.

Frequently Asked Questions

Does the Instagram API limit include posts made in the app?

Meta's sentence limits accounts to 100 "API-published posts", which names posts created through the Content Publishing API. The guide does not state whether posts a person makes by hand in the Instagram app count toward the same total. Read the account's own usage through GET /<IG_ID>/content_publishing_limit if manual posting volume is high enough to matter.

Do Stories and Reels count against the 100-post cap?

Meta's content publishing guide does not say. The limit sentence names API-published posts without listing which media types are included or excluded, and the Story posts and Reels posts sections of the page do not carry their own post-count limits. The guide leaves this undefined.

When does the 24-hour window reset?

The window never resets, because Meta describes it as a "24-hour moving period". Each publish ages out of the count 24 hours after it happened, one at a time. An account that publishes 100 posts between 09:00 and 10:00 regains capacity between 09:00 and 10:00 the next day, not at midnight.

How many images can one account publish per day through the API?

An account can publish up to 1,000 images per rolling 24 hours if every publish is a full carousel, because a carousel holds at most 10 items and counts as one post. Publishing single images instead caps the same account at 100 images. The item count and the post count are separate ceilings.

Which number should an integration plan against, 100 or 50?

Neither number should be hardcoded. Meta's page carries both, in different sections, without saying which governs an account, so a fixed constant in your code will be wrong for some accounts. Query GET /<IG_ID>/content_publishing_limit before publishing and let the account's reported usage drive the decision.

Where is the 100-post limit documented?

The limit is documented on Meta's Instagram Platform content publishing guide at developers.facebook.com/docs/instagram-platform/content-publishing, in the Limitations block under Requirements. The 50-post sentence appears further down the same page, in the Limitations block under Create a carousel container.

How long can an unpublished container sit before it expires?

Meta gives an unpublished container its own 24-hour shelf life, separate from the posting quota. Query GET /<IG_CONTAINER_ID>?fields=status_code and a container that missed its window comes back as EXPIRED, described as "The container was not published within 24 hours and has expired." A queue that batches containers overnight and publishes them the next evening can trip this clock while still far from the 100-post budget.

Why shouldn't error handling rely on a specific rate-limit message from Instagram?

Meta's content publishing guide never documents an error string for exceeding the publishing limit. Its Troubleshooting section lists container statuses such as EXPIRED, ERROR, FINISHED, IN_PROGRESS, and PUBLISHED, plus a short table of partnership ads errors, and none of them name the rate limit. Code written against a string nobody documented is a guess, so check the account's usage count before publishing instead of catching a failure after.

How often should a retry loop check a container's status?

Meta advises polling a container's status once per minute, for no more than 5 minutes. That cadence applies to the container-expiry clock, not the 100-post window, so a retry loop built around it should stay short and stop within that five-minute span.

Is the 25-post limit mentioned in some scheduler blog posts still real?

No. Meta's content publishing guide never mentions 25 anywhere on the page, in Requirements or in the carousel section. The number spread through scheduler blog posts, Stack Overflow answers, and library READMEs, and an integration hardcoded against it publishes far below the 100 Meta actually allows without anyone noticing, because the throttle sits in the code and the API never complains.