How to generate up to 1,000,000 QR codes in a single production job
At one million QR codes, generation becomes a pipeline problem involving CPU, memory, archive size, naming and network transfer.
For serialization programs, large packaging campaigns, industrial assets, unique coupons and data volumes beyond normal spreadsheet workflows.
- Automatic series without a million browser rows
- Parallel Python engine
- Streamed ZIP64
- Backend job progress
- SVG/PNG output based on capacity
A clear path from source data to QR assets
1. Avoid giant spreadsheets
If data follows a rule, generate from a template rather than a million XLSX rows.
2. Size the server
Throughput depends on vCPU, output format, compression and payload length.
3. Stream the archive
The ZIP is created progressively instead of being held entirely in browser memory.
4. Validate the batch
Check file counts, naming and representative samples.
One-million series
A simple example showing how source data stays linked to the generated QR asset.
| Template | First | Last |
|---|---|---|
https://example.com/item/{id_padded} | .../00000001 | .../01000000 |
asset_{id_padded} | asset_00000001.svg | asset_01000000.svg |
What really changes at one million files
CPU is only one limit; archive size and network throughput can dominate total duration.
MassQR limits concurrent massive jobs so one customer cannot consume every server core.
For repeatable system-to-system flows, REST API or deterministic templates can simplify operations.
Frequently asked questions
Can one million QR codes finish in a few seconds?
Streaming can start quickly, but total time depends on CPU, output format, archive size and network bandwidth.
Should I use Excel for one million rows?
Usually no. Automatic series, CSV pipelines or API integrations are more appropriate.