2026-08-27

LinkedIn Connection Request Limit 2026: Daily & Weekly Caps

LinkedIn caps invites at ~100 a week on a rolling window. What triggers it, why accounts get throttled below 100, and the daily pace that stays safe.

LinkedIn cuts you off at roughly 100 connection requests per week. Not exactly 100, not on a schedule it publishes, and not with any 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 numbers PoliteReach ships as defaults.

The cap is about 100 invites a week, and paying doesn't raise it

LinkedIn has never published the exact number. What people observe, consistently, is a warning somewhere around 100 invites inside a seven-day span, then a hard stop. 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. The current level dates to 2021. LinkedIn cut a much higher ceiling that year without announcing it, and the number hasn't moved since.

Paying doesn't move it. Sales Navigator buys search filters and InMail credits; InMail is its own messaging channel with its own allotment. No LinkedIn plan, free or paid, lists a higher invitation cap among its features. Anyone selling higher invite limits with Premium is selling a misreading.

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 100 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. Send 14 a day and about 14 free up every day. The account never stalls.

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

Throttling below 100 is about pace and acceptance rate

The observed cap is a ceiling, not a guarantee. Accounts get warned and restricted well under 100 a week. 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 does it automatically: invites pending longer than 60 days get withdrawn by default, and the window is configurable down to a floor of seven days.

12 to 16 a day beats maxing the cap

The arithmetic says you could send 100 every week. Run at the ceiling and the arithmetic also 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 caps each account at 12 to 16 invites a day, jittered so no two days look alike. The average lands near 14. A rolling seven-day counter per account keeps the total under the ~100 ceiling. Invites only go out during office hours you configure. 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, 14 a day is also simply enough. That's close to 100 invites a week, 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 three weeks

A fresh account, or one that's been dormant for months, shouldn't start anywhere near 14 a day. 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 bakes the idea in as a warm-up ramp. New and dormant accounts start well below the cap and climb to full pace over about three weeks, automatically.

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 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 under about 90, 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 that would break it, so the modal never fires. 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 12 to 16 a day under a counter than from a spreadsheet, join the waitlist.