The counter above tracks the two real limits: 200 characters on a free LinkedIn account and 300 characters on Premium, Sales Navigator, and Recruiter. Toggle your account type before you write and the bar adjusts instantly.
The character limit is only half the picture. The other half is what you actually put inside it. Seven independent datasets covering more than 310,000 tracked connection requests now map how notes really perform, and the length pattern is consistent: notes between 120 and 180 characters outperform both shorter notes and notes that fill the full cap. Everything on this page exists to help you land in that band with something real to say.
Free accounts also carry a monthly personalized note quota — LinkedIn's own Help pages currently split between three and five per month, and community testing reports up to ten depending on account age and LinkedIn's experimentation. Each note you send here is one of a limited monthly budget. Make it count.
What Is the LinkedIn Connection Request Character Limit in 2026?
The character limit on a LinkedIn connection request note depends on your account type. LinkedIn runs two separate limits and has done so since 2023. The number is not 200, and it is not 300 on its own. Both numbers are real, and which one applies to you depends on whether you pay for a LinkedIn subscription.
Free Accounts: 200 Characters Per Note
Basic (free) LinkedIn accounts are capped at 200 characters per connection request note, per LinkedIn Help page a6239760. Spaces, punctuation, line breaks, and emojis all count. The dialog box in the LinkedIn invitation window shows a live counter and simply stops accepting input when you reach 200.
Premium, Sales Navigator, and Recruiter: 300 Characters
LinkedIn Premium (Career, Business), Sales Navigator (Core, Advanced), and Recruiter accounts are capped at 300 characters per note with no monthly limit on how many personalized notes you can send. The extra 100 characters is enough for one more specific sentence, which matters when you have real context to share.
Why Do You Keep Seeing Conflicting Numbers?
The 200-versus-300 confusion has documented origins. The split first appeared in late 2023, when some free-account users started seeing a 200-character box while others still saw 300 — a change period that some publishers describe as an A/B test or UI bug and that screenshots from that period preserved forever. Those screenshots were copied into articles without timestamps: some 2024 guides reported 300 on every plan, and some 2025-2026 guides, including Reactin's and Fuzzy AI's, still state that 300 applies to every account in 2026. The mobile apps add one more layer — some app versions cap the note near 200 regardless of plan.
Against all of that, LinkedIn's own Help Center currently documents the split directly: page a6239760 states 200 characters for basic accounts and 300 for Premium. The authoritative check is still the simplest one: open the LinkedIn invitation dialog on your own account. If the counter in the box reads /200, your account uses the free limit. If it reads /300, you are on Premium or a paid plan. The counter in your own dialog is the only source of truth for your account.
The Complete LinkedIn Character Limit Reference Table
Every text field on LinkedIn has its own character cap. This table covers all of them so you never have to guess again.
| Content Type | Character Limit | Notes |
|---|---|---|
| Connection request note (free) | 200 |
Spaces, emojis, line breaks all count — this counter's focus |
| Connection request note (Premium / Sales Nav / Recruiter) | 300 |
Same counting rules — LinkedIn Help a6239760 |
| LinkedIn post | 3,000 |
First ~210 chars show before the "see more" fold |
| Profile headline | 220 |
60–70 chars visible in search results |
| Profile About / Summary | 2,600 |
~300 chars visible before see-more on desktop |
| Direct message (DM) to a connection | 8,000 |
Available after the request is accepted |
| LinkedIn comment | 1,250 |
AuthoredUp's March 2026 testing; one source reports a cut to 1,000 in May 2026 — dispute kept |
| Experience description | 2,000 |
Per role |
| InMail subject line | 200 |
Premium and Sales Nav only — subject line required |
| InMail body | 1,900 |
Per LinkedIn Help "Send an InMail Message"; some Premium experiences report ~2,000 |
| Company page tagline | 120 |
Appears under the company name |
| Company page description | 2,000 |
Different from the personal About limit |
| LinkedIn article title | 100 |
Pulse / article posts |
| LinkedIn article body | 125,000 |
Long-form publishing |
| Group post | 3,000 |
Same cap as a regular post |
| Event description | 5,000 |
LinkedIn Events pages |
Connection, post, headline, About, comment, and InMail limits verified against LinkedIn Help pages as of September 2026. LinkedIn adjusts limits without announcement, so check the in-dialog counter when writing at the boundary of any cap.
What Counts Against Your 200 or 300 Characters?
The LinkedIn Help page gives you the number but not the counting mechanics. People hit the cap sooner than expected because several characters cost more than they appear to.
Every typed character counts:
- Spaces: 1 character each
- Punctuation marks: 1 character each
- Line breaks: 1 character each. A three-paragraph note with two line breaks spends 4 to 6 characters on blank lines alone.
- Accented characters and non-Latin scripts: 1 character each. Writing in French, German, Spanish, or Arabic does not cost more than English.
Emojis cost more than they look. LinkedIn counts characters the way JavaScript does, in UTF-16 code units — the same counting this page's tool uses, because the invitation dialog is a JavaScript text box. A few third-party counters report emojis as a single character; they are counting Unicode code points rather than the UTF-16 code units the dialog's JavaScript uses, so budgeting the higher figure is the safe play. This matters for emojis specifically:
- Standard emoji (thumbs up, check mark, simple face): 2 characters
- Flag emoji: 4 to 7 characters depending on the flag
- Skin-tone emoji variants: 4 characters
A note with three emojis can cost 6 to 20 characters in emoji alone. Most high-performing connection notes in the data use no emojis at all.
Links are never worth including. A URL in a connection request note is counted letter by letter with no shortening. A typical LinkedIn profile URL costs 35 to 45 characters. A blog post link costs 50 to 80 characters. That is roughly a third to half of a free account budget. Links inside connection request notes are also a documented spam signal on LinkedIn, which means they can reduce acceptance rates independent of what the note says.
Personalization variables expand at send time. If you draft notes with a placeholder like {firstName}, the character count in the tool reflects the placeholder text, not the rendered name. The actual send uses the full name. A note that fits at 195 characters with {firstName} fills to 207 characters when the recipient's name is "Bartholomew". This is why every LinkedIn automation tool recommends writing your note to fit at roughly 20 to 30 characters under your account cap when using personalization variables — and why the counter above includes a send-time name check that computes the worst case for you.
What Happens When You Hit the Cap
LinkedIn does not show an error when you paste text that exceeds the limit. The text box silently stops accepting input. If you paste a 260-character note into a free account dialog, the last 60 characters are cut without warning. Always re-read the end of a pasted note before hitting Send.
The Monthly Personalized Note Quota for Free Accounts
The character limit gets all the attention. The monthly quota is the constraint that actually damages outreach. Free LinkedIn accounts can only send a limited number of personalized notes per month before LinkedIn strips the note field from all remaining connection requests until the next month.
How Many Notes Can Free Accounts Send Per Month?
This number is genuinely in dispute — and the dispute runs through LinkedIn's own documentation. As of September 2026, LinkedIn's Help Center gives two different answers on two different pages:
- Three per month: stated by the dedicated "Personalize invitations to connect" Help page (a563153), and reported by Contentin.io citing LinkedIn Help in 2026
- Five per month: stated by two other Help pages — "Invitation limit reached" (a550555) and "Differences between InMail Messages and personalized invitations" (a6239760) — and echoed by Taplio, LinkedHelper, and TryKondo
- Five to ten per month: reported by Dripify's help documentation and Salesforge community testing on mature accounts
What Happens When You Hit the Monthly Limit
- LinkedIn removes the note field from your connection request dialog for the remainder of the month.
- You can still send connection requests, they just go without any attached note.
- The quota resets on a personal monthly cycle, not on the calendar month. LinkedIn does not document the exact reset mechanics, and community reports consistently describe the note field returning on a date that is not the 1st — so treat the return of the note field as your reset marker rather than any calendar date.
That last point confuses more free-account users than any other limit on this page. People exhaust their notes early in a month, wait for the 1st, find the note field still missing, and assume something is broken. Nothing is broken — the window simply has not rolled over yet. The reset follows your account's own undocumented cycle, which you can infer from when the note field returns.
How the Quota Affects Your Strategy
If you are on a free account and run structured outreach, the monthly note budget matters more than the character limit. A few implications:
- Save personalized notes for the highest-priority contacts where you have specific, genuine context.
- Use blank connection requests for contacts where you have no real shared context. Data shows blank requests perform as well or better on acceptance rate when the note would have been generic anyway.
- Withdraw pending invitations older than 2 to 3 weeks to protect your sender health score. LinkedIn interprets a large backlog of unanswered invitations as a spam signal and can tighten your weekly invitation ceiling. Withdrawing a request also means you cannot re-invite that same person for approximately 3 weeks, so time your withdrawals carefully.
Premium Removes the Monthly Cap Entirely
LinkedIn Premium, Sales Navigator, and Recruiter accounts face no monthly limit on personalized notes. You can send a note with every connection request up to your weekly invitation cap. This, more than the 100-character increase, is often the practical reason B2B outreach teams upgrade to at least LinkedIn Premium.
The Weekly LinkedIn Connection Request Limit in 2026
LinkedIn caps how many connection requests you can send in a rolling 7-day window. The weekly limit is not tied to a fixed calendar day. When you send your first invitation on a Wednesday at 2pm, your window resets the following Wednesday at 2pm.
What the Numbers Actually Are
LinkedIn does not publish a hard weekly limit. The numbers below are community-observed and consistent across multiple outreach tools as of mid-2026:
| Account Type / Condition | Observed Weekly Ceiling | Safe Daily Pace |
|---|---|---|
| New account (under 3 months old) | 20 to 50 invitations | 5 to 10 per day for warmup |
| Established account, SSI score below 50 | 50 to 80 invitations | Under 15 per day |
| Established account, standard | ~100 invitations | 15 to 20 per day |
| High SSI score (70+), strong acceptance rate | Up to 150 to 200 invitations | 20 to 25 per day |
| Sales Navigator with strong account health | Up to 200 to 250 invitations | 25 to 30 per day |
| Restricted / warned account | 20 to 30 invitations | Resume slowly after restriction lifts |
These are behavioral ceilings, not guaranteed quotas. Sending all 100 invitations in a single morning is a bot signal regardless of account type. LinkedIn's anti-spam system watches the pattern of when invitations are sent, not just the total count.
What Triggers Limit Throttling
- An acceptance rate sustained below 20 to 30%. LinkedIn interprets low acceptance as evidence you are reaching out to people who do not know you, which reduces your weekly ceiling algorithmically.
- "I don't know this person" reports from recipients. Each report actively damages your sending capacity. A handful of reports on one account can drop the weekly limit significantly.
- A large pending invitation backlog. LinkedIn warns above roughly 700 to 1,500 outstanding invitations, depending on account age. A pile of unanswered requests reads as bulk spam behavior.
- Sending in unnatural bursts. A rapid-fire string of invitations spaced seconds apart — pacing no human operator keeps — is a bot signal regardless of account quality, and LinkedIn's Help Center states plainly that suspected automation use can restrict the account.
- New accounts with no posting or engagement history launching high-volume outreach immediately.
The Social Selling Index and Your Weekly Limit
LinkedIn's Social Selling Index (SSI) is a score from 0 to 100 measuring profile completeness, networking activity, engagement, and relationship building. It is free to check at linkedin.com/sales/ssi. It is also the one demographic variable that meaningfully moves your weekly ceiling — sender seniority and company size barely register in the 13.2M-request benchmark data, but SSI does:
| SSI Score | Observed Weekly Invitation Ceiling | What It Means |
|---|---|---|
| Below 50 | ~50 to 80 per week | Regularly throttled below the 100 baseline |
| 50 to 69 | ~100 per week | The standard established-account ceiling |
| 70 or above | Up to 200 per week | Plus stronger resilience against throttling |
| 70+ on Sales Navigator, mature account | 150 to 250 per week | The highest community-observed ceilings |
Accounts scoring 70 or above consistently see higher weekly ceilings in community testing (Cleverly, Konnector, OutX, Wandify). Accounts below 50 regularly see throttling below the 100-invitation baseline. Improving your SSI — completing your profile, posting regularly, engaging with your network, and building relationships rather than just sending requests — is the primary legitimate way to expand your effective weekly capacity.
How to Recover After a Restriction
The most common restriction is the "You have reached the weekly invitation limit" message. This is a soft lock, not a ban. LinkedIn's Help Center (a550555) states that the restriction "typically lasts one week" — and that withdrawing pending invitations will not remove it, so a purge alone does not speed the recovery. Do not send test requests before it lifts because that restarts the throttle clock. When the limit lifts, resume at 5 to 10 invitations per day for the first week before returning to normal volume.
Should You Add a Note to Your LinkedIn Connection Request? What 7 Datasets Actually Say
This is the most debated question in LinkedIn outreach. The data is genuinely contradictory at the surface level because different studies measured different things. Here is every major dataset reconciled in one place.
The Full Data Picture
| Source | Dataset Size | Acceptance With Note | Acceptance Without Note | Post-Accept Reply Rate |
|---|---|---|---|---|
| ReactIn (2024 to 2025) | 80,000+ requests | 28 to 45% | 55 to 68% | Not measured separately |
| Botdog (2025 to 2026) | 16,492 requests | ~28% lower (relative) | ~80% higher (relative) | Not measured separately |
| Reachium (Jan 2025 to Aug 2026) | 196,696 requests | Inconclusive (~27%) | Inconclusive (~27%) | 47.8% with note vs 25.5% without |
| Expandi / Cleverly (2025 to 2026) | 13.2M to 20M requests | 26.42% | 26.37% | Reply rate nearly doubles with a note |
| Crispy (2026) | Tens of thousands | 45 to 60% for specific notes | 55 to 68% blank | Not measured separately |
| SalesRobot (2026) | Industry analysis | ~45% personalized | ~15% to 26% generic | Not isolated |
| Expandi H2 2026 benchmarks | 13.2M+ requests | 28.5% average | Similar | Note reply rate fell 37% in 12 months (3.5% to 2.2%) |
What the Data Actually Means
On raw acceptance rate: blank requests outperform generic notes in nearly every large dataset. This is not because blank requests are better — it is because most notes in these datasets are generic templates. When studies isolate specifically personalized notes referencing a real trigger, acceptance rates climb back to 45 to 60%. Expandi's 20M+ analysis is the cleanest demonstration: 26.42% acceptance with a note versus 26.37% without — statistically identical — while their campaign-level analysis found notes referencing a follow, a group, or a shared network accept at 1.8 to 2.7 times the 30.2% baseline.
On post-acceptance reply rate: this is where notes clearly win. Reachium's 196,696-request dataset — among the largest to isolate reply behavior by note presence — found 47.8% of accepted connections replied when the request carried a note versus 25.5% when it did not. Belkins' 2026 study of 15M+ outreach touchpoints found the same shape: 8.2% reply after a noted request versus 5.3% after a blank one. Expandi's cross-account data puts the lift at "nearly double." The note does not get you connected more often. It gets you into a conversation more often after you connect.
On template fatigue: Expandi's H2 2026 benchmarks show the connection-note reply rate fell from 3.5% in May 2025 to 2.2% in April 2026, a 37% relative decline in 12 months. This decline reflects saturation, not a flaw in the concept. Notes that reference a real trigger still perform. Notes that recycle the same structure across thousands of sends are hitting an increasingly resistant audience.
The Decision Framework: When to Send a Note
Before you draft a note, answer one question:
- YES: send a note. Keep it between 120 and 180 characters. Leave the pitch out entirely.
- NO: send a blank connection request. A blank request with a complete, credible profile regularly outperforms a generic note in every large dataset.
Specific triggers that clear the context test:
- A post they wrote that you reference by topic
- An event you both attended or are both registered for
- A mutual connection who suggested you reach out
- A group you both belong to with a specific thread you can name
- Shared alumni, company, or professional community
- A specific piece of their work, research, or output you engaged with
Triggers that do not clear the context test:
- "I came across your profile and was impressed"
- "We are both in [industry] and I think we could collaborate"
- "I would love to learn from your experience"
- Any opening that could apply to 500 different people without changing a word
The 120 to 180 Character Sweet Spot
ReactIn's 80,000-request dataset shows a consistent pattern when acceptance rate is broken down by note length. Notes between 120 and 180 characters outperform notes that fill the full 200 or 300 characters, and outperform very short notes under 80 characters.
| Note Length | Acceptance Rate Range | Why It Performs This Way |
|---|---|---|
| 0 characters (blank) | 55 to 68% | Low-friction, reads as organic |
| 1 to 80 characters | 48 to 60% | Feels light and real, limited context |
| 120 to 180 characters (sweet spot) | 52 to 60% | Personal, deliberate, enough specific context |
| 200 to 250 characters | 38 to 48% | Starting to read as rehearsed outreach |
| 280 to 300 characters | 25 to 35% | Reads as automated pitch or template |
The independent 13.2M-request Expandi benchmarks point in the same direction from the other side: their top-performing connection notes run 150 to 200 characters, and their state-of-outreach report states plainly that "the top connection notes reference an existing relationship or shared context" while the longest notes underperform. Two datasets, two methods, one conclusion: fill less, mean more.
Why Shorter Wins Beyond Just the Data
There is a structural reason the 120 to 180 range outperforms longer notes that the data alone does not explain. When a recipient receives a connection request on LinkedIn, they see a preview of the note in their notifications panel. That preview truncates long notes — community testing puts the visible window at roughly the first 80 to 100 characters. A note that fits inside the preview window lands as a complete, readable thought. A note that overflows the preview window requires the recipient to click to expand it, which adds friction.
Notes between 120 and 180 characters typically read as complete in one view: a specific reason to connect, no pitch, no call to action beyond connecting. Notes that fill 280 to 300 characters often require expansion and signal that the sender is trying to pre-sell something inside an invitation.
Why Very Short Notes Also Underperform
Notes under 80 characters perform reasonably well but rarely carry enough specific context to clearly distinguish your request from a generic one. "Saw your post, would love to connect" at 42 characters is better than "I would love to add you to my professional network" but it still does not tell the recipient which post or why it mattered to you specifically.
The 120-character floor exists because that is roughly the minimum required to name a specific trigger and make a brief, honest connection to why you are reaching out, without padding or filling space.
Industry Acceptance Rates: Benchmark Against Your Own Row
Averages hide the number that actually applies to you. Expandi's H2 2026 benchmarks — 13.2 million connection requests across 60+ sender industries between May 2025 and April 2026 — show acceptance ranging from 17.5% to 40.1% depending on who sends. A recruiter and a SaaS seller sending identical notes will see materially different results, and neither is doing anything wrong:
| Sender Industry | Acceptance | Connection-Note Reply | Message Reply |
|---|---|---|---|
| Staffing & Recruiting | 36.5% | 6.6% | 18.9% |
| Venture Capital & Private Equity | 34.9% | 5.5% | 11.0% |
| Human Resources | 30.5% | 4.2% | 9.7% |
| Marketing & Advertising | 29.4% | 2.4% | 10.6% |
| Information Technology & Services | 28.4% | 2.6% | 10.5% |
| Platform average (all industries) | 28.5% | 3.0% | 10.4% |
| Hospital & Health Care | 27.7% | 3.4% | 10.6% |
| Computer Software (SaaS) | 27.5% | 2.8% | 8.8% |
| Financial Services | 26.0% | 2.2% | 10.3% |
| Telecommunications | 21.8% | 1.8% | 11.2% |
| Apparel & Fashion | 19.9% | 1.5% | 7.1% |
Three readings worth taking from this table. First, Staffing & Recruiting runs at roughly 2x the platform average on every metric — recruiting messages are reciprocal by nature, because the recipient often needs what is being offered. Second, sender seniority and company size barely move these numbers (all seniority buckets land in a 3-point band in the same dataset), but industry moves them by nearly 20 points. Third, the benchmark for "good" depends on your row: LeadRiver's 2026 benchmarks call 30–45% healthy and below 20% a targeting red flag, which means a software sender at 27% is on benchmark while a recruiter at 27% is ten points below peers. The same number, opposite diagnosis.
How to Write a LinkedIn Connection Note That Works
The Zero-Pitch Rule
Every study measuring connection request effectiveness produces the same finding about pitching inside the note: it reduces acceptance and it reduces reply rates after acceptance. The note is not a sales channel. It is a single-sentence explanation of why you specifically are connecting to this specific person. The pitch, the demo request, the 15-minute calendar link, the product description: all of those live in the first message after the connection is accepted, where you have 8,000 characters and the person has already indicated interest by connecting.
The CTR Writing Framework
The CTR framework (Context, Tie, Request) maps directly to how 200 characters should be allocated:
- Context (approximately 70 to 90 characters): What prompted you to reach out. A specific post, an event, a group thread, a referral from a mutual contact. This is the opening and the most important part.
- Tie (approximately 40 to 60 characters): What connects you to this person or why their work is relevant to what you do. One short phrase. Not a biography.
- Request (approximately 20 to 40 characters): The simplest possible ask. "Connecting to follow your thinking" or "Would love to be in your network" or nothing explicit at all, because the note itself is the request.
In practice, many effective notes omit the explicit request because the act of sending a connection request is already the ask. The note explains the why. The action explains the what. The Note Builder above implements this exact framework: fill in the Context, Tie, and Request fields and it generates three variants sized for the sweet spot.
What to Exclude Every Time
- A link to anything
- A meeting or call request
- A product, service, or company description
- "I came across your profile" as an opener
- Any opener that contains the word "impressive"
- Emojis used as punctuation or filler
- A self-introduction longer than one clause
- Any sentence that could apply to every person in your target list without changing a word
What to Include Every Time
- The specific trigger for this particular outreach
- One word or phrase that places you in the recipient's world
- A tone that sounds like a person, not a campaign
10 LinkedIn Connection Note Examples by Scenario
Every example below fits within 180 characters. Character counts are noted at the end of each. All use a specific trigger and zero pitch.
1. Shared Event
Your talk at SaaS Connect on activation loops was the clearest framing I have heard this year. Would love to stay in touch beyond the conference.
145 characters
2. Mutual Group
Saw we are both in the GTM Europe group. Your take on intent-based outbound in the thread last week was worth bookmarking. Connecting.
134 characters
3. Post Engagement
Your post on why win rates matter more than reply rates was a breath of fresh air. Connecting so I do not miss the next one.
124 characters
4. Mutual Connection
Maria suggested I reach out. We are both working on PLG motions for technical buyers. Would love to compare notes.
114 characters
5. Newsletter Reader
Been reading your newsletter for months. The piece on outbound that actually scales finally pushed me to send the invite.
121 characters
6. Shared Customer
We both work with Doctolib, on different sides. Curious to swap notes on how the deal lifecycle looks from your end.
116 characters
7. Conference You Both Attended
Heard great things about your session at SaaStock on retention math. Connecting so I do not lose track of your work.
116 characters
8. Alumni Connection
Fellow EM Lyon alum here. Saw you moved into RevOps at Aircall. Connecting because that is the path I am exploring next.
120 characters
9. Job Seeker to Target Company Employee
I am exploring product roles and your path from IC to PM at a company like yours is exactly what I am trying to understand. No ask, just connecting.
148 characters
10. Direct and Honest
Been following your work on community-led growth for a while. No pitch, just want to be in your network.
104 characters
3 Examples of What Not to Send
For contrast, these are the note types that consistently underperform in every study:
Hi [Name], I came across your profile and was really impressed by your experience in [industry]. I think we could have a lot of synergies and I would love to connect!
166 characters — but no specific context
Hi [Name], I am a [role] at [Company] and we help [titles] achieve [result]. Would love to show you how we do it. Here is a link: [URL]
135 characters — pitch and link
Hi [Name], let's connect!
25 characters — no context
Connection Request Note vs InMail vs DM: Which Box Are You Actually In?
The most common confusion in LinkedIn outreach is mixing up the three different text boxes. Each serves a different purpose and has a different character cap.
How to Tell at a Glance
- Counter reading /200 or /300: you are in the connection request note
- No counter or counter ending in /8000: you are in a regular direct message to an existing connection
- Subject line field present above the message box: you are in an InMail
The Character Limit Comparison
| Message Type | Character Limit | Best Use Case |
|---|---|---|
| Connection request note (free) | 200 |
First touch, explain why you are connecting |
| Connection request note (Premium / Sales Nav) | 300 |
First touch with more room for context |
| InMail subject | 200 |
Cold outreach bypassing the connect step |
| InMail body | 1,900 |
Long-form cold pitch to non-connections |
| DM after acceptance | 8,000 |
Follow-up, nurture, pitch, full context |
When InMail Beats a Connection Request
InMail bypasses the acceptance step and goes directly to the recipient's inbox. It costs a credit. LinkedIn's own response-timing data (published by LinkedIn's talent team) found 65% of InMail responses arrive within 24 hours and 90% within one week — so when an InMail is going to work, it works fast. The narrow use case where InMail outperforms a connection request: senior executives and decision-makers, whose acceptance of connection requests from strangers is often reported below 10 to 15%. If someone's acceptance rate is low enough that a connection request is essentially a cold email that gets ignored, paying for an InMail credit to reach their inbox directly can be worth the cost. For most outreach, send the connection request first, use InMail credits for people who never accept.
One more data point on channel choice: in Expandi's restricted analysis of nearly 11,000 campaigns, Sales Navigator-sourced leads accepted only 1.3 percentage points more than CSV-imported ones — about one additional acceptance per 77 requests. The upgrade that meaningfully changes your numbers is targeting and note quality, not the lead source.
The Post-Acceptance DM Strategy
Once a connection accepts, you have 8,000 characters in the DM window and a warmer context to work from. Expandi's H2 2026 benchmarks put the peak first-message reply rate — 8.5% — on messages of 150 to 200 characters, so keep the opening DM short, put a single question at the end, and leave the pitch for later in the thread. The higher reply rate tied to connection notes comes from the note pre-qualifying who accepts, meaning the people who accept a specific, contextualized note are already more likely to engage. Do not waste that signal by opening the follow-up DM with a pitch.
Best practice: send the first DM within 24 to 48 hours of acceptance. Botdog's 16,492-request study found 63% of acceptances happen within 24 hours and 88% within 7 days. The moment of highest engagement is within the first 24 hours. Waiting a week means losing the warmth of the acceptance.
All LinkedIn Connection Request Limits in 2026: The Complete Reference
One table, every number, sourced. Flag anything marked "community-observed" when citing for decisions at scale.
| Limit | Free / Basic | Premium | Sales Navigator | Recruiter |
|---|---|---|---|---|
| Note character limit | 200 characters | 300 characters | 300 characters | 300 characters |
| Monthly personalized notes | 3 to 5 (LinkedIn's pages split; community reports up to 10) | Unlimited | Unlimited | Unlimited |
| Weekly connection requests | ~100 rolling (community-observed) | ~100 rolling | ~100 to 200 (SSI-dependent) | ~100 to 200 |
| Daily soft cap before throttle | ~20 to 25 | ~20 to 25 | ~25 to 30 | ~25 to 30 |
| Optimal note length (data-backed) | 120 to 180 chars | 120 to 200 chars | 120 to 200 chars | 120 to 200 chars |
| Max first-degree connections | 30,000 | 30,000 | 30,000 | 30,000 |
| Invitation expiry | 6 months | 6 months | 6 months | 6 months |
| Re-invite cooldown after withdrawal | ~3 weeks | ~3 weeks | ~3 weeks | ~3 weeks |
| Pending invite warning threshold | ~700 to 1,500 | ~700 to 1,500 | ~700 to 1,500 | ~700 to 1,500 |
LinkedIn does not officially publish weekly invitation caps, daily soft caps, or pending invite warning thresholds. The figures above are consistent across Taplio, Wandify, LeadLoft, LinkedRent, Konnector, and community testing as of August 2026. Treat them as safe operating guidelines, not guaranteed numbers.
How to Use This LinkedIn Connection Request Character Counter
The counter is designed around the real structure of how LinkedIn processes notes. Here is how each feature maps to a real decision.
- Toggle your account type before you write. The Free (200 char) and Premium (300 char) buttons switch the limit the progress bar tracks against. If you type in the Premium mode but you are on a free account, you will cut yourself off in the LinkedIn dialog before you expected.
- Watch the zone bar, not just the remaining count. The green sweet-spot zone marks 120 to 180 characters. Landing in that zone is the goal. Reaching zero characters remaining is not.
- Set the send-time name check. Enter the longest recipient name on your list and the counter shows the worst-case character count after your
{firstName}-style placeholder expands — the number that decides whether the note actually sends. Automation tools recommend 20 to 30 characters of slack when drafting with variables; this makes the slack visible. - Check the quality panel. It flags the five problems that sink notes: unfilled name placeholders like
{FirstName}, generic template phrases, pitch language, a missing specific context anchor, and length outside the sweet spot — plus buzzword, emoji-cost, and all-caps checks. A note that clears every flag is ready to send. - Read the invitation card preview. The preview shows your note the way the recipient sees it: in the invitation card that appears in their notifications, in the email version LinkedIn sends, and in Messages under Invitations. If the note reads as specific and human in that card, it will read that way to the recipient.
- Benchmark against your industry row. The acceptance table under the counter lists average acceptance by sender industry from Expandi's 13.2M-request benchmarks. A software sender at 27% is on benchmark; a recruiter at 27% needs new targeting, not a longer note.
- Use the Note Builder only when you have real inputs. The scenario presets and CTR (Context, Tie, Request) fields are starting points, not templates to send as-is. Replace every generic placeholder with something specific to the actual person you are contacting.
How to Write a LinkedIn Connection Note That Gets Accepted
- Run the context test first. Before writing anything, ask: can you name one specific thing that connects you to this person? A post they wrote, an event you both attended, a mutual contact, a shared group thread. If you cannot answer that question with something specific, send a blank request rather than inventing a reason.
- Open with the trigger, not a greeting. The first words of your note carry the most weight. Put the specific context first. Their name, then the trigger: your post on activation loops, your talk at SaaStr, we were both in the live session last Thursday. The recipient decides within the first line whether this is a real request or an automated template.
- Keep the note between 120 and 180 characters. Write the note, paste it into the counter, and check where it lands on the zone bar. If you are over 180 characters, cut filler before cutting context. If you are under 120 characters, consider whether you have enough specific detail to make the request feel real.
- Take the pitch out entirely. No product description, no meeting request, no link, no "I would love to share what we do." The connection note has one job: give the recipient a reason to accept. The pitch belongs in the DM you send after they accept, where you have 8,000 characters and a warmer relationship.
- Check your account type limit. Toggle the counter to your account type before you finalize the note. A note you wrote in Premium mode at 270 characters will be cut to 200 if you send it from a free account.
- Verify in the counter and read the preview. Paste the final note into the connection request character counter. Check the remaining characters, confirm the note lands in the sweet-spot zone, read the invitation card preview the way the recipient will see it, and clear any quality warnings before copying to LinkedIn.
About TextCountify
TextCountify builds free character counters and writing tools for every major platform. All tools run in the browser with no signup required and no data stored. The LinkedIn character counter suite covers connection requests, posts, headlines, the About section, comments, and direct messages.