Bulk QR generator

Prepare a small batch without losing the item-to-code mapping

Treat each line as a complete payload

This page uses one non-empty line for one QR code. A line can contain a complete URL or a short piece of text. Do not paste a spreadsheet row containing an identifier, a description, and a URL separated by tabs and expect the generator to choose only the URL. It encodes the line's text. Prepare the payload column separately and copy that column into the form.

For a simple test, use three synthetic items: a menu URL, a contact URL, and a short text label such as “Table 7”. The expected output is three images in the same order as those three non-empty lines. The first two can offer website navigation; the third can display text. Their square appearance does not imply that they all perform the same action. Verify each payload according to its intended use.

The implementation trims surrounding whitespace and skips empty lines. It does not remove duplicate non-empty entries. If the same URL appears twice, two codes can encode the same destination. That may be deliberate for two signs, but it may also reveal a preparation mistake. Decide whether duplicates are wanted before generating, rather than assuming that the tool will deduplicate the batch.

Keep the batch within the actual page limit

This version renders the first twelve non-empty entries. It is designed for a small browser batch, not a thousand-row campaign import. If you paste more than twelve entries, the extra entries do not appear in the output. Divide a longer source list into clearly labelled groups of twelve or fewer and count the generated images for each group. Do not infer complete coverage from the fact that some images appeared.

For thirteen intended signs, prepare a twelve-item batch and a separate one-item batch. Keep a written mapping from your own sign identifiers to the original payloads. The captions displayed by this page can shorten long text, so a visible caption is not always the full destination. Two different long URLs can share the same visible beginning. Verify against the source list instead of relying on those shortened captions alone.

If your task needs many items, metadata, a downloadable archive, or a machine-readable manifest, this small page does not provide that workflow. Use the output for the supported small batch and retain your mapping independently. Planning those limits before printing is more efficient than discovering missing signs after installation.

Check the destinations before checking the artwork

For URL entries, verify that every intended destination is accessible and belongs to the task. A valid-looking QR can encode an expired page, an unfinished website, a misspelled path, or a login page that the audience cannot access. The generator does not fetch the destinations to establish that they work. Rendering confirms encoding, not content availability.

For plain-text entries, inspect the exact decoded text. If an identifier needs leading zeros, keep them in the source line. A spreadsheet may have converted “007” into “7” before you copied it; the QR tool cannot recover lost formatting. Similarly, punctuation and accented characters should be part of your test rather than assumed from an English-only sample.

Review every item at its intended size

A small batch still deserves item-by-item checking. Scan each code and match its destination to its sign identifier. Testing only the first image does not establish that the rest were paired correctly. A code with a longer payload may be denser than a neighbouring code even if both output images have the same pixel dimensions.

When preparing print artwork, preserve each image's proportions and border. Avoid resizing an entire sheet in a way that gives individual codes too little physical space. Test the longest or densest item on a sample print, then check the others for correct mapping. If the images will be photographed from a distance, perform that distance test rather than only scanning while the camera is close to a monitor.

Preserve an auditable source list

Maintain a small record with an item identifier, the complete payload, the batch number, and the final artwork name. The image alone is inconvenient to audit later because somebody must scan it to discover its contents. A mapping lets a designer or colleague check a reprint without guessing which code belongs to which table, document, or display.

Changing the input list and generating again replaces the visible batch on this page. It does not remotely modify already saved images or printed sheets. Store the source list before overwriting it, and distinguish revised artwork from earlier versions. This page is not an account-based history system.

Choose batch generation for the right workload

Use this tool when several independent static codes share a straightforward preparation process. Use the dedicated Wi-Fi, contact, or UPI page when you need structured fields assembled into a specialised payload. Pasting informal notes about those fields here will encode the notes themselves. The intended receiving task should determine the payload format; batch rendering is only the final image-generation step.