Quick Response (QR) Code Generator

Scan Readiness Index

{{ readinessLabel }} · Version {{ versionEstimate }} · ECC {{ selectedEcc }}

{{ typeBadge }} {{ usagePresetLabel }} Bytes {{ payloadBytes }} Quiet zone {{ quietZoneModules }} modules Contrast {{ contrastRatioDisplay }} Transparent BG Logo {{ logoCoverageDisplay }} {{ readinessLabel }}

{{ warning }}

Payload template:

Generate one QR for a URL, text note, Wi-Fi login, contact, phone, SMS, email, or event.

Destination URL:

Enter the exact destination, including protocol and any path/query needed.

Plain text:

Use concise display text, such as a ticket note or short instruction.

Phone number:

Use E.164-style numbers such as +12025550123 when possible.

Use case preset:

Choose where this QR will be used; fine-tune exact pixels, colors, and logo settings in Advanced.

Error correction:

Use Q or H for print, rough surfaces, or center logos; M is balanced for screens.

Canvas size:

Use 300+ px for screen sharing and larger exports for print artwork.

Quiet zone: {{ quietZoneModules }} modules

Keep 4+ modules unless final artwork adds its own quiet margin.

Dot style:

Use Square for maximum reliability; rounded styles fit branded screen use.

Eye style:

Keep corners high contrast and distinct from decorative modules.

Colors:

Use dark foreground on light background; avoid low-contrast brand pairs.

Transparent background:

Use for overlays only when the placement surface stays light and uncluttered.

Gradient fill:

Use only when both gradient colors remain dark enough to scan.

Frame style:

Use None for raw exports or Scan me label for poster handoff.

Frame label:

Keep under 42 characters, for example Scan menu.

Logo coverage: {{ logoScale }}%

Keep logos small and test a real scan before print.

Logo image:

Drop or browse one PNG, JPEG, or SVG under 2 MB.

{{ logoDataUrl ? 'Drop another image to replace it.' : 'PNG, JPEG, or SVG only.' }}

Logo state:

Use Remove before reliability testing if scans are inconsistent.

Field	Value	Copy
{{ row.label }}	{{ row.value }}

Check	Status	Current value	Action	Copy
{{ row.check }}	{{ row.status }}	{{ row.value }}	{{ row.action }}

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

QR codes turn text into a square pattern that cameras can decode quickly. The encoded text may be a web address, a Wi-Fi login string, a contact record, a phone or message action, or a calendar event, so the scan result depends on both the symbol and the text hidden inside it.

Payload text becomes a QR matrix with a quiet zone, then scans into an action such as opening a page, joining a network, or saving a contact.

A scanner first finds the square boundary, reads the modules, repairs what it can, and reconstructs the payload text. Only after that does the device decide what to do with the text. A compact address can open a page, while a structured contact card or calendar record may ask another app to create a new item.

Scan quality depends on more than the code looking sharp. Long payloads require more modules, higher error correction leaves less room for data, small print reduces each module, weak contrast makes edges harder to separate, and a center logo can cover data. Those tradeoffs are easy to miss when the symbol is still large on a screen.

QR codes are useful for menus, guest networks, posters, slides, packaging, badges, and business cards. They are still just encoded text. They do not confirm that a link is safe, a password is current, a phone number is correct, or a printed code will work under glare, so the finished symbol needs a real scan before it is shared or printed.

How to Use This Tool:

Use the generator as a short scan-risk workflow rather than an artwork-only preview.

Pick a Payload template. Fill the required field for that mode, such as Destination URL, SSID, Phone number, SMS number, Full name, or at least one event field, until the preview area can render a symbol.
Choose a Use case preset, then check the summary for Version, ECC, payload bytes, quiet zone, contrast, and the current Scan Readiness Index.
Open Advanced and set Canvas size, Quiet zone, and Colors. Keep a dark foreground, light background, and at least 4 quiet-zone modules for the first reliable scan.
Add Dot style, Eye style, Frame style, Gradient fill, Transparent background, or Logo image only after the plain symbol works in Symbol Studio.
Open Payload Blueprint and confirm Payload bytes, Capacity used (selected level), Estimated QR version, Minimum foreground/background contrast, and Warning count.
Open Scan Checklist. If a row says Fix, resolve that issue, such as an empty required field, a URL missing http:// or https://, a quiet zone below 4 modules, low contrast, an event end time earlier than the start time, or a large logo without ECC H.
Use Readiness Radar to find the weakest score when the overall label is Balanced, Risky, or Fragile. Adjust the matching control before changing unrelated styling.
Copy the payload or download the finished symbol only after the encoded action works from the exported QR code, not just from the form preview.

Brand styling should come after a plain scan test. Decorative dots, gradients, transparent backgrounds, and logos can make the symbol fit a design, but they can also remove scan margin.

Interpreting Results:

Read the Scan Readiness Index with Warnings and Scan Checklist. The score gives a quick risk signal, while the warning text explains which tradeoff needs attention. A clean-looking preview can still be weak if it is dense, low contrast, missing quiet zone, or covered by too much logo area.

QR generator result bands and follow-up actions
Visible cue	Meaning	Best follow-up
Robust at 85 to 100	The current settings leave stronger scan margin across the measured checks.	Scan the exported symbol at final size and surface before distribution.
Balanced at 70 to 84	One design choice is already reducing safety, even if the preview looks acceptable.	Use Readiness Radar to decide whether capacity, contrast, quiet zone, logo, or ECC needs attention.
Risky at 50 to 69	The code may scan only in clean lighting, at a comfortable distance, or on a bright surface.	Shorten the payload, increase contrast, widen the quiet zone, reduce logo coverage, or raise ECC.
Fragile below 50	The current design is too close to failure for routine use.	Rebuild from a plain dark-on-light code before adding branding back.
Fix in Scan Checklist	A specific rule has failed, such as payload capacity, low contrast, narrow quiet zone, or unsafe logo obstruction.	Clear the failed row first, then rerun a scan test.

Do not overread a high score as proof that the destination is safe, the scanner app will interpret every payload identically, or the printed piece will work in every lighting condition. The final verification is a real scan of the exported symbol, including the same size, material, logo, and background it will use in production.

Technical Details:

The QR Code standard defines 40 square versions. Version 1 has 21 modules per side, version 40 has 177, and each step adds 4 modules per side. More data or stronger error correction usually increases the version. If the exported canvas stays the same size, a larger version makes each module smaller and harder for cameras to separate.

Error correction levels L, M, Q, and H add recovery data to the symbol. DENSO WAVE describes their restoration capability as approximately 7%, 15%, 25%, and 30% of total codewords. Higher levels help with dirt, damage, and small logo obstruction, but the same payload then needs more matrix space.

Formula Core:

The displayed size and readiness values come from the selected version estimate, canvas size, quiet-zone setting, contrast check, logo coverage, and error correction level.

\begin{array}{lcl} modules per side & = & 21 + 4 (V - 1) \\ quiet-zone pixels & = & \frac{canvas pixels}{modules per side} (quiet-zone modules) \\ R & = & 0.30 P + 0.22 C + 0.18 Z + 0.15 L + 0.15 E \end{array}

The displayed capacity estimate counts the final payload as UTF-8 bytes and compares it with byte-mode capacity for the selected error correction level. That is conservative for mixed content. Structured payloads such as Wi-Fi, contact, and calendar records may look short in the form but expand into longer encoded text.

QR payload families and their encoded text patterns
Payload family	Encoded shape	Why it changes scan risk
Web address or plain text	Exact text entered	Usually compact. A complete `http://` or `https://` address improves scanner handoff.
Wi-Fi access	`WIFI:T:mode;S:ssid;P:password;H:true;;`	The network name, password, security mode, and hidden-network flag are encoded into one string.
Email, phone, and SMS	`mailto:`, `tel:`, or `SMSTO:`	These prepare an app action. The user still reviews the call, message, or draft before sending.
Contact card	`BEGIN:VCARD` through `END:VCARD`	Name is required here; organization, title, phone, email, and site lines add bytes quickly.
Calendar event	`BEGIN:VCALENDAR` with one `VEVENT`	Title, location, notes, and UTC start/end values create a useful event draft but can become dense.

The quiet zone is the blank margin around the symbol. Standard QR guidance calls for four modules on every side. Reducing that margin may still scan in a clean test, but it gives the camera less clear boundary information, especially when the code sits near text, artwork, or the edge of a label.

Color checks use relative luminance contrast between the foreground and the effective background. When a gradient is enabled, the lowest contrast among the gradient colors drives the score. A transparent background assumes a light final placement surface, so the same file can scan well on white and fail on a busy or dark design.

Scan Readiness Index components
Symbol	Component	Scoring behavior
`P`	Payload headroom	Falls as capacity used rises past 60%, 85%, and 100% of the selected byte estimate.
`C`	Color contrast	Reaches full value at 7:1 or higher, gives a review-range score from 4.5:1 to 7:1, and drops below 4.5:1.
`Z`	Quiet zone	Reaches full value at 4 modules and scales down when the margin is narrower.
`L`	Logo safety	Starts at full value with no logo or small logo coverage, then steps down above 10%, 15%, 20%, 25%, and 30% area.
`E`	ECC resilience	Maps L, M, Q, and H to increasing resilience values, with H treated as the safest choice for rough print or logo use.

Worked Examples:

Short slide link

A slide that points to https://ex.co/menu can use Website URL, Screen / slides, ECC M, a 720 px canvas, a 4-module quiet zone, dark foreground, white background, and no logo. The Payload Blueprint should show a small byte count and modest Capacity used (selected level), so the Scan Readiness Index can land in Robust territory if no warnings are present.

Guest Wi-Fi card with branding

A Wi-Fi payload for SSID Cafe Guest, WPA password Summer-2026-menu!, and a 24% center logo may still render cleanly, but Scan Checklist can mark Logo obstruction as Fix when ECC is not H. The better correction is to reduce Logo coverage below 20% or switch Error correction to H, then scan the printed card from normal hand distance.

Event code with a time mistake

A calendar event with title Product Demo, location HQ Room 4, start time 2026-05-20 14:00, and end time 2026-05-20 13:30 still has enough text to render, but the warning list reports that the event end time is earlier than the start time. Fix the time fields first, then use Estimated QR version and Payload bytes to decide whether a long description should move to a linked page instead.

FAQ:

Why did the QR preview disappear or stay blank?

The selected payload needs enough content to build a real string. For example, Website URL needs a destination, Wi-Fi access needs an SSID, Phone call needs a phone number, SMS needs a number, Contact card needs a full name, and Calendar event needs at least one event field.

Why did the estimated version jump after a small edit?

QR capacity changes in version steps. A few more UTF-8 bytes can move the payload past the current capacity estimate, especially for vCard and calendar records where optional fields expand into line-based text.

Does ECC H make a large logo safe?

No. ECC H improves recovery headroom, but the checklist still treats large center obstruction as a scan risk. A logo above 20% area should be reduced or paired with ECC H and tested on real devices.

Should I use a transparent background?

Only when the final artwork keeps a flat light area behind the entire symbol and quiet zone. Transparent background mode adds a review warning because contrast is calculated as if the placement surface were light.

Do phone, email, and SMS codes send anything automatically?

No. Phone, email, and SMS payloads prepare an action for the device app. The person scanning still reviews the call, draft, or message before completing it.

Does my payload or logo get uploaded?

No separate backend is used for generating the symbol. After the page loads, payload assembly, logo reading, readiness scoring, chart data, copying, and downloads run in the browser.

Glossary:

Payload: The final text string embedded in the QR symbol.
Module: One dark or light square in the QR grid.
Quiet zone: The blank border around the symbol that helps scanners find the code boundary.
ECC: Error correction level, which trades usable payload capacity for recovery from dirt, damage, or partial obstruction.
QR version: The size tier that determines how many modules appear on each side of the symbol.
Scan Readiness Index: The 0 to 100 score combining payload headroom, contrast, quiet zone, logo safety, and ECC resilience.
vCard and iCalendar: Structured text formats used here for contact records and calendar event drafts.

References:

Information capacity and versions of QR Code, DENSO WAVE.
Error correction feature, DENSO WAVE.
Point for determining the code area, DENSO WAVE.
Understanding SC 1.4.3: Contrast (Minimum), W3C Web Accessibility Initiative.
RFC 6068: The "mailto" URI Scheme, IETF, October 2010.
RFC 3966: The tel URI for Telephone Numbers, IETF, December 2004.
RFC 2426: vCard MIME Directory Profile, IETF, September 1998.
RFC 5545: Internet Calendaring and Scheduling Core Object Specification (iCalendar), IETF, September 2009.