How-To Guide
What are the Instagram DM limits?
Meta publishes no daily DM cap. The windows decide who you may message, the per-second ceilings how fast, and every daily count elsewhere is an estimate.
By the Superdirector editorial team. Meta's developer documentation and every competitor guide in this article read November 14, 2026; dated figures carry their own date.
At a glance
What are the Instagram DM limits?
No daily DM cap exists anywhere in Meta's documentation, so the honest answer is a split: what you may send is decided by eligibility windows, how fast you may send is decided by per-second and per-hour call ceilings, and the daily numbers you see quoted are estimates or tool conventions. Meta's documented ceilings for Instagram messaging are 100 Send API calls per second for text on the Instagram Platform route (300 per second on the Messenger route), 10 per second for audio or video, and 750 private replies per hour to comments on posts and reels. A private reply to a comment is one message, within seven days. A conversation opens to you for 24 hours after the person's message. Everything else a guide tells you about daily DM counts is a report, not a rule.
- Documented per account: Send API 100 calls per second for text (300 on the Messenger route), 10 for audio or video, private replies 750 per hour for posts and reels and 100 per second for Live comments during the broadcast, Conversations API 2 calls per second. None of these is a daily DM number, and the Instagram Platform call budget that is measured daily, 4,800 calls per 24 hours times impressions, explicitly excludes messaging.
- Reported, not documented: manual daily DM ranges between about 20 for brand-new accounts and about 200 for aged ones (estimates by account age and trust), the 200 automated DMs per hour figure (a tool pacing convention), and a first block that lasts roughly 24 to 48 hours (creator reports).
The same text DM counts against a different per-second ceiling depending on which Meta route a tool sends on, and neither route publishes a daily cap. Limits are counted per Instagram professional account (Original diagram; Meta rate-limit documentation read November 14, 2026).
Make it work for your brand
Find it. Remake it. Post it. Superdirector turns the viral formats in your niche into your brand's carousels, X posts and video scripts, and keeps the calendar full.
The limits that actually exist
Ask what the Instagram DM limits are and the direct answer is uncomfortable but short: Meta publishes no daily DM cap, in its developer documentation for automation or anywhere else, and Blotato's limits guide opens with exactly that finding as well. What does exist is three separate limit systems, and the mistakes people make almost always come from applying a number from one system to another.
- Manual messages you type in the app: judged by behavior, not by a published count.
- Automated sends through the official API: judged by per-second and per-hour call ceilings Meta documents in full, plus the messaging windows that decide who can receive a message at all.
- Tool-side pacing and allowances: numbers a tool chose for itself, such as 200 DMs an hour, which sound official until you trace them.
Keep the three apart and the whole question becomes manageable: the windows decide who you may message, the call ceilings decide how fast, and the daily counts you read elsewhere are estimates by account age or pacing conventions. The rest of this article walks each layer in that order, because the binding constraint on automation is usually the window, not the volume.
What Meta actually documents
Meta's rate-limit documentation counts every Instagram messaging endpoint per Instagram professional account. Two Send API readings exist because the two Meta routes quote different rates, so the first thing to learn about your tool is which route it sends on.
| Limit | Meta's documented value | Counted per | What it decides |
|---|---|---|---|
| Send API, Instagram Platform route | 100 calls per second for text, links, reactions and stickers | Instagram professional account | How fast text sends can go out on the Instagram Login route |
| Send API, Messenger route | 300 calls per second for text, links, reactions and stickers | Instagram professional account | The same send on the Facebook Login route |
| Send API, audio or video | 10 calls per second on either route | Instagram professional account | Media-heavy sends, far slower than text |
| Private replies to post and reel comments | 750 calls per hour | Instagram professional account | The keyword-comment automations a viral post can carry |
| Private replies to Live comments | 100 calls per second, only while the broadcast runs | Instagram professional account | Answers to live commenters, which stop when the Live ends |
| Conversations API | 2 calls per second | Instagram professional account | How fast an agent can read threads source |
| Message text | Under 1,000 characters; UTF-8, 1,000 bytes or less | One message | Emoji count in bytes, so decorated messages hit it sooner source |
| High-volume inbox | More than 72,000 messages sent and received, with no time period stated | Instagram professional account | The inbox stops showing new messages and cannot send until volume drops source |
| Single thread | No number; Meta warns an app may be rate limited if too many messages are sent to one thread | One conversation | The rule a looping automation trips source |
Notice the row that is missing: there is no DMs-per-day line, because Meta does not define one. The only daily formula on the page, 4,800 calls per 24 hours times the account's impressions, applies to Instagram Platform calls excluding messaging. When a Business Use Case throttle does hit, the response header carries an estimated_time_to_regain_access figure in minutes, and the error code tells you which budget was hit: 80002 for Instagram, 80006 for Messenger.
The numbers are generous for replies. At 100 calls per second, sending 2,000 replies to a viral post takes 20 seconds of budget; at the 750-per-hour private-reply ceiling, the same 2,000 keyword comments need just under three hours to receive their one reply each. The ceilings almost never bind what a person actually wants to do. What binds is the next section.
The windows that bind before any number does
Meta's send-message documentation opens with the rule that decides everything else: to send messages to a person on Messenger or Instagram, the conversation must be initiated by that person. The API has no cold-outreach path. Every automated message answers someone who acted first, and each action opens its own clock.
- A person sends a message: the standard 24-hour window opens, and messages inside it may contain promotional content.
- A person comments on your post or reel: the private-reply rule earns exactly one automated DM, and it must go out within seven days of the comment.
- After that one private reply, follow-up messages need the person to respond, which re-opens their own 24-hour window.
- A conversation that starts from a Click-to-Messenger or Click-to-Direct ad: the window may last up to 7 days from the person's first message, a change Meta documented on September 28, 2026. Conversations that start by other entry points keep the 24-hour clock.
- Outside every window, Meta permits only non-promotional tagged messages, and from April 27, 2026 several common tags return error code 100. The Human Agent tag extends a support conversation to 7 days and requires app review approval.
Two practitioner readings complete the picture. Reachlee's sourced guide treats the comment-to-DM flow as one-shot by design and reports that its own tool refuses to DM the same comment twice, recording every replied comment durably. DMGO's limits post reports that the windows cause more support tickets than the rate limits do, because a comment from a month ago can no longer be answered by automation at all. Meta's own send-page lists a comment among the actions that open the standard window; the practitioners read the Instagram flow more narrowly, one reply per comment and nothing more until the person replies. This article keeps both readings side by side rather than adjudicating beyond the sources.
A comment earns exactly one private reply within seven days, and the next message waits for the person to reply. Meta lists a comment as a window opener while practitioners read the flow as one reply per comment (Original diagram; Meta send-message documentation and competitor guides read November 14, 2026).
Why there is no official daily DM number
For messages you type yourself, no published count exists at any tier. Instagram's help center says only that a sender who keeps going after a warning "may not be able to send more direct messages for a period of time," which Blotato quotes as the closest thing Instagram offers to a number. Novalya argues the silence is deliberate: a published threshold becomes a target every spam operation would park itself one message under, so enforcement stays a per-account model of normal use. That reading matches the help page's own wording.
What circulates instead is a stack of estimates that disagree with each other more than their authors admit. CreatorFlow reports 20 to 50 manual DMs a day for accounts under 30 days old and 150 to 200 for accounts older than 180 days. Reflys reports 20 to 50 for fresh accounts and 100 to 150 for older business profiles. Inro reports 50 to 100 for established accounts with a clean history, and Wave treats 50 as the ceiling worth planning around. The ranges overlap; the honest summary is that new accounts taper on far less than aged ones and nobody has an official number.
The pattern sends are judged by matters more than the count, and the sources agree on its order. Inro's compliance guide puts near-identical messages to many people first, ahead of speed, cold recipients and recipient reactions. Reflys adds the velocity flag: dozens of messages inside a few minutes reads like a bot attack even at a modest daily total. Cold messages to people who never interacted with you are the high-risk case by default, which is why Wave holds links back entirely until a person replies and why Sumora ramps cold volume at 5 a day for a brand-new account against 10, 15 or more after weeks of clean history. Dealism adds the consent layer from Meta's community guidelines: repeatedly contacting people for commercial purposes without their consent is discouraged even when the send technically goes through.
What a block looks like and what to do
The restriction ladder is creator-reported, not published, and every duration below carries that label. The reports agree on the shape even where they disagree on the numbers.
- A first action block: a temporary restriction on a feature, reported as a few hours to a couple of days (CreatorFlow's reports put most first offenses at 24 to 48 hours). The notice reads "try again later" or "we restrict certain activity to protect our community," and you can still receive messages.
- A longer restriction on a repeat: reported at several days, more when the same behavior resumed the moment the first block lifted. After a multi-day block, guides report accounts running under quietly reduced limits for a while, which is how people get blocked again at a volume that was previously fine.
- A feature-specific loss: the ability to write to non-followers goes first in Novalya's ladder, while the rest of the account carries on.
- The account disabled: rare, and reported only at the far end of repeated violations and circumvention, not from one bad day.
The recovery steps read the same across every guide, including the ones built on the official API. Stop the sending entirely rather than at reduced volume. Read the notice your account shows, and use the Account Status hub to see whether Instagram names a removed item or an ongoing review to fix. Do not move the same behavior to another account, device or network: Novalya's reading of the Instagram Terms of Use is that defeating an action block is the real breach, not the volume that earned it. When the block lifts, return below the volume that triggered it, to warm contacts first, and let replies rebuild the pattern the model reads as normal.
The same daily total reads differently when it arrives as a burst inside minutes versus paced across the day, and velocity is the flag that separates them. Tool delays exist to keep sends out of the burst shape (Original diagram; creator reports and tool guides read November 14, 2026).
What tools add on top
Every official-API tool lives inside Meta's ceilings and adds its own pacing on top, because the documented numbers do not include the behavior model that actually gets accounts restricted. The honest guides name their own numbers, and those numbers are tool conventions by definition.
| Tool | Its own addition | How its page labels it |
|---|---|---|
| CreatorFlow | About 200 DMs paced per hour | A tool-side convention, not Meta's limit source |
| Reflys | The same 200-per-hour conservative buffer | Stated as a safety buffer, with the reminder that Meta publishes no DMs-per-hour number source |
| Reachlee | 600 private replies per hour kept under Meta's 750; retrigger capped at 200 new people per account per day for the last 7 days of comments | An internal headroom reserve for bursts source |
| DMGO | A 30-second minimum delay plus a random gap before every DM, an hourly cap under 750, and a monthly quota on the free plan | Pacing that keeps no two DMs in the same second source |
| Blotato | A monthly active-contact ceiling of its own: 1,000 to 15,000 by plan, one contact per person per connected account | Named as a limit Blotato adds, separate from Meta's source |
| Novalya | A monthly send cap you choose, with spacing and message variants applied for you | The range the tool is willing to stand behind, not an Instagram figure source |
Read the table with the right question in mind: a tool cap is what the vendor can promise, and it tells you their throttle. Meta's ceilings tell you the technical maximum. The account-level reality, eligibility to send at all, sits above both, and no tool page changes it. Inro's summary is the strongest version: the official API is a different rulebook, stricter about who you can message and more permissive about doing it reliably at volume, not a bigger bucket. Two operational notes round it out: DMGO advises one automation tool per Instagram account because two tools double the pace Instagram sees, and Meta's own docs warn against looping sends to a single thread, which is the exact pattern a misconfigured automation produces.
Where Superdirector fits
This article is deliberately narrow about DM automation, and so is Superdirector (ours). Superdirector is not a DM tool, and nothing here describes messaging limits to promise on its behalf. What it does is the publishing side: Superdirector watches competitors and keywords on Instagram, TikTok, YouTube and X, and turns the formats that are working into new carousels and X posts in your brand.
Growth, at $199 a month, is the plan for one AI-run account: eligible Instagram carousels and single link-free X text posts can be published to a connected account under its standing posting permission. Starter, at $29 a month, is the hands-on entry you use from Claude or ChatGPT through MCP, with no sending of its own. If your queue is empty, that operated-account model addresses the posting half of being visible on Instagram; the DM windows and ceilings above belong to whichever reply tool you pair it with, and this page is where those numbers stay honest.