QR Code Generator: Complete Guide to QR Codes in 2026

Everything you need to know about QR codes. How they work, when to use static vs dynamic codes, error correction levels, and best practices for print and digital.

What this actually means in practice

A QR code is a two-dimensional barcode that links physical materials to digital actions. A restaurant can put one on a table, a developer can place one in an app, and a customer can scan it with the standard camera on a recent iPhone or Android phone. The code itself contains encoded data; it does not need to be connected to the internet to store a URL, message, contact record, Wi-Fi credential, or other supported payload.

QR codes use a grid of black and white modules, normally displayed as squares. Three position-detection patterns help a scanner determine the code's orientation. Timing and alignment patterns help the reader interpret the grid, while a format identifier and other control information identify how the data is arranged.

The amount of data a QR code can hold depends on its version and error-correction level. At the largest version, a QR code can hold up to 7,089 numeric characters, 4,296 alphanumeric characters, or 2,953 bytes of binary data. These are maximums under specific conditions, not practical targets. Real-world codes should be kept short, especially when they must be scanned quickly or printed at a small size.

Every standard QR code also includes error correction, which stores redundant information. The nominal recovery levels are 7% for L, 15% for M, 25% for Q, and 30% for H. This redundancy makes a code tolerant of modest damage or obstruction, but the percentages describe the proportion of codewords the specification can recover, not a guarantee that any randomly damaged 30% will scan. A fold across several data modules, a reflection, or a poorly printed region can still prevent a successful scan.

The first practical decision is whether the code should be static or dynamic. A static QR code contains its destination directly. If it encodes https://laiuse.com, that address is part of the printed code and cannot be changed without replacing the printed material. This is usually the simplest and least expensive option for menus, business cards, packaging, and other assets whose destination is stable.

A dynamic QR code contains a short address managed by a redirect service. The physical code remains unchanged while the service can send visitors to a new destination. This is useful for campaigns that need scan counts, for packaging that may need a revised support page, and for printed signs that should not become obsolete when a website changes. It also introduces dependencies: the redirect service must remain available, and visitors may see a short domain before reaching the final page.

Dynamic codes are worth considering for short campaigns. For example, a conference can print the same code on stage screens, badges, and table cards while changing its destination from the event schedule to a post-event survey. For a permanent product label, a static link to a stable product page is often more dependable. If the link must change, a permanent product URL that redirects internally is a useful compromise because the printed QR code never has to change.

Common uses include:

  • Business cards — a vCard can let a user add contact details to their address book.
  • Restaurant menus — a short URL can open a mobile-friendly menu without exposing a long address.
  • Wi-Fi sharing — an encoded network name, password, and encryption type can help guests connect.
  • Payments — PayNow, WeChat Pay, and similar systems use QR codes as payment instructions or requests.
  • Product packaging — codes can lead to instructions, registration, warranty registration, or authenticity checks.
  • Event tickets — a code can contain a ticket identifier or link to the check-in system.
  • App downloads — a short landing page can route users to the correct app store.

LaiUse provides a free QR code generator that runs in the browser. Open the generator, paste a URL, text, vCard, or Wi-Fi credential, choose the error-correction level and colors, and download the result as PNG or SVG. The Advanced QR Generator adds options such as custom logos and additional output formats. Browser-based generation can also be convenient for confidential or temporary payloads because the tool may not need to send the content to a server, but users should still verify the service's privacy and data-handling policy rather than assuming every generator is local-only.

On a website or app, a generated code can support a “scan to download” link, a printed contact shortcut, or a physical event-ticket handoff. An embed widget can also place a QR generator within a site. The embedded generator still needs sensible limits: protect it against abuse, validate input, and avoid making untrusted users believe that a code is secure merely because it is machine-readable.

Common mistakes and how to avoid them

Using too much data. A long URL, a detailed Wi-Fi password, or a large vCard produces more modules and a denser code. A longer code is harder to scan and may look dirty when reduced. Prefer a short, stable link such as https://example.com/wifi over encoding a long address directly. For Wi-Fi credentials, make sure the displayed network name and password are accurate and that the password is no longer than the format allows.

Choosing the wrong error-correction level. L produces the simplest code but offers little protection. M is a sensible general-purpose default. Q is useful for outdoor or textured printing. H creates a larger code and is appropriate when a logo overlaps the center, but a logo should not be so large or opaque that the remaining finder patterns and data modules are compromised. Error correction does not repair weak contrast, blurred printing, or an unsuitable colour scheme.

Ignoring contrast. Use a very dark foreground on a very light background. Dark blue on white or black on white is generally dependable. Yellow, red, orange, and similar light foreground colours are poor choices because their luminance is too close to the background. Translucent backgrounds, photographs, gradients, and drop shadows can also interfere with detection.

Cropping the quiet zone. The quiet zone is the blank margin around the code. The QR specification calls for a margin of at least four modules on every side. A quiet zone is measured in modules, not a fixed number of pixels, so it grows with the code. Text, borders, table edges, and other graphics should remain outside it.

Printing too small. A QR code should generally be at least 2 cm by 2 cm, or about one inch square, for close-range use. That is a baseline, not a universal guarantee. A 3 cm or 4 cm print is safer for longer content, more distant scanning, or less-controlled conditions. A 2 cm code may work perfectly on a business card but fail when viewed from across a room.

Using a low-resolution image. For print, use an SVG where possible or a PNG exported at a suitable physical size and resolution. A nominal 300 DPI is a common minimum for conventional print, but the correct calculation depends on the final dimensions. A 600-pixel-wide PNG printed at 5 cm gives roughly 3,048 DPI and remains sharp; the same image printed at 30 cm would be much less suitable. A code exported as a low-resolution thumbnail and then enlarged will show jagged or blurred modules.

Failing to test the final material. A code that scans on a bright monitor can fail on a glossy, folded, curved, dirty, or poorly lit surface. Test a real print at its intended size. Scan it with an iPhone camera, an Android camera, and, if the audience relies on it, a dedicated scanner. Test under the lighting and viewing distance expected in use.

Assuming every scan succeeds. Always provide a visible short URL, account number, or equivalent fallback next to the code. A restaurant menu should display its web address, and a packaging code should include a support URL. This is particularly important for people with impaired vision, damaged packaging, older devices, or an app that cannot handle the intended action.

Publishing unsupported statistics. Frequently cited industry figures have reported that 89% of US smartphone users had scanned a QR code, that scans rose 433% between 2021 and 2025, and that 47% of consumers preferred scanning to typing or searching. Survey wording, sample design, and market definitions vary, so these figures are useful context rather than universal conversion rates. Measure scans from a specific campaign instead of assuming a benchmark.

A worked example

Suppose a café prints table cards for a menu that changes every week. The printer does not want a different QR code every week, and the café also wants to know whether customers are using the cards. A dynamic QR code is appropriate. The printed code can encode https://qr.example.com/caf-menu, while the café changes the destination behind that short address each Friday.

The encoded content is short, so the resulting grid remains relatively simple. The café should use M error correction, provide a dark code on a white background, preserve the four-module quiet zone, and print it at least 3 cm square because table cards may be viewed under uneven lighting. An SVG is preferable for professional printing because the printer can scale the artwork without interpolation. If the café also needs a polished table card with its logo, the logo can sit beside the code rather than over it.

Before rollout, the café should print one card at the final size. It should test the code with an iPhone, an Android phone, and a dedicated scanner under normal café lighting. It should also test the final page on mobile data rather than Wi-Fi, confirm that the page loads without a sign-in prompt, and check that the destination is correct in every language used by customers.

For analytics, the redirect service should report scans by date, device category, and campaign, subject to its privacy policy. These reports can show whether people scanned the code, but they do not automatically prove that someone read the menu or made a purchase. The café should compare total scans with traffic to the menu and an optional, clearly explained feedback prompt rather than treating scans as customer conversions.

A second example illustrates when static is better. A hardware manufacturer prints 20,000 serialized labels. Each label links to the same long-running product-support page, and the company has no reason to change the destination. A static QR code avoids a redirect dependency and may be easier to audit. If support information will eventually move, the company should instead print a short static URL on its own domain and configure a server-side redirect. That preserves the original printed artwork while allowing the final destination to change.

For a Wi-Fi card, the payload may contain WIFI:T:WPA;S:Cafe-Guest;P:correct-password;;. A scanner can use that information to join the network, but cameras and apps differ in their support for Wi-Fi payloads. The card should also state the network name and password visibly. If security policy requires guests to change the password frequently, a static QR code containing a fixed password will become obsolete; a dynamic web page with current access details is more appropriate.

Limitations and when to use something else

QR codes are not a security mechanism. A static code exposes exactly what is encoded, and a dynamic code exposes the short redirect address. Anyone who can photograph it can copy the destination. Encryption or authenticated access must happen at the destination, using techniques such as signed URLs, expiring tokens, application login, or device-specific verification. A QR code should not replace authentication for refunds, medication access, account recovery, or other sensitive transactions.

Dynamic QR codes also depend on network availability, DNS, the redirect provider, and the final website. If the service is down or the domain expires, every printed code can fail at once. Short links can also be mistyped, blocked by security software, or associated with suspicious activity. For long-lived physical assets, a short link on an organisation-controlled domain or a stable static code generally offers better control.

Very small spaces may require a Micro QR code, but ordinary cameras and scanners do not support Micro QR as reliably as standard QR. Rectangular iQR codes and branded Frame QR designs can fit particular layouts, yet they have less scanner compatibility. JAB-style high-density colour codes can carry more data in some implementations, but standard monochrome QR remains the safest choice for general audiences.

QR codes can also be obstructed, replaced, or covered by an unwanted sticker. They are not proof that the destination is legitimate. Payment codes, event tickets, and product-authentication labels should be placed where tampering is visible and should use destination-level checks. A colour logo or decorative overlay is not a trademark-security feature.

For a short URL that a user can easily type, a memorable domain or short vanity URL may be more accessible. For a highly complex document, a download link may work better than encoding the document into the code. For one-to-one authentication, NFC, Bluetooth, or a conventional serial number may be more appropriate. Use a QR code when a camera scan is faster and more convenient than typing, not merely because it is available.

Printed codes need ownership after launch. Record the generator, destination, payload, error-correction level, colours, print date, and responsible owner. Dynamic links should be reviewed for expired campaigns, changed pages, and security events. Static packaging should be checked periodically as well, because a dead URL remains a dead URL even though the code itself still scans.

Troubleshooting

If a code does not scan, first increase the screen brightness and move the phone slightly. A faint camera or autofocus problem can resemble a defective QR code. Confirm that the device's camera and QR-scanning service are enabled, then try a second phone. If both fail, examine the border, contrast, and physical condition before regenerating anything.

When the code scans but the wrong action occurs, inspect the payload. Extra spaces, missing protocol prefixes, line breaks, and incorrectly encoded characters can alter the result. URLs should normally begin with https://. vCards and Wi-Fi payloads should follow the format expected by the target operating system, and passwords containing semicolons or other reserved characters need appropriate encoding.

If a printed code works on screen but not on paper, the image may have been exported at the wrong size or resolution. Check the print dimensions rather than only the pixel dimensions. Regenerate it as an SVG or as a higher-resolution PNG, and ask the printer not to crop, stretch, or compress it. A minimum four-module quiet zone must remain around the artwork.

If the code works indoors but fails outdoors, switch from L or M to Q or H, increase its printed size, and test under glare. Avoid glossy finishes and direct reflections. Codes on transparent packaging, frosted plastic, or curved bottles can also require a larger physical size because the surface changes the optical conditions.

If a dynamic code opens an error page, verify the redirect record, domain status, HTTPS certificate, and final destination. Test the short URL directly in a browser. A code can be perfectly valid while the service behind it is unavailable. If a URL is flagged by scanners, review the destination and any recently introduced redirects rather than repeatedly changing the QR artwork.

When a logo causes failures, reduce its width, increase contrast, and use Q or H error correction. Do not cover any finder pattern. A practical logo should occupy no more than roughly 10% to 15% of the code's area, although the exact safe area depends on its shape and the generator's mask selection.

If different phones behave inconsistently, test more than one operating system and scanning method. A dedicated scanner may support a payload format that a basic camera does not, and some corporate phones have restricted camera or profile permissions. Keep a manual fallback whenever a failed scan would cause inconvenience or block access.

Frequently asked questions

What is the best QR code size for printing? At least 2 cm by 2 cm for close-range use, but 3 cm or 4 cm is safer for long content, poor lighting, or greater viewing distances. The right size also depends on the number of modules, the print material, and the scanning distance.

Should I choose static or dynamic QR codes? Choose static for stable, permanent destinations and simple deployments. Choose dynamic when you need scan analytics or must change the destination without reprinting. For important long-lived materials, a static short URL on your own domain can provide both stability and control.

Which error-correction level should I use? M is a good general-purpose default. Use Q for outdoor signs, textured materials, or moderate obstruction, and H when a logo overlaps the code. L produces the least redundant code and is best only when printing quality and handling are reliably excellent.

Can every phone scan a QR code? Most current iPhone and Android cameras can scan standard QR codes, but support for vCards, Wi-Fi payloads, payment formats, Micro QR, and other specialised variations varies. Test the exact action on representative devices rather than testing only whether the camera recognises the grid.

Are QR codes safe? A QR code is a carrier, not a security guarantee. It may open a legitimate site, a phishing site, a redirect, or a sensitive action. Inspect unfamiliar destinations, verify payment or identity requests independently, and use application-level authentication and signed links where appropriate.

What is the best file format for a printable QR code? SVG is usually best because it remains sharp at any scale. A high-resolution PNG is appropriate for digital and ordinary print use. Avoid saving a small preview image, using JPEG compression, or enlarging a low-resolution export.

How much data can a QR code contain? The theoretical maximum is 7,089 numeric characters, 4,296 alphanumeric characters, or 2,953 bytes at the largest version and lowest error correction. Practical codes should be much shorter because density reduces scanning reliability, especially at small printed sizes.

Can I put a logo in the centre of a QR code? Yes, if you use adequate error correction and leave a generous clear area. A logo covering about 10% to 15% of the code is a common starting point. The code must still have strong contrast, a four-module quiet zone, and no covered finder patterns.

Why does a QR code scan on my phone but not on another? Check the other phone's camera permissions, software version, autofocus, and QR-scanning mode. It may also be affected by brightness, glare, screen damage, or an unsupported payload type. If both devices fail, focus on the code's contrast, size, quiet zone, and print quality.

Do QR code scan statistics show conversion? Not by themselves. A scan records an interaction with the code, not whether the visitor read the page, completed a purchase, or returned later. Connect scan data with destination-page analytics and, where appropriate and transparent, a voluntary follow-up action.

Should a restaurant menu QR code contain the menu directly? It is usually better to encode a short link to a mobile-friendly menu. This keeps the code compact, allows prices and items to change without reprinting, and makes corrections easier. Display the web address as a fallback.

Do QR codes expire? A static code's data does not expire unless its destination does. A dynamic code stops working when its redirect service, domain, or account is unavailable or cancelled. Test printed batches and assign an owner to monitor long-lived links and campaigns.