Account health becomes the limit
Desktop filtering runs through a logged-in account. The bigger the list, the higher the chance it hits an automated limit mid-run.
Large lists
Batch workflow
Validate Large Lists Without Checking One by One
A few hundred thousand rows is a different job from a few hundred. Batching, export handling and account health all start to matter — here is how to run bulk validation without it falling over halfway.
Batch 01 · 50,000 rowsNormalised and deduplicated
DoneBatch 02 · 50,000 rowsValidating now
RunningBatch 03 · 50,000 rowsQueued behind batch 02
Queued$2.50per 100,000 numbers
$25per 1,000,000 numbers
1M+rows per upload
0accounts at risk
Why volume changes things
Bulk is not just more of the same
Three problems appear at scale that simply do not exist on a list of five hundred.
Jobs must survive interruption
A run that dies at 60% with no checkpoint means re-checking everything. Batching is what makes progress recoverable.
Dirty data gets expensive
On 500 rows a formatting error is a rounding error. On 500,000 it is thousands of wasted checks and a misleading active rate.
The method
How to run a large job properly
Clean before you spend
Normalise to E.164, drop impossible numbers and deduplicate. This routinely removes 5–20% of a raw list at zero cost.
Split into batches
Work in chunks of 25,000 to 50,000. Each finished batch is progress you keep if something interrupts the run.
Export and label as you go
Save active and inactive output per batch with the date. Never wait until the whole job finishes to write results.
Cost check: cloud validation is $1 per 40,000 numbers — about $2.50 for 100,000 and $25 for a million. At that price, cleaning first saves time rather than money, and batching is about reliability rather than budget.
Which route
Desktop or cloud for large jobs
Volume is exactly where the two diverge most.
| At scale | Desktop Turbo Filter | Cloud checking |
|---|---|---|
| Rows per job | Limited by account health | 1M+ per upload |
| Risk of interruption | Account restriction mid-run | None — no account |
| Cost for 1,000,000 | Covered by the license | About $25 |
| Machine must stay on | Yes, a Windows PC | No |
| Country coverage | Your account reach | 200+, localised routing |
| Automation | Not available | REST API on approval |
If you already run a stable multi-account setup and want unlimited checks on one license, desktop still wins on cost. If a job failing halfway is the thing you cannot afford, use cloud checking.
Go deeper
The detail, if you want it
How do I check WhatsApp numbers in bulk?
Put every number on its own line in a text or CSV file using full international format, load it into WhatsPro Turbo Filter, set a safe checking speed, and start. It processes large lists in batches and lets you export active and inactive numbers as separate files.
What batch size should I actually use?
25,000 to 50,000 rows per batch is the range most teams settle on. Small enough that losing one batch is not painful, large enough that you are not babysitting fifty separate files.
Name each output with the batch number and the date it was validated. When someone asks in three months whether a segment is still fresh, that filename is the answer.
Reading the active rate on a large mixed list
A blended active rate across ten countries tells you almost nothing actionable. Split by dial code first, then judge each market against its own baseline.
WhatsApp adoption is very high across much of Europe, Latin America, South Asia and the Middle East, and comparatively low in the United States where SMS and iMessage dominate. A low US rate is usually accurate reporting rather than a data problem. The country page covers this per market.
Recurring bulk jobs should be automated
If you are validating a large list on a schedule — weekly, or every time a CRM sync lands — uploading files by hand stops making sense.
The REST API uses the same credits as the dashboard and lets you batch programmatically, cache results with a timestamp, and re-validate only what has aged past 60 to 90 days rather than re-checking everything.
Legal and consent at scale
Validating a large list does not create a lawful basis to contact anyone on it, and the rules differ sharply between the EU, UK, US and elsewhere.
Volume tends to attract more scrutiny, not less. Confirm your position with qualified local advice before outreach, and see our terms for the responsible-use conditions that apply to our software.
Quick answers
Frequently asked
How large a list can I validate?
Cloud uploads take 1M+ rows per file, and you can run as many files as your credits cover. Desktop is limited by account health rather than a hard row count.
What does a million numbers cost?
About $25, at $1 per 40,000 checks. Credits do not expire, so buying ahead of a large migration carries no penalty.
Should I split my file before uploading?
For cloud checking it is optional. Batching is mainly about keeping progress recoverable and making results easier to date and track.
Can I automate recurring bulk jobs?
Yes, through the REST API on approval. It shares the same credit balance as the dashboard.
Tell us your volume and we will size it with you
List size, countries involved, and whether it needs to run on a schedule. That is enough for us to point you at the right route.
Related pages
Number Checker
The focused active/inactive lookup for smaller jobs.
Checking Without Login
Why volume and account-based filtering conflict.
Validation API
Automate large recurring batches instead of uploading by hand.
Number Validator
Clean the list before you spend checks on it.
Check By Country
Essential when a bulk list spans many markets.
Marketing Workflow
Where bulk validation sits in a weekly campaign SOP.