Bulk CPF Generator

Multiple CPFs for enterprise load testing and BI mocks

Some toolkits distinguish a batch (lote) generator — which dumps X CPFs into a single CSV download — from a multiple (múltiplos) generator — which streams them sequentially, often consumed by an external script via copy-paste or HTTP. In practice the terms are interchangeable and this page focuses on enterprise angles that the standard batch tool does not cover: load-testing backends, populating CRM and BI mocks, and driving sandbox integrations against the Receita Federal.

Load-testing a validator endpoint

A modern JavaScript runtime mints roughly 1 million CPFs per second — the modulo-11 check is O(1) and Math.random is non-blocking, so the generator is never the bottleneck. The real load goes to your validator. Standard playbook: paste 10,000 numbers into a k6, Locust or JMeter data source, then ramp users from 1 to 500 against the POST /validate-cpf endpoint. Watch p99 latency and error rate — a well-written validator stays under 5 ms p99 at 5,000 req/s on a single Node instance.

Enterprise CRM and BI scenarios

• SAP / TOTVS mock CRM — populate the customer master (KNA1, SA1) with 10,000+ synthetic registers to rehearse migrations and acceptance tests without exporting production PII.
• RFB sandbox integrations — exercise the homologation channels of Receita Federal services with fictional inputs before signing the production certificate.
• Power BI / Tableau QA — fill a data warehouse with 100k fake clients so dashboards render with realistic cardinalities without violating the LGPD.
• Postman / Insomnia collection runners — feed a data.csv with one CPF per row into the collection runner; useful for regression tests that hit dozens of endpoints in sequence.

Output formats: paste, CSV, JSON, SQL

// Paste-block (one per line)
123.456.789-09
987.654.321-00

// CSV with header
cpf
12345678909
98765432100

// JSON array
["12345678909","98765432100"]

// SQL INSERT
INSERT INTO customers(cpf) VALUES ('12345678909'),('98765432100');

Anti-patterns to avoid

Do not use a generated CPF on a "card-payment" mock that routes through a real PSP — gateways like Pagar.me, Cielo and Stone consult the Receita base and silently reject unregistered numbers, contaminating your test metrics with false-negative declines. Use the PSP's own sandbox CPFs, listed in their developer docs. Likewise, a uniformly random generator covers all ten fiscal regions evenly — for realistic Brazilian demographics, weight SP/RJ/MG to about 50% of the dataset and treat region 4 (north) as a minority.

LGPD pitfall: accidental real numbers

There are ~220 million registered CPFs out of 10¹¹ possible eleven-digit combinations, so the probability that a random output coincidentally matches a real citizen is roughly 0.22%. For a batch of 10,000 numbers, expect around 22 collisions with real CPFs. These are still unusable in any binding transaction (you do not own those identities), but if the generator is feeding a public demo, mask the middle four digits or reserve the special pattern 000.000.000-00 family which every production validator rejects by default.

FAQ

Is this faster than faker.js? Yes — no Node dependency, no npm install, no bundle weight. The browser runs the modulo-11 algorithm directly and streams results into the textbox as fast as the DOM can paint them.

Can I export to TSV instead of CSV? Copy the output and replace the line break with a tab in your editor — the underlying format is plain text, so any delimiter works.

Does it integrate with Postman collection runners? Yes — save the output as data.csv with a single cpf header column and feed it into the collection runner's data file field.

What is the difference between "lote" and "múltiplos" generators? In most toolkits they are synonyms. When a distinction exists, lote implies a downloadable artefact (CSV file), while múltiplos implies inline output suitable for paste, API streaming or collection-runner consumption.