Generators·4 min read

Generating QR Codes from a CSV: A Batch Workflow

Three hundred asset tags by Friday, each needing its own QR code, is the kind of task that either eats a day or takes ten minutes. Generating qr codes from a csv is the ten minute version: your spreadsheet already holds the URLs or serial numbers, so the real work is getting that column into a batch tool and a ZIP of images back out. This walkthrough covers preparing the column, the paste-driven workflow the Bulk QR Generator uses, how output files get named, and what to verify before anything reaches a label printer.

Open the tool All insights

When single QR codes stop scaling

The jobs that arrive as spreadsheets.

Batch QR work always starts life as a table. An events team holds 400 attendee check-in links. A facilities crew needs a scannable tag on every fire extinguisher, keyed to its inspection record. A restaurant group wants table-specific ordering codes across twelve locations. In each case the payloads already exist as rows, and the bottleneck is purely image production.

Producing those one by one through a single-code tool means four hundred rounds of paste, download, rename. The batch route collapses all of it into one paste and one ZIP download.

Generating QR codes from a CSV, start to finish

The Bulk QR Generator reads one value per line, and a spreadsheet column becomes exactly that the moment you copy it. Open your CSV in Excel or Google Sheets, select the column carrying the final payloads, copy, and paste into the input box. The counter beneath confirms how many values were detected, which is your first sanity check against the row count in the sheet.

Then press the button labeled Generate N QR codes as ZIP. Each line renders as a 512 pixel PNG inside your browser, gets packed by JSZip, and arrives as qr-codes.zip. Nothing uploads, which matters when the list contains internal asset URLs or serials you'd rather not hand to a third party service.

Column mapping for QR batches happens in your sheet

There's no mapping interface in the tool itself, and that's a feature: column mapping for qr batches belongs in the spreadsheet, where you already have formulas. The tool encodes exactly the text it receives, so your job is building one column that contains the finished payload for every row.

A formula does the assembly. Say column A holds tag IDs like TAG-0047 and you need each code to open an asset page. In B2 write a concatenation such as ="https://example.com/asset/"&A2, fill it down, and copy column B. Input: TAG-0047 in the sheet. Output: a QR code encoding https://example.com/asset/TAG-0047 in the ZIP. Change the URL pattern once and the whole batch remaps.

Naming bulk QR files so code 47 stays findable

A ZIP of five hundred anonymous images is its own small disaster, so the naming scheme carries the mapping. Each PNG is named with its line position, a hyphen, and the value itself with every character outside letters, digits, hyphens, and underscores converted to an underscore, capped at 40 characters.

Concretely: if line 47 reads https://example.com/asset/TAG-0047, the archive contains 47-https___example_com_asset_TAG-0047.png. The position prefix keeps files sorted in the same order as your rows, and the sanitized tail makes each one identifiable at a glance. When naming bulk qr files matters even more, like feeding a label printer's mail merge, keep the spreadsheet ordered and let the numeric prefix be the join key.

Bulk QR batch mistakes that surface after printing

The expensive errors in batch work all become visible only after the stickers exist:

Pasting the header cell along with the data, which faithfully produces a QR code encoding the word url as your first file.
Letting blank rows shift the count; empty lines are skipped, so the numeric prefixes can drift out of step with spreadsheet row numbers.
Duplicates hiding in the column, which waste labels and put identical codes on two different assets.
Encoding long URLs bloated with tracking parameters, making every code in the batch denser and harder to scan at label size.
Skipping the spot check; printing five hundred labels before scanning even one is how reprint budgets happen.

Tips for cleaner QR code batches

Deduplicate the payload column in the sheet before copying, since the tool will loyally encode the same value twice. Run one representative value through a single-code test and scan the print at real label size before committing the batch. And treat the spreadsheet as the source of truth: keep it, version it, and regenerating any subset later is a filter and a re-paste away.

Bulk QR Generator next to the single-code tools

Batch output is uniform by design: 512 pixel PNGs at the rendering library's medium redundancy setting, with no per-code styling. When one code needs custom colors, a specific pixel size, or SVG output for large format print, make that single code in the QR Code Generator, whose article also explains the four error correction levels if you want the theory. Contact card payloads deserve the vCard QR Generator so the field syntax is handled for you, and 1D labels for scanner guns come from the Barcode Generator instead.