Most pages that claim to list Apollo.io export limits still quote the old export-credit allowances, and several contradict each other. Apollo spent 2025 and 2026 moving accounts onto a single pool of unified credits, so the figures below are the current ones, sourced to Apollo’s own plan comparison and documentation, with a dated note on what changed. There are three separate limits to understand: credits, the per-search display cap, and the selection cap. They interact, and the one that stops you first depends on your plan and the size of your search.
The three limits in one table
| Limit | Value | Applies to | Source |
|---|---|---|---|
| Unified credits | 900 to 72,000 a year by plan | Every email reveal (1 credit) and phone reveal (8 credits), whether on screen or in an export | Apollo plan comparison |
| Display cap | 100 pages of 25 results (2,500 records) per search | Native export, extensions and paste-URL services alike | Apollo Knowledge Base |
| Selection and API cap | 50,000 records | Bulk selection in the app and the people-search API | Apollo API docs |
Credits are consumed; the other two are ceilings. A Basic user with 30,000 credits can export 30,000 emails across the year, but never more than 2,500 from any one search without changing filters, and never more than 50,000 in one selection.
Unified credits by plan
| Plan | Unified credits a year | Approximate per month | Max emails (1 credit each) | Max phones (8 credits each) |
|---|---|---|---|---|
| Free | 900 | 75 | 900 | 112 |
| Basic | 30,000 | 2,500 | 30,000 | 3,750 |
| Professional | 48,000 | 4,000 | 48,000 | 6,000 |
| Organization | 72,000 | 6,000 | 72,000 | 9,000 |
Credits are a shared pool, so the email and phone columns are either-or maximums, not both. A list where every row needs a phone number costs eight times as much as an email-only list. Apollo’s month-to-month price for Basic is reported as both $59 and $65 in different places and is unconfirmed; the per-plan prices and what they buy are covered in Apollo pricing and credits. One further detail remains unconfirmed and should be tested on your own account: Apollo’s help articles do not say how many credits a CSV export charges per row when the email was already revealed, or whether rows without a revealed email are charged at all.
Legacy allowances (no longer provisioned)
The table below describes the structure of Apollo’s legacy credit system so you can recognize it when a vendor page quotes it. The exact legacy figures varied by sign-up date and plan generation, so they are not repeated here as current numbers; if a page you are reading gives separate “export credits” and “email credits” per month, it is quoting this system.
| Legacy credit type | What it covered | Status in 2026 |
|---|---|---|
| Export credits | A monthly allowance of CSV or CRM export rows, separate from reveals | Legacy; folded into unified credits |
| Email credits | Monthly email reveals, with an “unlimited” tier on some legacy plans | Legacy; now 1 unified credit per email |
| Mobile credits | Monthly phone-number reveals | Legacy; now 8 unified credits per phone |
Accounts created under the legacy system were migrated; if your account still shows separate buckets, Apollo’s billing page is the authority for your specific allowance.
The 100-page display cap
Apollo renders search results 25 to a page and stops at page 100. Whatever the result count says, 2,500 records is the most any single search exposes, and page 101 does not exist. The cap is on the search view, which means every tool that reads the search, including native export, Chrome extensions and paste-URL services, inherits it. It is not a credit limit, so it applies equally on Organization and Free. Vendors that advertise “up to 50,000 leads per search URL” are either splitting the search for you behind the scenes or describing the selection cap rather than what the page actually shows. If a tool returns exactly 2,500 rows from a search that reported 30,000 matches, this cap is why.
The 50,000 selection and API cap
Bulk selection in the app and the people-search API are both capped at 50,000 records per request. For native users this matters when pushing a large result set into a list or sequence rather than a CSV. For API users it means a search with more than 50,000 matches has to be split by filter the same way as a search above the display cap. Both limits sit on top of credits: selecting 50,000 records does not cost anything until emails or phones are revealed or exported.
How to split a large search past the page cap
The reliable way past 2,500 rows is to turn one search into several, each returning fewer than 2,500 results, then export each one and dedupe on LinkedIn URL. Use filters that partition the population cleanly:
- Location. Split by country, then by state or metro for large countries. A US-wide search of 20,000 people usually becomes 10 to 15 slices under 2,500.
- Headcount band. Apollo’s employee-count ranges (1-10, 11-20, 21-50, 51-100 and so on) partition companies without overlap.
- Title group. Separate “VP” from “Director” from “Manager”, or split by department.
- Industry. Useful when the search is title-led and spans many sectors.
- Alphabetical company name is a last resort and is only possible where Apollo offers a keyword or name filter.
Paste the resulting URLs into the Apollo search URL parser to confirm each slice carries the filters you expect and to spot slices that still exceed 2,500. The Apollo Exporter paste-URL export accepts each slice URL, collects the rows from your own logged-in session, verifies the emails and returns one CSV or XLSX per slice with the 25 standard Apollo people fields; it bills per exported row rather than per Apollo credit, and sign-up comes with 500 free credits (1 credit is 1 row).
Which limit stops you first?
On Free, credits stop you first: 900 a year is 36 pages of emails. On Basic, a single search rarely exhausts credits, so the 2,500-row display cap is the usual wall. On Professional and Organization, both caps are reachable in a month of heavy use, and the 50,000 selection cap only matters for list pushes and API work. For a step-by-step on the native export itself, see how to export leads from Apollo, and for the alternatives when credits run out, see how to scrape Apollo.