How to generate QR codes in bulk
Prepare a label and a value for each code
Use two columns with the headers label,value, or Name,URL for website links. Export a comma-separated CSV or copy tab-separated cells from your spreadsheet. The tool does not import an XLSX workbook directly.
Choose URL or plain-text mode
Keep Treat each value as a web address selected for website links. Turn it off for asset references and other plain text. Inspect the preview and fix errors before exporting.
Download, reconcile and print a sample
The ZIP contains individual SVGs and an index.csv showing filenames, values and row results. The PDF puts 12 codes on each A4 page. Check the export summary, compare the index with your source and test before printing the whole set.
Use predictable spreadsheet columns
Explicit headers prevent the tool from having to infer which column contains a destination. One value per line also works, but a descriptive label makes the exported files easier to identify. Keep identifiers such as 000123 formatted as text in the spreadsheet so leading zeros are not lost before export. Semicolon-separated files should be exported as comma-separated CSV or pasted as tab-separated cells.
Example CSV structure
A header of label,value followed by a row such as Front counter,https://example.com/menu creates a labelled website QR. For inventory, a row such as Shelf A1,BIN-A1 belongs in plain-text mode. If a label contains a comma, use standard CSV quoting around that field. The preview lets you inspect how the input has been interpreted before downloading.
Know what each export contains
The ZIP is useful when a designer needs individual vector files. Filename characters are cleaned up and duplicate names are made distinct, so keep the index.csv mapping instead of guessing from filenames. The A4 PDF is a paginated contact sheet, not a template for a particular brand of adhesive label stock. Test alignment before printing onto pre-cut labels.
Handle invalid rows and larger batches
The tool processes up to the first 500 parsed rows in a batch and reports when more rows were supplied. Split larger lists deliberately and name the exported batches clearly. Invalid rows can be skipped during export; check the created and skipped totals, and use the ZIP index to identify rows requiring attention. A download finishing does not mean every input became a code.
A QR list is not an inventory or ticketing system
A batch can encode table links, equipment IDs or event URLs that you supply. It does not allocate tables, authenticate tickets, update stock or check visitors in. A plain-text asset reference only becomes useful to an inventory workflow when your own system knows what that reference means. Do not put confidential records directly into labels that anyone can scan.
Static batch codes and editable links
These exports encode the supplied values directly. They do not automatically create managed dynamic records. If a list contains links you already manage elsewhere, the printed QR relies on those links. Keep the destination list and a record of where labels were placed so future updates or replacements are manageable.
Example: labelling equipment in a small workshop
Prepare one row per item, using a short asset name and either an internal reference or an authorised maintenance-page URL. Generate a small sample first and check that the identifier survives scanning exactly, including any leading zeros. After exporting the full set, use the mapping file to match labels to equipment. The QR makes an identifier easy to read; the maintenance record still belongs in the system your team uses.
Illustrative workflow, not a customer case study.Check before you share
- The preview selects the right value column and URL/text mode.
- The created and skipped counts match your expectations.
- The ZIP index is retained with the original spreadsheet.
- Labels are tested at actual size and checked against the correct physical item.