LOCAL CSV BATCH

Generate a static QR batch

One CSV in, verified PNG, SVG and PDF files out. The file never leaves this browser: there is no upload, no server job and no stored copy.

  1. FILE
  2. COLUMNS
  3. ROWS
  4. VERIFY
  5. PACKAGE

CHOOSE A FILE

Choose a CSV in this browser

Up to 100 rows, up to 256 KB.

Keep this page open while processing. Split larger files into batches and edit failed rows before retrying.

No file selected
Printer resolution

Applied to every row. Changing it clears every result, because it changes every file.

Printed size

The printed edge length each row is checked against.

FILE REQUIREMENTS

File errors and row errors stay separate

  • Required columns: name, target_url. Optional: number, utm_source, utm_medium, utm_campaign, utm_term, utm_content.
  • Leave a tracking cell empty and nothing is added for that row; a file with none of the five columns works exactly as before. Any other utm_… column is refused, not ignored. The final address goes through the same HTTPS, 2048-byte and QR-capacity checks after the parameters are added.
  • Every address goes through the same HTTPS, credential, control-character and 2048-byte contract as the single-code tool.
  • There is no server queue, no upload, no stored file and no emailed result. Close the tab and the batch is gone.

CHECK EVERY ROW

Valid rows keep moving. Failures stay on their line.

0 of 0 rows processed

0 passed · 0 failed · 0 not processed

No file has been checked. No example rows are inserted.

A row that fails does not stop the rows after it. Edit a row to correct it — that clears its result, and the next run redoes only the rows that have none.

PACKAGE PASSED FILES

Only verified files enter the ZIP

The archive holds one file per verified format under codes/, plus success.csv and errors.csv. A row that failed, or that is still waiting on a warning, appears in the error report instead.

Batch status

Waiting for a CSV

Nothing is parsed, generated or uploaded until you choose one.