Instagram DM Limits in 2026: What Meta's Docs Actually Say
Meta's documented limit for comment-to-DM is 750 private replies per hour per Instagram professional account, and each comment can get one private reply within 7 days. Many numbers floating around online, like "200 DMs per hour", aren't in Meta's documentation. This page quotes the official limits, explains what they mean for automation, and links to the source for each one.
Checked against Meta's developer documentation on October 16, 2026. Meta can change these, so check the linked pages for the latest.
The official limits, in one table
| What | Limit | Source |
|---|---|---|
| Private replies to comments on posts and reels | 750 calls per hour per Instagram professional account | Meta rate limiting |
| Private replies to Instagram Live comments | 100 calls per second, only during the broadcast | Same page; Private replies |
| Send API: text, links, reactions, stickers | 100 calls per second per account | Meta rate limiting |
| Send API: audio or video | 10 calls per second per account | Same page |
| Conversations API | 2 calls per second per account | Same page |
The rules that matter more than speed
Speed limits are rarely the problem. These rules decide whether a DM can be sent at all:
- One private reply per comment. Meta's docs: "Only one message can be sent to the Instagram user who commented."
- Within 7 days. "Private replies can be sent within 7 days of when the comment was created." Older comments can't get a private reply.
- The person has to answer before you continue. "Only when the Instagram user responds to the private message can you continue the conversation." A button tap counts as a response.
- Live comments only during the live. "As soon as the live broadcast has ended, private replies can no longer be sent."
What about "200 DMs per hour"?
You'll see "200 per hour" in many guides. It isn't a limit in Meta's rate-limiting documentation for private replies, which states 750 per hour. It's a cautious pacing number some tools picked. Pacing below the official limit is sensible. Treating 200 as Meta's rule is a misunderstanding.
So is DM automation safe?
Hitting the hourly cap isn't what usually gets accounts in trouble. Behavior is. Accounts get flagged when they:
- message people first (cold DMs), which the API doesn't allow for private replies anyway
- send the same text over and over, especially public replies under comments
- send to the same person again and again
Safe automation looks like this:
- Reply-only: every DM answers a comment, a reply or a button tap
- Paced below the official limit, with the overflow queued in order rather than dropped, since every comment has a full 7 days to be answered
- One DM per person per post per day
- Varied public replies instead of one repeated line
DMisland enforces all of these on every plan, and they can't be turned off.
FAQ
Is there a daily DM limit?
Meta's docs list per-hour and per-second limits for the API, not a daily cap. The practical daily ceiling for comment replies follows from the hourly limit and the one-reply-per-comment rule.
Do public replies count toward the 750?
No. Public comment replies are a different API from private replies. Repeating the same public reply text is the bigger risk.
What happens to comments beyond the limit?
The API refuses calls over the limit. A good tool waits and sends the rest in order. Because each comment can be answered for 7 days, nothing needs to be dropped.