Bulk QR Generator

The CSV workflow, step by step

Step 1 — build the spreadsheet. Put a short label in the first column (it becomes the file name) and the content to encode in the second, then export as CSV from Excel, Numbers or Google Sheets. Keep labels free of slashes and other characters that file systems dislike.

Step 2 — upload the file above and pick the content type so the generator interprets the values correctly, whether they are URLs, phone numbers, WhatsApp links or WiFi credentials.

Step 3 — choose PNG, SVG or PDF, then start the run. A progress bar shows how far along the batch is, and a cancel button stops it cleanly if you spot a mistake in the data.

Step 4 — download the ZIP, or grab individual codes from the results list. Spot-check two or three files with the QR code decoder before handing the set to a printer or uploading it to a catalogue.

Where bulk generation saves real time

Product catalogues are the clearest case: one code per SKU pointing at its product page, generated in a single pass instead of one at a time, then dropped into label artwork by file name.

Events use it for per-ticket or per-session codes — a code for each workshop's feedback form, or a code per exhibitor stand pointing at their profile.

Property and rental portfolios generate a code per listing for signage, and asset registers generate a code per item for maintenance records or serial-number labels.

Multi-location businesses build one code per branch — separate review links, WiFi credentials or contact numbers — with file names that match each site, so the right code reaches the right store.

Working with large batches without locking up the page

Generation runs on your device, so the practical limit is memory rather than a server quota. The tool renders codes one at a time and yields back to the browser between them, which keeps the interface responsive and lets you cancel mid-run without leaving a half-written download.

For very large sets, split the CSV into chunks of a few hundred rows. Smaller ZIPs are quicker to download, easier to check, and far less painful to regenerate if you spot a data error after the fact.

Before a print order, decode a sample from the middle of the batch as well as the first row — errors in spreadsheets tend to appear where a formula was dragged, not at the top.

File naming, duplicates and matching codes back to data

The label column is the only thing connecting a generated file to the row it came from, so treat it as an identifier rather than a description. A SKU, a room number, a ticket reference or a branch code all merge cleanly into label artwork; 'Front window poster (new)' does not.

Strip characters file systems dislike — slashes, colons, question marks — and keep names short and consistent in case. If two rows share a label, the second file is saved as name-2 rather than overwriting the first, which protects the batch but usually means the spreadsheet has a duplicate worth fixing before the run.

Sort the CSV by label before generating. A ZIP whose file order matches the spreadsheet order makes a variable-data print merge trivial and makes a missing row obvious at a glance.

Catching data errors before they reach print

Empty rows are skipped and unencodable values are reported rather than dropped in silence, so the count in the results list should match the number of data rows in your CSV. A mismatch is the first sign that something in the file needs attention.

The most common cause of a broken batch is not the generator but the data: a URL missing its https prefix, a phone number that lost its leading zero to spreadsheet formatting, or a trailing space that turns two identical values into two different ones. Format the column as text before pasting values in.

When a handful of rows fail, fix those rows in a small separate CSV and run them alone. Regenerating a whole catalogue to correct three labels wastes time and risks introducing a new inconsistency in styling.

Testing a batch properly

Decode a sample from the start, the middle and the end of the ZIP with the QR code decoder. Errors introduced by a dragged formula appear partway down a sheet, so a first-row check is the least useful test you can run.

Print one physical proof at the final size on the actual material — label stock, vinyl, thermal paper — and scan it on both an iOS and an Android phone. Codes that pass on screen still fail on gloss laminate or a curved bottle.

Keep the approved CSV alongside the ZIP. Reprints months later should regenerate from the same source data rather than from a fresh spreadsheet that may have drifted.