Bulk QR Code Generator — CSV Import for 1,000 Codes at Once

Up to 1,000 codes per CSV upload via the dashboard. The API batch endpoint accepts 100 codes per request — chain multiple batches for larger workflows. No per-code fees on any plan; you pay the monthly subscription, codes are unlimited.

Four columns in this order: name, content_type, content, target_url (optional). The first row is the header. Each subsequent row creates one QR code. Save as plain CSV (UTF-8). Example: Store NYC,url,https://acme.com/nyc,https://acme.com/r/nyc creates a dynamic code named "Store NYC" that redirects to acme.com/nyc via the EZQR short link.

Bulk CSV import and the API batch endpoint are both on the Max plan ($20/mo). The free, Lite ($5/mo), and Pro ($10/mo) tiers create codes individually in the dashboard form. If you regularly need 50+ codes per batch, the Max plan pays for itself in the first import.

Yes — include a target_url value in the CSV row and the code is created as dynamic with a repointable redirect. Rows without a target_url create static codes. Your plan's dynamic-code limit still applies; if you're on Max, the dynamic limit is 5,000 active codes, well above any single bulk import.

EZQR processes valid rows and reports failed rows in the import summary with the specific error (invalid URL, missing required vCard field, Wi-Fi password too short, etc.). Failed rows do not consume your dynamic-code limit. Fix the offending rows in your CSV, re-upload the failed subset, and the rest of the batch is untouched.

Static codes (rows without `target_url`) keep working forever — the payload is encoded directly into the pattern, no server needed. Dynamic codes (rows with `target_url`) route through EZQR's redirect and require an active subscription to keep resolving. If your workflow is print-once-keep-forever (asset tags, packaging, business cards), prefer static. If you need to repoint after printing, dynamic.

Up to 1,000 rows per CSV on the Max plan. Each row mints its own code with its own destination and its own scan tracking. Split larger sets across uploads. There is no cap on how many batches you run.

A destination column at minimum, plus a name column so you can tell the codes apart afterwards. Anything else you add rides along as metadata. Get the naming right on upload, because renaming 1,000 codes by hand afterwards is the mistake everyone makes once.

Yes, and that is the normal case. Asset tags, table numbers, serial numbers and per-store landing pages all work this way. One row, one destination, one code. Scan data then separates by row, so you learn which asset or table actually gets used.

Yes. Every code from a bulk import is a dynamic code, so you retarget any of them later without reprinting. That matters at volume more than anywhere else. Reprinting 1,000 asset labels because a URL changed is a genuinely expensive afternoon.

SVG or PDF for a printer, PNG only for screens. Vector files hold their edges at any size, which is what a label press needs. Send a printer a 300 px PNG scaled to a 5 cm label and the modules blur together. Your run is then wasted.

Yes. The batch stays in your dashboard with every code and its destination, so you re-export at a different size or format whenever the print spec changes. Keep the original CSV too. It is the fastest way to regenerate a set that has drifted out of sync.