Bulk QR Code Generator

Reconcile a batch with the publishing plan

Before generation, keep a simple mapping from each destination to its intended sign or artwork. After extraction, compare the manifest outcomes and successful file count with that plan. A clean filename does not establish that a code was placed in the correct design.

Test representative short and long URLs, with the chosen logo and printed size. Review every destination’s permissions separately; automatic payload comparisons do not visit all linked pages. Keep the manifest private if it contains non-public links, and do not treat a ZIP as a shared project history.

Prepare a batch without losing track of filenames

Use One URL per line for a quick list, or CSV with column headers when each output needs a meaningful name. CSV requires a single url column; an optional filename column supplies the base name. A name column is also accepted as that name field. The file-import limit is 500 KB and the batch limit is 100 data rows.

url,filename
https://example.com/menu,menu
https://example.com/contact,contact

These example addresses are placeholders. Replace them with final public pages you have checked. If a field contains a comma, enclose it in double quotes; a literal double quote inside a quoted field is written twice. Blank lines are ignored. A missing required column or malformed quote produces an input error.

Review rows before running the image checks

1. Choose the input format or import a CSV file. The imported text remains available in the input area for correction.
2. Select Preview rows. Check the URLs, output names, and validation messages. Only HTTP and HTTPS destinations are supported; encode spaces in a URL rather than entering literal spaces.
3. Choose a common pattern, colours, image size, and optional PNG, JPG, or WebP logo. Logos must be under 5 MB and use a modest fixed size.
4. Choose PNG or SVG and a ZIP filename. PNG files include the selected DPI metadata; that setting does not change the selected pixel dimensions.
5. Generate the batch, wait for completion, and download the ZIP. Read the row report before using the files.

What is—and is not—in the ZIP

Every exported image is decoded locally and compared with the exact input URL. A failed check excludes that image rather than silently packaging an unreadable code. Invalid input rows are skipped too. The ZIP includes manifest.json with each row’s URL, filename, outcome, and any error, plus the common design settings.

Output names are cleaned for normal filesystem use. Duplicate names receive a suffix, including names that differ only by letter case. A blank name receives a numbered default. This prevents one image overwriting another when the archive is extracted.

A batch is not a hosting or tracking service

The codes store direct static URLs. eToolPlus does not host their destinations, add managed redirects, or count scans. A verified image can still point to a wrong, private, or unavailable page, so check each destination before publication. Keep the ZIP report with your artwork to help identify which code belongs to each page.

The batch tool runs in your browser and provides no cross-device history or saved project account. Cancelling stops the batch without preparing a partial ZIP. Correct the input or design and run it again. Test a selection of the actual printed files on the devices and surfaces your audience will use.