Free bulk QR code generator: up to 100 codes in one ZIP file

When one code at a time isn’t enough

Generating one QR code takes ten seconds. Generating eighty — one per inventory reference, one per wedding table, one per product sheet — takes an afternoon. Batch generation exists for that case: you paste a list, one line per content, and walk away with a ZIP of numbered PNGs, one per line.

The method

1. Prepare your list: one line = one content. Easiest source: a spreadsheet column pasted in — each cell becomes a line.
2. Open the generator in Batch mode.
3. Paste the list into the field — the counter shows how many valid lines will be generated.
4. Run it: codes render one by one in memory, get compressed, and download as flashscanpro-batch.zip. A confirmation message states how many codes the ZIP actually contains — useful to check no line was swallowed by the 100-line cap or by empty-line filtering.

What’s inside the ZIP

Each line produces a file named qr-001.png, qr-002.png… up to qr-100.png, in the exact order of your list. The three-digit numbering keeps alphabetical sorting aligned with list order — qr-010 correctly sorts after qr-009, not before qr-002. To map files back to lines, keep the source list: qr-023.png = the 23rd non-empty line.

Two rules to know before pasting

• https:// is prepended automatically to lines without a scheme: example.com/product-12 becomes https://example.com/product-12. If your lines are raw text (serial numbers, internal references) rather than URLs, they’ll be encoded as links — prefer complete content, or accept that the code decodes to https://….
• Empty lines and whitespace are skipped: the batch caps at 100 valid lines; anything beyond is ignored. Split larger volumes into multiple batches.

Organizing the ZIP after download

Once flashscanpro-batch.zip is unzipped, three habits prevent mix-ups:

• Keep the source list in the same folder: the file-to-content mapping rests on line position. If you reorder the list later, regenerate the batch rather than renaming by hand.
• Rename as needed: qr-001.png is clear in production, but for delivery to a client or printer, renaming to table-12.png or ref-ABC-042.png avoids placement errors. Do it after unzipping, never by editing the list backwards.
• For more than 100 codes: split the list into successive batches and store each ZIP in its own folder — numbering restarts at qr-001 every batch.

What the batch codes look like

All codes in a batch share the generator’s settings at render time: if you adjusted colors, error correction, or loaded a logo, those choices apply to the whole series — a branded batch is prepared like a single code. Content alone varies line by line: that’s the only thing distinguishing qr-001.png from qr-023.png.

Why the 100 limit?

The limit isn’t commercial — it’s technical: everything happens in the browser. Each QR code renders to a PNG in memory, then the whole set is compressed by the ZIP engine before download — no server does the work for you. A hundred simultaneous PNGs stay reasonable on a modest phone; five hundred might crash the tab. The limit protects the outcome: two batches that complete beat one that fails silently.

The symmetric benefit: your data goes nowhere. A list of internal references, identifiers, or private URLs is processed locally, and each generated code lands in your local history (stored on-device, 500 entries max — see scanning without uploads).

A concrete workflow: spreadsheet to label sheet

The typical end-to-end run looks like this. Your inventory lives in a spreadsheet — column A holds the identifier or URL per item. Export or copy that column, paste it into the batch field, generate, and unzip. You now have one PNG per row. Drop those PNGs into a label template (most office suites and label software import image lists), align them with the references, and print a test sheet on plain paper. Scan three or four codes with a phone — including the first and the last — before committing the adhesive stock. Total time for 60 labels: about fifteen minutes, versus an afternoon one code at a time.

The use cases that justify batch

• Inventory: one code per shelf, item, or asset — paste the identifier column, print the PNGs as label sheets.
• Events: one code per table, badge, or ticket with a personal URL.
• Shelf labeling: one code per product sheet pointing to its online page.
• Documentation and support: a series of codes to each product’s help page.

Before the print run, verify two or three ZIP codes with the scanner and review the print size rules — a batch printed too small is a hundred mistakes at once.