QR Batch Generator

Batch Scan Readiness

ECC {{ selectedEcc }} {{ selectedFormatLabel }} ZIP {{ totalBytesDisplay }} bytes {{ batchStatusLabel }} {{ warningCount }} warning(s)

Payload rows:

Generate one QR image per row. CSV/TXT loading stays local in the browser.

{{ note }}

Error correction:

Choose the scan resilience shared by every generated QR symbol.

ZIP image format:

Sets the image extension used for every QR file in the ZIP archive.

Image size:

Output width and height for each square QR image.

Filename prefix:

Used before row labels when building the ZIP archive and manifest.

Quiet zone:

Blank border around each symbol, measured in QR modules.

modules

Foreground color:

Module color shared by all generated symbols.

Background color:

Background color used for PNG, JPEG, WebP, and preview rendering.

Dot style:

Visual module style applied consistently across the batch.

Eye style:

Corner finder pattern style for all generated symbols.

Preview limit:

Maximum number of QR previews rendered in the gallery tab.

codes

Skip duplicate payloads:

Useful when a spreadsheet accidentally repeats the same destination.

Showing {{ previewRows.length }} of {{ exportableRows.length }} valid QR code(s). Increase the preview limit in Advanced to inspect more.

#	Filename	Type	Bytes	Version	Capacity	Readiness	Copy
{{ row.indexDisplay }}	{{ row.filename }}	{{ row.typeLabel }}	{{ row.bytes }}	V{{ row.version }}	{{ row.utilizationDisplay }}	{{ row.status }}

Row	Status	Main issue	Next action	Copy
{{ row.label }}	{{ row.status }}	{{ row.issue }}	{{ row.action }}

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

When QR work moves from one code to a list, the main risk shifts from drawing the symbol to keeping the batch traceable. A front-desk sign, lobby Wi-Fi card, support email action, asset label, and menu link can all look like similar squares after export. The row name, filename, payload, and readiness note are what keep each image tied to the right destination.

Every QR symbol stores a payload, which is the exact text returned by a scanner. That payload may be a web address, Wi-Fi configuration string, mail or phone action, vCard, calendar record, map coordinate, data URI, or plain identifier. The scanner does not know whether the row came from a spreadsheet, a label run, or a campaign plan. It reads the text and hands it to the phone, app, or browser.

Common QR batch preparation concerns and safeguards
Batch concern	Why it matters	Practical safeguard
Payload length	Longer text needs more QR modules, which makes each module smaller when image size stays fixed.	Use short destination URLs or identifiers for small labels and crowded print layouts.
Error correction	Higher recovery levels tolerate more dirt or damage, but they reduce payload room for the same version.	Use stronger correction for codes that may be handled, scratched, or partly obscured.
Quiet zone and contrast	Scanners need a clear blank border and strong dark-light edges to find the square reliably.	Keep a four-module quiet zone and test any custom colors on the final surface.
Names and duplicates	A repeated payload or vague filename can hide a spreadsheet mistake until labels are printed.	Keep row names, generated filenames, payload types, and duplicate notes in the review record.

Several QR terms decide whether a whole set is ready to hand off. A module is one dark or light square in the grid. A version is the symbol size, from Version 1 at 21 by 21 modules to Version 40 at 177 by 177 modules. The quiet zone is the blank margin around the grid. Error correction adds recovery codewords so a symbol can still scan after some damage, but it is not a substitute for readable size, clean contrast, and a clear border.

Diagram of source rows becoming a QR image set with shared settings and then ZIP images, manifest rows, and a readiness audit.

Tradeoffs compound across a batch. Raising error correction from M to H can help a symbol survive scuffs, but a long payload may jump to a denser version. Shrinking image size keeps a label compact, but smaller modules leave less room for printer blur, screen glare, or a shaky phone camera. Rounded dots and custom eye shapes should be added only after a plain square version scans cleanly.

A QR code carries data, not trust. It can open a link, prepare an email, join a network, or display an identifier, but it cannot prove that the destination is safe, current, or intended for the person scanning it. Large batches should end with row review and scan tests on the same material, size, and lighting where the codes will be used.

How to Use This Tool:

Use the generator when one named row set needs QR images plus a review record.

Paste one payload per line into Payload rows, paste name,payload rows for predictable filenames, or use Browse CSV/TXT. If the file warning says the source is larger than 512 KB or cannot be read, split the source or export a cleaner CSV/TXT file.
Check the yellow source notes before changing design settings. CSV header detected, blank row(s) ignored, and duplicate payload row(s) skipped explain how the input was parsed.
Choose Error correction, ZIP image format, Image size, and Filename prefix. The summary updates with the selected ECC level, export format, total bytes, exportable row count, and batch status.
Open Advanced when the batch needs stricter print settings or a branded look. Keep Quiet zone at 4 modules unless you have a tested reason to reduce it, and use the foreground/background color fields to restore high contrast before relying on decorative dot or eye styles.
Use Preview limit only to control how many symbols render in QR Image Set. The ZIP can still include every valid row up to the 1,000-row browser safety limit.
Open Payload Ledger to review filenames, type labels, byte counts, estimated versions, capacity use, readiness scores, and row status. Open Readiness Audit for the main issue and next action when a row shows a warning.
Check Batch Readiness Map when a large set needs a quick triage view. The chart surfaces the weaker exportable rows first, so dense payloads or lower scores are easier to inspect before handoff.
Download the ZIP only after blocked rows and high-priority warnings are resolved. Use the CSV, DOCX, JSON, and chart exports when another person needs to review the batch record before printing or distribution.

Turn on Skip duplicate payloads when repeated destinations are accidental. Leave it off when different labels intentionally point to the same place and the manifest should keep each row.

Interpreting Results:

The large summary number counts Robust and Balanced rows against all parsed rows. The batch status is the first release cue: Ready means no current warnings, Needs review means at least one warning is present, and Blocked rows means one or more rows cannot be treated as production-ready QR symbols.

Readiness score is a scan-preparation score, not a guarantee. It rewards capacity headroom, contrast, quiet-zone spacing, and stronger error correction. A high score still needs a real scan test on the exported image size and final surface, while a lower score points to the likely repair: shorten the payload, restore contrast, increase quiet-zone spacing, or adjust error correction.

How to interpret QR batch result cues
Output cue	Boundary	Best follow-up
Robust	`Readiness score >= 86` and no row warnings.	Scan-test representative samples before production use.
Balanced	`Readiness score >= 72`, with warnings still possible.	Review Main issue before printing or sharing.
Review	`Readiness score >= 50`, but scan margin is weak.	Use Readiness Audit to find the setting or payload that reduced the score.
Blocked	Empty payload, byte capacity overflow, or `Readiness score < 50`.	Correct the row before using the batch for production handoff.

Trust the row tables more than the gallery thumbnail. The gallery confirms that a symbol rendered, while Payload Ledger and Readiness Audit show whether the filename, payload, byte count, estimated version, warning, and next action still make sense.

Technical Details:

QR Code Model 2 symbols are square grids with versions 1 through 40. Version 1 contains 21 modules per side, and each higher version adds 4 modules per side, so Version 40 reaches 177 by 177 modules. More data, stronger error correction, or less efficient content can require a higher version. If the exported image size stays fixed, a higher version makes each module smaller and leaves less physical scan margin.

Error correction levels L, M, Q, and H add Reed-Solomon recovery codewords. Higher levels can restore more damaged codewords, but they reduce the maximum payload capacity for the same QR version. Mixed business batches are safest to estimate in UTF-8 byte mode because URLs, Wi-Fi strings, vCards, calendar records, map coordinates, and ordinary identifiers can all appear in the same source list.

Transformation Core:

QR batch row parsing and output rules
Input pattern	How it is interpreted	Output effect
One payload per line	The whole line becomes the payload, with an automatic row name.	The generated filename uses the selected prefix plus the row number.
`name,payload`	The first cell becomes the source name when it does not look like a payload.	The source name is sanitized into the filename and kept in the manifest row.
CSV or tabular text with headers	Header labels such as `payload`, `url`, `content`, `data`, `qr`, or `value` are mapped automatically.	A source note reports header detection, then each data row becomes a QR row.
Duplicate payloads	Duplicates are warned by default or skipped when duplicate skipping is enabled.	The batch either keeps each label or reports the number of skipped duplicate payload rows.
Very large sources	CSV/TXT loading is limited to 512 KB, and ZIP export uses the first 1,000 valid rows.	Large jobs should be split into smaller browser-sized batches.

Formula Core:

The row calculations use the estimated QR version, selected image size, quiet-zone setting, contrast ratio, and selected error correction level. Capacity use is checked before status labels are assigned.

\begin{array}{lcl} modules per side & = & 17 + 4 V \\ U & = & UTF-8 payload bytes / byte capacity for V and ECC \\ quiet-zone pixels & = & round (image size / modules per side x quiet-zone modules) \\ R & = & round (0.38 C + 0.24 K + 0.20 Z + 0.18 E) \end{array}

Here V is the estimated QR version, U is capacity use, R is readiness score, C is the capacity headroom score, K is the contrast score, Z is the quiet-zone score, and E is the error-correction score. For example, a 28-byte URL at ECC Q fits Version 3 because the Version 3 byte capacity is 32 bytes. The module count is 17 + 4 x 3 = 29; with a 360 px image and 4 quiet-zone modules, the computed margin is about 50 px.

Byte-mode capacity limits used by the QR batch generator
Error correction	Maximum byte-mode payload	Practical reading
`L`	2,953 bytes	Most payload room, least recovery headroom.
`M`	2,331 bytes	Common general-purpose correction level.
`Q`	1,663 bytes	Balanced for many printed batches.
`H`	1,273 bytes	Most recovery headroom, smallest payload room.

Readiness score inputs and warning rules
Signal	Rule used	Why it matters
`C` capacity	Full score through 70% capacity use, gradual reduction from 70% to 90%, and a steeper reduction above 90%.	Dense symbols have smaller modules and less tolerance for print blur or camera distance.
`K` contrast	Uses relative luminance contrast. A warning appears below `4.5:1`, and `7:1` receives full contrast score.	Dark-light separation is more important than hue for scanner edge detection.
`Z` quiet zone	Reaches full score at 4 modules. Values below 4 modules add a warning.	The scanner needs clear space around the grid to find the code boundary.
`E` error correction	Maps `L`, `M`, `Q`, and `H` to increasing resilience scores.	More recovery data can survive more damage but lowers capacity for the same version.
Payload checks	Empty payloads, capacity overflow, duplicate payloads, very dense rows above 92%, and `www.` URLs without a protocol can appear in the audit.	These row checks catch spreadsheet mistakes and scan-risk choices that are easy to miss in a gallery.

Readiness status boundaries
Status	Boundary	Meaning
Robust	`R >= 86` and no row warnings	Strong measured scan margin, still requiring a real scan test.
Balanced	`R >= 72`	Likely usable, but any warning should be reviewed before handoff.
Review	`R >= 50`	One or more choices are reducing scan margin enough to slow release.
Blocked	Empty payload, capacity overflow, or `R < 50`	The row should be corrected before the QR image is used in production.

Privacy Notes:

Pasted rows and selected CSV/TXT files are parsed in the browser, and the QR archive is assembled during the browser session. Preview, ZIP creation, and chart export depend on external QR, ZIP, and chart resources loading successfully.

Do not put secrets in public QR payloads unless everyone who can scan the code is allowed to see the secret.
Wi-Fi QR strings can expose network names and passwords to anyone with camera access to the code.
Short links and plain identifiers can become stale or ambiguous if the destination system changes after printing.

Advanced Tips:

Use name,payload rows when filenames must remain predictable. The manifest keeps the source name, payload type, byte count, readiness score, and payload text together.
Turn on Skip duplicate payloads only when repeated destinations are accidental. Leave it off when two labels intentionally point to the same page or action.
Keep Preview limit low for large batches while reviewing totals, then raise it only when you need to inspect more symbols in QR Image Set.
Use Batch Readiness Map to find the weakest rows first. Dense payloads, low contrast, and quiet-zone warnings are easier to fix before the ZIP is downloaded.
Choose SVG when a print or design workflow needs editable vector artwork; use PNG when the handoff should be simple and consistent across ordinary office tools.
Split very large sources before import. Selected CSV/TXT files are capped at 512 KB, and ZIP export is limited to the first 1,000 valid QR rows for browser safety.

Worked Examples:

Front-desk starter set

Paste rows for front-desk, wifi-lobby, and asset-042 with the default ECC Q, PNG, 360 px, and 4 modules. Payload Ledger labels the rows as URL, Wi-Fi, and Text, builds filenames from the current Filename prefix, and shows byte counts for each payload. A 28-byte URL estimates Version 3 at ECC Q and should appear as Robust with the default colors.

Repeated menu destination

Rows named poster-a and poster-b that both contain the same menu HTTPS URL are kept when Skip duplicate payloads is off. The second row appears in Readiness Audit with Main issue set to Duplicate payload appears in the batch. If the repetition is accidental, turn on Skip duplicate payloads; the source note then reports that one duplicate payload row was skipped.

Protocol warning on a URL row

A row such as menu,www.example.com/menu is detected as a URL, but Readiness Audit warns that the URL starts with www and has no web protocol. The row may still be exportable. The safer correction is to change the payload to a full HTTPS URL before downloading the ZIP.

High-correction capacity overflow

A 1,300-byte plain-text inventory note under ECC H is above the 1,273-byte byte-mode capacity used for the highest QR version. Payload Ledger shows Version 40 and capacity pressure, while Readiness Audit returns Blocked. Shorten the text, lower error correction only if the use case allows it, or replace the QR payload with a shorter link to the full record.

FAQ:

What row format should I paste?

Use one payload per line when filenames do not matter, or use name,payload when you want predictable filenames. CSV headers are mapped when they include payload-like columns such as payload, url, content, data, qr, or value.

Why is a row blocked?

A row is blocked when the payload is empty, the UTF-8 byte count exceeds the selected error correction capacity, or the readiness score falls below 50. Check Readiness Audit for the specific Main issue and Next action.

Does Preview limit reduce the ZIP?

No. Preview limit only controls how many QR previews appear in QR Image Set. ZIP export includes every valid row up to the 1,000-row browser safety limit.

What does the 4.5:1 contrast warning mean?

It means the selected foreground and background colors fall below the scan-readiness contrast threshold. It is a conservative warning, not a formal QR pass-fail rule, so scan-test the exported image on the final surface.

Are pasted rows or CSV/TXT files uploaded?

The row parser reads pasted text and selected CSV/TXT files in the browser, and the ZIP is assembled in the browser session. Preview, archive generation, and chart export still require the page's QR, ZIP, and chart resources to load.

Glossary:

Payload: The exact text encoded in one QR symbol, such as a URL, Wi-Fi string, email URI, vCard, event record, or plain identifier.
QR version: The symbol size number from 1 to 40. Higher versions contain more modules per side and can hold more data.
Module: One dark or light square in the QR matrix.
Quiet zone: The blank border around the QR symbol. Four modules is the standard margin used as the readiness target here.
Error correction: Recovery data added to the QR symbol so scans can survive some dirt, damage, or obstruction.
Readiness score: A 0 to 100 row score based on capacity headroom, contrast, quiet zone, and selected error correction.
Manifest: The exported row record that connects each generated filename with its source name, payload type, byte count, status, and payload text.

References:

What is a QR Code, DENSO WAVE.
Point for determining the code area, DENSO WAVE.
Point for setting the module size, DENSO WAVE.
Understanding Success Criterion 1.4.3: Contrast (Minimum), W3C Web Accessibility Initiative.