Bulk QR Code Generator

From spreadsheet to ZIP file

1. 1

   Prepare two columns

   Column A holds what each code should contain: a link, text or an email address. Optional column B holds the file name, such as table-12 or SKU-4471. Other columns are ignored.

2. 2

   Paste or upload

   Select the cells in Excel or Google Sheets, copy them and paste into the list box. Or upload a .csv file; comma and semicolon separators are both detected.

3. 3

   Check the header and preview

   A header row such as url or name is detected and skipped; a switch overrides that. The preview shows the first rows and any that will be left out.

4. 4

   Design once and download

   Set colors and an optional logo in the same design panel as the main generator, choose PNG or SVG, and download. Rows that fail are listed with the reason.

QR code generator from Excel, Google Sheets or CSV

Spreadsheet add-ins and formulas that make QR codes often send each value to an outside web service. Copying the cells here keeps the list on your device.

• Pasted from a spreadsheet

  Columns are split on tabs, which is what Excel and Google Sheets copy. A comma inside a cell, like Table 4, by the window, stays one value.

• Uploaded CSV

  The separator is detected from the first line, comma or semicolon. Excel in many European languages saves CSV with semicolons, and that works unchanged.

• What each row becomes

  A bare domain gets https:// added. Anything else, such as mailto:, tel:, a WIFI: string or plain text, is encoded exactly as written.

File names, numbering and duplicates

A name in column B becomes the file name, cleaned of characters Windows or macOS would reject. Without one, files are numbered in list order plus a readable part of the content, so the folder sorts like your sheet. Duplicate names get -2, -3 and so on instead of overwriting each other.

Batch QR code generator limits and rows that are left out

Each batch takes up to 1,000 rows, because every code is drawn and checked one at a time on your device; split longer lists across batches, as many as you like. Rows that are too long for a code, look like a script rather than a link, or fail the read-back check are left out and listed with the reason. The rest of the batch still downloads.

What goes into each code

Each code contains the value from its row, changed only where it helps: a bare domain gets https:// so it opens. The design is applied identically to every code. Two pasted columns look like this, separated by a tab.

https://northside-bistro.com/t/1	table-01
https://northside-bistro.com/t/2	table-02

Printing codes made in bulk

Bulk codes usually end up on labels, badges and table cards, so settle the size before printing hundreds. A 20 to 25 mm code suits a product label read at arm's length; table cards read from a seat need 30 to 40 mm. Choose SVG when the files go into label or layout software for a mail merge, so every code stays sharp at the template's size.

Mistakes that ruin a bulk run

• Printing the lot without a test sheet

  Every file is checked before download, but print one sheet and scan a few codes from it. Printer scaling and label bleed are beyond a file check.

• Long links with unique tracking parameters

  Campaign parameters on every row make dense codes. Shorten the links or use dynamic codes.

• Leaving column B empty

  Numbered files are fine for a test. For 300 table cards or labels, put the table number or SKU in column B so the printer can tell them apart.

Bulk jobs people run here

• A restaurant makes 40 table codes, each with the table number in the link and in the file name.
• An IT team generates asset tags from an inventory sheet, with the asset ID as both content and file name.
• A conference creates one code per attendee for their personal schedule page.