Recipients per campaign is the maximum contact count a single Hunter.io sequence can target. The free plan allows 500, Starter 2,500, Growth 5,000, Scale 15,000, and Enterprise negotiates a custom cap. This limit caps how large each outreach campaign can be, so high-volume teams upgrade to Scale to run bigger sequences without splitting them across multiple campaigns each week.
What Is ‘Recipients Per Campaign’ in Hunter.io?
Recipients per campaign is the cap on contacts a single email sequence can target before the campaign must be split into multiple sequences. Each Hunter.io plan sets a different limit, and the cap shapes how teams structure outreach: large lists get divided into campaign batches, while smaller programs run as single sequences.
- Campaign size ceiling: The cap defines the upper bound for any single sequence, forcing list segmentation once the prospect count exceeds the plan limit.
- Sequence reach per send: Recipient cap determines how many contacts each sequence touches, which directly affects daily reach for weekly cadence sends.
- Splitting effort overhead: Lower caps create more campaigns to manage, multiplying tracking and follow-up work across more sequence dashboards.
- Throughput per cycle: Larger caps let outreach throughput scale linearly with credit pool rather than being limited by sequence structure.
- Plan fit signal: Recipient cap is one of three core plan signals (with credits and accounts) that determine which tier matches workload shape.
The cap is often the most overlooked plan signal until a large list forces a tier-mismatch realization.
What Are the Recipients Per Campaign by Plan?
Hunter.io recipient caps step cleanly between tiers: Free at 500, Starter at 2,500, Growth at 5,000, Scale at 15,000, and Enterprise at a negotiated custom cap. The size step between Growth and Scale is intentionally large because it spans the transition from team-cadence sequences to agency-scale sends.
Source: hunter.io/pricing.
The 3x size step from Growth to Scale tracks the typical transition from one-team workflows to multi-client agency operation.
Why Do Campaign Size Limits Exist?
Recipient caps exist to protect deliverability and ensure fair usage across customers. Single oversized sends spike volume on connected inboxes, trigger spam classification, and damage sender reputation, so platform caps keep individual campaigns within deliverability-safe sizes that match the plan’s account capacity.
Platform-enforced caps are deliverability infrastructure rather than artificial scarcity, which is why the cap scales with plan account count.
How Do Recipients, Credits, and Accounts Differ?
The three limits measure different parts of the outreach workflow: recipients cap campaign size, credits cap address-finding and verification volume, and connected accounts cap sending inbox count. Any one of the three can bind first depending on workflow shape and team structure.
Source: hunter.io/pricing.
Understanding which limit binds first prevents over-paying for capacity that the workflow does not actually need.
How Big Should Your Campaigns Be?
Right-size each campaign to weekly cadence and account capacity rather than maximizing single sequence size. Large lists work better when split into batches that match weekly send capacity across rotated inboxes, which protects deliverability and gives cleaner per-batch performance reads.
- Count total prospects: Sum the list size across all segments to identify the full audience that needs to receive the outreach sequence.
- Divide by safe weekly cadence: Split the total by safe weekly send capacity (accounts × 30/inbox × 5 workdays) to find how many weeks the program runs.
- Compare against recipient cap: Map each weekly batch size to the plan’s recipient cap to ensure each sequence stays within limits.
- Split into batches if needed: Break the list into multiple campaigns of cap-or-below size whenever the total exceeds the per-campaign ceiling.
- Stagger campaign launches: Launch batches across consecutive weeks rather than all at once to maintain deliverability and produce cleaner performance data per batch.
The four-step plan turns campaign sizing into a deterministic calculation rather than guesswork.
Example: Splitting a Large List Across Campaigns
A team with 20,000 prospects on the Growth plan (5,000-recipient cap) splits into four campaigns of 5,000 each, launching one per week over four consecutive weeks. The same list on Scale (15,000-recipient cap) needs just two campaigns, freeing weekly cycles for additional segments or follow-up programs.
The Scale recipient cap directly reduces program management overhead by halving the number of separate campaigns to track for the same list.
What Are the Risks of Oversized Campaigns?
Pushing campaigns at or above the recipient cap concentrates send volume and risks deliverability damage. The risks include spam classification, bounce-rate spikes, sender reputation drops, provider throttling, and ultimately lower reply rates as inbox placement degrades over the campaign’s lifetime.
- Spam flagging: Oversized initial sends spike volume on connected inboxes, triggering bulk-mail classification that drops inbox placement for the rest of the campaign.
- Bounce-rate spikes: Large untested batches surface invalid addresses all at once, producing bounce spikes that mailbox providers interpret as poor list hygiene.
- Reputation drop: Concentrated volume damages sender reputation across the sending domain, which takes weeks of careful sending to recover from once degraded.
- Provider throttling: High-volume single sends trigger throttling on mailbox providers, slowing message delivery and reducing same-day reach across the recipient list.
- Lower reply rates: Reply rates fall as inbox placement degrades, since messages landing in spam folders rarely produce responses regardless of copy quality.
Sizing campaigns to the cap rather than maximizing them is the deliverability-protective default for serious outreach programs.
How Does the Recipient Cap Affect Plan Choice?
Teams routinely running campaigns above 5,000 recipients need Scale; teams running above 15,000 need Enterprise. The recipient cap forces the tier step before credit volume or account count does for high-volume outreach programs with large segmented lists.
Cold email cadence works best when batch sizes match weekly inbox capacity rather than maximizing single-campaign reach, because per-batch deliverability data drives smarter list iteration.
HubSpot, Sales operations resources
Recipient cap is one of three plan-fit signals that drive the tier decision; for high-volume teams, it is often the deciding one.
How Do You Choose a Plan by Campaign Size?
Map the largest realistic campaign size needed against each plan’s recipient cap, then confirm credits and accounts also fit. The lowest tier that meets all three signals is the right pick; tier overshoot leaves capacity unused, and tier undershoot forces inefficient list splitting.
- Identify largest single campaign: Project the largest single sequence the workflow will run in a typical month, including outliers from large client segments.
- Compare against tier caps: Map that size to plan caps (Starter 2,500, Growth 5,000, Scale 15,000) to find the lowest tier with enough recipient headroom.
- Confirm credit volume fits: Verify the same tier’s monthly credit pool covers projected research and verification load across all campaigns.
- Verify account count fits: Confirm the tier’s connected-account cap supports the safe daily send rate the projected campaign volume requires.
- Pick the lowest matching tier: Choose the lowest tier that satisfies all three signals to balance capacity against monthly cost.
Recipient cap, credit pool, and account count are three independent dimensions; the right plan satisfies all three rather than just one.
How Do Recipient Limits Shape Your Hunter Choice?
Teams running campaigns consistently above 5,000 recipients should plan for Scale; campaigns above 15,000 push toward Enterprise. The recipient cap is often the deciding plan-fit signal for high-volume programs because list size is harder to compress than credit consumption or inbox count.
Recipient caps are one of the clearest tier signals in Hunter.io’s pricing because they map directly to campaign workflow size.
Growth Hack Suite, Hunter.io pricing guide
Recipient cap interacts with credit pool and account count, but it often dictates the tier step on its own for high-volume work.
Campaign Planning Checklist Before Large Launches
A clean large-campaign launch rests on five confirmations: list split to cap, inbox rotation configured, list verified, sends staggered, and reply monitoring active. Working the checklist before launch avoids the common deliverability traps of high-volume outreach.
- Split list to recipient cap: Divide the prospect list into batches that each stay within the plan’s recipient cap to avoid forced platform splits.
- Rotate sends across inboxes: Configure the campaign to distribute sends across all connected accounts, lowering per-inbox volume below provider thresholds.
- Verify the list first: Run the list through email verification before sending to remove invalid addresses and prevent bounce-rate spikes.
- Stagger send timing: Stagger sends across business hours and across days rather than launching the full batch in one window.
- Monitor reply and bounce rates: Track reply, bounce, and complaint rates after the first 24 hours to catch deliverability issues before they damage the full campaign.
The checklist takes about thirty minutes per campaign and prevents weeks of reputation damage from a single bad launch.
Related Campaign & Plan Guides
Recipient cap sits inside the wider Hunter.io pricing context. The full pricing guide covers all five tier limits in one place, alongside credit-pool and account-count comparison for complete plan-fit analysis.
Email marketing is the act of sending a commercial message, typically to a group of people, using email, with each message contributing to the sender’s overall relationship with the audience.
Wikipedia, Email marketing
Recipient sizing is a relationship variable as much as a technical one, since each batch shapes how prospects experience the brand.
Recipients Per Campaign: Frequently Asked Questions
How many recipients per campaign does Hunter.io allow?
Free 500, Starter 2,500, Growth 5,000, Scale 15,000, and Enterprise negotiates a custom cap. Each tier raises the ceiling for single-sequence size.
What does ‘recipients per campaign’ mean?
The maximum number of contacts a single email sequence can target before the campaign must be split into multiple sequences within the plan’s cap.
Why is there a recipient limit?
To protect deliverability and ensure fair platform usage. Caps prevent oversized single sends that would trigger spam classification and damage sender reputation.
How big should my campaigns be?
Size each campaign to weekly send capacity, not to the cap. Split large lists across multiple campaigns staggered over consecutive weeks. See the full Hunter.io pricing guide for tier-fit comparison.
Which plan allows the largest campaigns?
Scale allows 15,000 recipients per campaign. Enterprise negotiates a custom cap for larger needs, typically above 15,000.
Is recipients the same as credits?
No. Recipients cap campaign size; credits cover finding and verifying email addresses. Both move independently across the workflow.
What happens if my list exceeds the cap?
Split it into multiple campaigns of cap-or-below size, launched on staggered weeks for deliverability and cleaner per-batch performance reads.
Do oversized campaigns hurt deliverability?
Yes. Single oversized sends spike volume, trigger spam classification, raise bounce rates, and damage sender reputation across the sending domain.
How does the cap affect plan choice?
Needing larger single campaigns pushes the choice toward Scale (15,000) or Enterprise (custom). The cap is often the deciding signal for high-volume workflows.
Can I run multiple campaigns at once?
Yes. Within account and credit limits, several campaigns can run simultaneously. The recipient cap applies per campaign, not across the account total.
How many recipients does Growth allow?
Growth allows 5,000 recipients per campaign and 10 connected sending accounts, enough for most weekly team-cadence outreach.
Which plan fits high-volume outreach?
Scale fits high-volume work. Its 15,000-recipient cap and 25,000 credits per month support large segmented lists and frequent campaign cadence. See the Hunter.io pricing breakdown.
Pick the Plan That Fits Real Campaign Size
Recipient cap is one of the three core plan-fit signals. Map projected campaign size to each tier’s ceiling, confirm credits and accounts also fit, and pick the lowest matching tier.
Start free, scale campaign size when ready.
Try Hunter.io Free → See Full Pricing →No card required for the free plan
