Search for Instagram DM automation limits and nearly every result repeats the same number: 200 DMs per hour. It shows up in comparison posts, compliance guides, and tool marketing pages as though Meta published it somewhere specific.
Meta didn't. Here's what its actual Graph API documentation says, where the 200 figure likely came from, and why the distinction matters if you're running comment-to-DM automation at any real volume.
What Meta's Documentation Actually Specifies
Meta's Graph API rate-limiting docs don't list a single messaging cap. They break it down by endpoint, and the numbers are more specific than the rounded figure everyone quotes.
The Send API (the endpoint used to send a DM directly) has separate per-second limits depending on message type: a higher ceiling for text, links, reactions, and stickers, and a noticeably lower one for audio and video. Different sources report the text figure differently (some cite 100 calls per second per account, others cite 300), which suggests either the number has changed over time or is measured slightly differently depending on context. Either way, it's a per-second ceiling, not a per-hour one, and it's well above what any real comment-to-DM campaign would hit.
The number that matters more for this category is the Private Replies API, specifically for replies to comments on posts and Reels, which most comment-to-DM automation actually uses. Meta's documentation puts that limit at 750 calls per hour per Instagram professional account. That's the closest thing to an official hourly ceiling that exists in Meta's own docs, and it's nearly four times the 200 figure everyone repeats.
So Where Did 200 Come From
Nowhere official. It reads like a convention that spread because it's a safe, round, conservative number that comfortably sits under the documented 750-per-hour private-reply ceiling.
That gap matters. Pacing to 200 an hour instead of the documented 750 leaves headroom for retries, failed sends, and Meta's separate anti-spam behavior monitoring, which isn't rate-limit enforcement at all. It's a pattern-detection system that can flag or restrict an account for looking automated regardless of raw volume. A tool quoting "200/hour" is describing an operating margin it chose, not a rule Meta wrote down.
The risk with treating 200 as gospel isn't that it's wrong to pace conservatively. It's that creators reading it as an official Meta rule might assume staying under it is a compliance guarantee, when the actual enforcement mechanism is behavioral, not purely numeric.
Rate Limits and Spam Detection Are Different Systems
This is the distinction most "here's the limit" posts skip. Rate limiting is Meta's API infrastructure protecting itself from being overwhelmed by call volume. It's mechanical: hit the ceiling, get throttled, back off, try again.
Anti-spam and account-restriction systems are separate. They look at behavior patterns: sending speed relative to account age and trust level, whether messages go to people who never engaged, whether a burst of sends follows a single viral post. Instagram's account-ban patterns in 2026 are driven far more by these behavioral signals than by which side of any specific number an account lands on.
That's why two accounts sending the identical hourly volume can have completely different outcomes. One paces smoothly across the day with a healthy ratio of genuine replies. The other blasts everything in the ten minutes after a Reel goes viral. Both might stay under 200 an hour on average. Only one looks suspicious to Meta's systems.
What This Means for Choosing a DM Automation Tool
The practical takeaway isn't "ignore the 200 number," it's "understand what it actually protects you from." A tool that paces sends conservatively is managing behavioral risk, not just avoiding a hard rate-limit wall that's actually closer to 750 an hour for the private-reply pathway most comment-to-DM tools use.
That's also the argument for an outbox that queues and paces delivery instead of firing everything the moment a keyword comment lands. A Reel that suddenly gets 2,000 comments shouldn't turn into 2,000 DMs sent in the same five minutes just because the technical rate limit would theoretically allow it. Spreading that volume out over hours looks like normal account behavior to Meta's systems. Firing it all at once looks like exactly the pattern anti-spam detection is built to catch, regardless of which specific number you're pacing against.
If you're evaluating tools, ask less about their stated hourly cap and more about how they actually pace delivery after a spike. A tool that quotes 200/hour but sends everything the second it's queued isn't meaningfully safer than one with no stated number at all.
The Compliance Baseline Underneath All of This
None of the rate-limit numbers matter if the underlying mechanic isn't compliant to begin with. Automated DMs need to go through Meta's official Instagram API, replying to people who engaged first (a comment, a Story reply, a DM), inside the 24-hour messaging window that resets each time the recipient responds. Meta's DM compliance rules cover that baseline in full, and it matters more for account safety than any specific hourly figure.
Pacing is a risk-reduction layer on top of that baseline, not a replacement for it. A tool that respects the messaging window and only contacts people who engaged first, then paces sends sensibly after a spike, is doing the two things that actually matter. The exact number it paces to is a secondary detail.
This kind of gap between a widely repeated number and what Meta's documentation actually says isn't unique to DM pacing either. The Messenger message-tag deprecation earlier this year is another case where the practical effect on tools spread faster than accurate detail about what actually changed and when.
FAQ
Is 200 DMs per hour a real Instagram rate limit?
It is not a number that appears in Meta's own Graph API rate-limit documentation. It is a pacing convention that automation tools converged on as a safe operating ceiling. Meta's actual documented messaging limits are structured differently, as per-second Send API caps and a specific 750 calls per hour limit for private replies to comments on posts and Reels.
What does Meta's Graph API documentation actually say about DM rate limits?
Meta's rate-limit docs specify Send API limits per second per Instagram professional account (higher for text and stickers, lower for audio and video), plus a distinct limit of 750 calls per hour specifically for private replies to comments on posts and Reels. There is no single published 200-per-hour figure covering all messaging.
Why do so many tools quote the same 200 DMs per hour number?
Because it became an informal industry safe zone. Comment-to-DM tools mostly send through the private-reply-to-comment pathway, and pacing to roughly 200 an hour keeps well under the documented 750-per-hour ceiling with margin for retries, errors, and Meta's separate anti-spam behavior detection, which isn't a fixed number at all.
Does staying under 200 DMs per hour guarantee my account won't get restricted?
No. Rate limits and anti-spam enforcement are two different systems. Meta can restrict an account for sending patterns that look automated or unsolicited even while staying under any hourly cap, since spam detection weighs behavior signals, not just volume. Pacing under a safe ceiling reduces risk, it doesn't eliminate it.
UnlockDM's DM outbox paces delivery after a spike instead of firing every reward the second a comment lands, because the actual protection against restriction is smooth, believable sending behavior, not just staying under whichever hourly number a tool happens to quote.
