Bulk QR Code Generator From a CSV File

The CSV format the generator expects

Two columns are all you need: the content to encode and the filename to use. Put a header row on top, keep one row per code, and avoid merged cells or blank separator rows — spreadsheets tolerate those visually, but a CSV export turns them into empty rows that produce nothing useful.

Save as CSV UTF-8 rather than plain CSV where your spreadsheet offers the choice. That single setting prevents the most common corruption, where accented characters and symbols in filenames arrive as replacement characters on the other side.

Preparing the file so the run succeeds first time

Trim whitespace from both columns; a trailing space on a URL is invisible in a spreadsheet and can produce a link that 404s. Watch for curly quotes and en dashes if any of the text was pasted from a word processor, since those are different characters from the straight quotes and hyphens a URL expects.

If a value itself contains a comma, it must be wrapped in straight double quotes — every spreadsheet does this automatically on export, which is another reason to export rather than hand-edit a CSV in a text editor.

Running the import step by step

Open the bulk QR generator and choose your CSV. The tool parses it, shows how many rows it found, and reports anything it had to skip — that count is your first sanity check, because a number that does not match your spreadsheet means the file has empty or malformed rows.

Set the size and styling for the batch, start the run, and watch the previews appear. Scan a few, then download the ZIP. If something is wrong, fix the CSV and re-run; nothing is stored between runs.

Why rows fail and how to fix them

The three recurring causes are empty rows at the bottom of the file, a delimiter mismatch in regions where spreadsheets export with semicolons instead of commas, and encoding problems from a non-UTF-8 export. All three are solved in the spreadsheet rather than the generator.

Duplicate names are handled rather than rejected: a repeated filename gets a numeric suffix so both codes survive. It is still worth deduplicating the source, because two rows sharing a name usually means the export contained the same record twice.

Typical CSV workflows

A conference exports its session list, adds a feedback URL column with a session ID in the query string, and produces one code per room sign. A warehouse exports its bin list and generates a code per location that opens the stock record. A restaurant group exports its venue list and produces a menu code per site, each named after the branch.

In all three the CSV is a byproduct of a system that already exists, which is what makes this route fast — nobody types the list twice.

Your spreadsheet stays on your machine

CSV exports often carry more than the two columns you need — customer references, internal IDs, prices left in adjacent columns. Because parsing and rendering happen in the browser, the file is never transmitted, so an over-inclusive export is not a disclosure risk.