How the list should look
One entry per line. The simplest version is just destinations:
https://example.com/product/1
https://example.com/product/2
https://example.com/product/3Add a comma and a name to control what each file is called:
https://example.com/product/1, blue-mug
https://example.com/product/2, red-mug
https://example.com/product/3, green-mugNames are cleaned up so they work on every operating system, and duplicates get a numeric suffix rather than overwriting each other. A CSV export with a header row works too — the header is detected and skipped.
Where bulk codes get used
- Product labels — a different code per SKU, each pointing at that product's page.
- Event badges and tickets — one per attendee, generated from a registration export.
- Asset tags — equipment, rooms, machines, each linking to its own record.
- Table numbers — the same ordering page with a different table parameter, so orders arrive tagged.
- Print runs — a code per variant, region or language edition.
Why this is free here
Most tools put bulk generation behind a paid plan, and there is a real reason: they generate codes on their servers and store them against your account. That costs money, and the cost grows with how much you use it — so it has to be metered.
FigQR generates in your browser. A thousand codes uses your processor and our infrastructure not at all. There is nothing to meter, so there is no limit and no plan.
It also means your list never leaves your device — which matters more than it sounds if the file is a customer export, a list of unreleased product URLs, or anything else you would rather not upload to a company you had not heard of an hour ago.
A note on very large batches
Because the work happens locally, a few thousand codes will keep the tab busy for a while and the ZIP will be large. If you need tens of thousands, split the list into batches of around five hundred — you will get them faster and the browser stays responsive.