2026-08-27

LinkedIn Connection Request Limit 2026: Daily & Weekly Caps

LinkedIn publishes no invitation limit. What the weekly wall looks like, why accounts hit it well below the number vendors quote, and the pace that stays safe for each type of account.

LinkedIn cuts you off at a weekly number it never publishes. The figure passed around is about 100 connection requests, but accounts get walled well below it, the line differs from account to account, and there is no warning you can plan around. One day you click Connect and a modal says you've reached the weekly invitation limit. If you run outreach on your own account, the LinkedIn connection request limit decides how fast you can build pipeline. Most of what's written about it is guesswork dressed up as fact. Here's what's observable, what LinkedIn refuses to publish, and the exact pace PoliteReach ships for each type of account.

LinkedIn publishes no number, and the one everyone quotes is a guess

LinkedIn has never published a number. Its help page on the limit message gives no figure, and Support says it cannot disclose one. What people observe is a warning after too many invites inside a seven-day span, then a hard stop. Vendor blogs settled on about 100; we have watched one of our own accounts walled far under that twice in one week, with nothing hidden inflating its count. The modal doesn't show your count or say when you can send again. It doesn't say whether the source matters either; in practice an invite from search results, a profile page, or My Network draws down the same budget. LinkedIn tightened invitations in 2021 without announcing a figure, and it has not published one since.

Does paying move it? LinkedIn doesn't say. No plan, free or paid, lists an invitation cap among its features, and Sales Navigator buys search filters and InMail credits, a separate channel with its own allotment. Field reports do point the same way, though: Premium accounts get more room, and new or unverified ones much less. That is why PoliteReach paces each account by its type instead of one flat number, and why those bands are our policy, not a LinkedIn promise.

The window rolls, so there's no reset day

The seven-day window is rolling, not calendar. An invite sent Tuesday afternoon stops counting against you the following Tuesday afternoon. There's no Monday reset and no first-of-the-month refresh. LinkedIn doesn't document this mechanic either, but it's easy to verify. Hit the limit on a Thursday and capacity trickles back over the next week, in roughly the same rhythm you spent it.

This has a practical consequence. Burn a week's worth of invites in two days and you're locked out for the better part of a week. Then the whole allotment floods back at once, and the temptation is to burn it again. Spread the same budget across the week and slots free up at about the rate you spend them. The account never stalls.

There is no reset day: every invite frees up seven days after you sent it, one at a time.

Getting walled early is about pace and acceptance rate

Whatever an account's line is, nothing guarantees you reach it. Accounts get warned and walled well under the 100 a week vendors quote. LinkedIn doesn't publish the triggers, but two patterns show up over and over in accounts that get flagged early.

First, pace. A hundred invites spread across five working days and a hundred fired in a single hour are the same volume and opposite signals. No human sends 40 connection requests in 20 minutes at metronome intervals. Software does. LinkedIn has watched software do it for a decade.

Second, acceptance rate. When most of your invites sit ignored, or get flagged by the people receiving them, LinkedIn reads it the way an email provider reads spam reports. LinkedIn doesn't publish an acceptance-rate threshold and I won't invent one. The direction is clear, though. Accepted invites make you look like a networker. A pile of ignored ones makes you look like a scraper with a quota.

Pending invites are a liability, so withdraw them at two to four weeks

Every pending invite is an open bet against your acceptance ratio. Leave 400 of them sitting and you're carrying 400 pieces of evidence that people don't want to hear from you. Nobody accepts a three-month-old invite anyway. It's dead weight with downside.

The fix is boring: withdraw anything still pending after two to four weeks. Manually, that means paging through Sent invitations under My Network and clicking Withdraw one at a time. Nobody keeps that up past week two. PoliteReach will do it for you: switch the cleanup on for an account and invites pending longer than 60 days get withdrawn on a schedule, with the window configurable down to a floor of seven days. It is optional and ships off, because a withdrawal blocks re-inviting that person for about three weeks and cannot be undone.

A jittered daily band beats maxing the week

Say an account's week allows 100. Run at that ceiling and the arithmetic says 14.3 invites a day, every day, forever. That regularity is itself a signature. A person's output wobbles. Some days 9, some days 16, none of them starting at 9:00:00 sharp.

That's why PoliteReach paces each account by the type it reads at sign-in: 5-10 invites a day for a new or unverified account, 18-24 a day once verified, 25-30 a day on Premium, jittered so no two days look alike. A rolling seven-day allowance per account sits on top, 63-70 a week new, 90-100 verified, 135-150 Premium, and that weekly counter, not the daily number, is what actually binds. LinkedIn publishes no invitation limit, so every one of these numbers is ours. Invites go out only during the sending hours you configure, and the automated follow-ups wait for the same window; a reply you send by hand is never held. Notes get typed, not pasted, with per-keystroke delays and randomized pauses before opening, typing, and sending. Every regular pattern you remove is one fewer thing for LinkedIn to correlate.

For founders and small sales teams running their own accounts, a verified account's allowance is also simply enough: 90-100 a week is around 400 a month. If a third of those accept, you've opened about 130 new conversations. Volume isn't the constraint. Writing a note worth accepting is.

Warm up a new account over its first month

A fresh account, or one that's been dormant for months, shouldn't start anywhere near the full daily cap. Going from zero to full cap overnight is the most legible bot pattern there is. Ramp instead.

LinkedIn publishes nothing about account age or dormancy affecting limits, so treat this schedule as field practice rather than doctrine. PoliteReach ships its own version of this as a warm-up ramp you switch on per account, and it is slower than the table above: 8 a day for the first two weeks, 12 in week three, 17 in week four, and a verified account's full 18 to 24 a day only from week five. It is off by default, because slowing an established account down is not always what you want.

The day you hit the limit, stop completely

Hitting the weekly modal once isn't fatal. A human hits it, shrugs, and comes back in a few days. What burns accounts is what happens next: the retry loop. A script that keeps clicking Connect every few minutes after the modal produces a log of dozens of refused attempts, and that log is a cleaner bot signature than anything that came before it.

So stop. Send nothing until the rolling window has freed real capacity, and come back below the pace that hit the wall. PoliteReach does exactly that: an account that hits the wall drops a tier for eight days and probes again before it resumes. PoliteReach applies the same reflex to the scarier case: if LinkedIn throws a security checkpoint at an account, a per-account circuit breaker halts that account's automation immediately, while other accounts keep running. Nothing retries into a wall.

One limit modal is a speed bump; a retry loop after the modal is the flag.

You have to track the rolling seven-day count yourself

LinkedIn shows you pending invitations, not a counter. Nowhere in the interface can you see how many invites you sent in the trailing seven days, which is the only number the limit cares about. If you're doing this by hand, keep the ledger yourself.

1. Log every invite the day it goes out, including one-offs you send manually.
2. Each morning, total the trailing seven days before sending anything new.
3. Keep that total well under the line you last hit, and far lower on a new account, so a miscount or a stray manual invite doesn't put you into the modal.

Or let software count. PoliteReach keeps the rolling seven-day counter per account and won't queue an invite past that account's allowance. Run three accounts and each gets its own window, its own daily jitter, and its own circuit breaker.

PoliteReach is in early access, built by Diverse Labs, and your first 14 days are free. The caps in this post are published on purpose: a tool that won't tell you its send limits is telling you they're too high. If you'd rather your invites went out at a pace set by your account's type, under a counter, than from a spreadsheet, join the waitlist.