Skip to content
Programmable

LinkedIn connection limits: what LinkedIn actually says

Most articles quote a weekly number. LinkedIn doesn't publish one. Here is what it does publish, and how to work inside limits you can't see.

By the Programmable Social team ·

LinkedIn doesn't publish a weekly invitation limit. Its help pages describe what happens when you reach a limit, not what the limit is. The figures you'll see elsewhere, usually around 100 a week, come from third parties, and they disagree with each other. Treat any exact number as a report, not a rule.

What LinkedIn does say

  • The limit is enforced with a temporary restriction. If you reach it, you may be blocked from sending invitations, and LinkedIn says you'll be able to send again within one week.
  • You can't get out of it early. Withdrawing invitations doesn't remove the restriction, you can't buy more, and LinkedIn says it can't lift the wait.
  • The wait can grow. LinkedIn describes a few hours for a first restriction, a few days for repeated restrictions within a day, and up to a month for restrictions tied to too many outstanding invitations.
  • Withdrawing has a cost. After you withdraw an invitation, you can't invite that person again for up to three weeks.
  • Notes have their own limit. Personalized invitations are limited separately from standard ones. LinkedIn says basic accounts can send a small number of personalized invitations, and third parties report that allowance as monthly. A note can be up to 300 characters.
  • Your network has a ceiling. LinkedIn allows up to 30,000 first-degree connections.

What actually triggers a restriction

This matters more than the number. LinkedIn names two causes: sending many invitations in a short time, and many invitations being ignored, left pending or marked as spam by the people who receive them.

The second one is the useful part. It means the limit responds to how people react to you, not just your volume. A hundred invitations to people who recognise why you wrote and a hundred to strangers who ignore you don't count the same. So the best way to “raise your limit” is to send fewer invitations that people actually accept.

How to work inside a limit you can't see

  1. Spread them out. A few each working day beats a burst on Monday morning. Bursts are named directly as a trigger.
  2. Target harder. Before you send, ask why this person would accept. If the honest answer is “they might”, leave them out.
  3. Warm up first. Comment usefully on someone's post before you invite them. A name they've seen is more likely to be accepted, and less likely to be ignored.
  4. Clear your pending list carefully. Old pending invitations can work against you, but remember the three-week lockout on anyone you withdraw.
  5. Treat a restriction as feedback. LinkedIn says you can't remove it, so wait it out and change what you were doing. Sending the same way the moment it lifts invites a longer wait.

Does paying remove the limit?

LinkedIn's pages don't give a higher published number for paid plans. Third parties report larger allowances and longer notes on Premium, but they vary in what they claim, so check your own invitation screen, which shows the character count that applies to you. And LinkedIn says you can't buy more invitations once you're restricted.

How we handle this in Programmable Social

Because the real limit isn't published, we don't pretend to know it. Limits are conservative by default and set in two places, with the lower one winning: an extension allows 40 sends a day and 10 an hour on LinkedIn out of the box, with at least 20 seconds between sends, and each account has its own caps on the server. Those are our defaults, not LinkedIn's numbers, and staying under them doesn't mean LinkedIn permits the tool. Read what LinkedIn's rules say about automation before you decide.

Sources

Checked on October 31, 2026. Platforms change these pages, so check the originals before you rely on them.

Drafted with AI and reviewed against the sources above. This is general information, not legal advice.

Read next