How bulk QR generation works
- Prepare a CSV with two columns:
name(used as the filename) anddata(the URL or text encoded into the QR). - Drop the CSV onto the upload area. We show the first five rows so you can verify the parsing.
- Pick the colors and dot style — every code in the batch shares the same look.
- Click Generate ZIP. A progress bar shows you where the run is. Generating 1,000 codes takes ~20–30 seconds in a modern browser.
- Your browser downloads a ZIP containing one PNG per row.
CSV format
Header row required. Example:
name,data table-1,https://menu.example.com/?t=1 table-2,https://menu.example.com/?t=2 table-3,https://menu.example.com/?t=3
If your CSV uses different column names we fall back to the first column for filename and the second column for content.
Limits and performance
We cap each batch at 1,000 rows to keep the browser responsive. Past about 500 rows you may see the browser tab slow down — we recommend splitting very large jobs into several CSVs. All processing happens client-side, so closing the tab cancels the generation.
Use cases
- Restaurant table menus with one unique URL per table
- Event tickets with one-time codes
- Asset tags for inventory tracking
- Per-employee onboarding links
- Wedding favors with personalized URLs
FAQ
What if my CSV is bigger than 1,000 rows? Only the first 1,000 are processed. Split the file and run multiple batches.
Are the codes uploaded? No. CSV parsing, QR rendering, and ZIP packaging all run in your browser.
Can I get SVG output? The default batch format is PNG; SVG batch is on the roadmap.
The progress bar froze. A very large batch may make the tab unresponsive briefly. Wait it out — the browser is single-threaded and rendering is CPU-intensive.