A QR code is a square grid of black and white modules that encodes text, a web address, or contact details so a phone camera can read it instantly. You make one by typing your content into a generator (a website, your phone's built-in tool, or design software like Canva), setting the error-correction level, downloading a PNG, SVG, or PDF, and testing it with two different phones before printing. The one condition that decides everything downstream: a QR code has no fixed "destination" β the link lives in the pattern itself, so you can't edit it after printing unless the code is a dynamic type tied to a redirect service.
Most people finish a usable code in under two minutes. The failures happen later: at the printer, in a dim restaurant, or three months after a campaign when someone changes a URL and a thousand posters go dead. This guide covers the methods, the error-correction setting almost nobody adjusts, and the scan-failure cases the top results skip.
Step-by-Step: Building a Static Code From Blank to Printed
This is the sequence that actually works, in the order a careful person does it, not the order a generator's homepage suggests.
1: Decide static vs. dynamic first. Static codes embed the data directly and never expire; dynamic codes route through a redirect service you (usually) pay for and can edit later. Choose static if the destination never changes, dynamic if you'll repoint the link. 2: Shorten the destination URL before generating. Every character adds module density and makes the code harder to scan at small print sizes. 3: Open a generator. In Chrome on desktop, Chrome's own share menu (three-dot menu, then Cast, Save, and Share, then Create QR Code) builds one for the current tab. On iPhone, the Shortcuts app has a built-in "QR Code" action. 4: Pick the content type. URL, plain text, Wi-Fi network (SSID plus password), vCard contact, or email/SMS. Each produces a different data format the scanner interprets differently. 5: Set error correction to the highest level that still scans at your print size. The four levels are L (about 7% recoverable), M (15%), Q (25%), and H (30%). H survives damage but packs more modules into the same square. 6: Keep a quiet zone. Leave a blank border of at least four modules on every side. Cropping it is the single most common reason a printed code won't scan. 7: Download the vector version (SVG or PDF) for anything printed larger than a business card. PNG at 300 dots per inch minimum for everything else. 8: Test on two phones, one older. Scan at the final printed size, in the lighting the code will actually face, before you commit to a print run.
If a test scan fails, work backward in this order: check the quiet zone first, then the contrast (dark modules on light background, never inverted), then your print size against the module count, and only last the error-correction level. Reversing that order wastes time, because a weak contrast problem looks identical to a density problem at phone-camera distance.
Where to Generate One: Platform Comparison by Use Case
Four realistic paths exist, and they win for different people. The comparison below uses dimensions that matter in practice, not feature lists.
| Tool | Cost model | Editable after print | Best for | Main limitation |
|---|---|---|---|---|
| Chrome desktop share menu | Free, built in | No (static) | A quick code for a single URL | No design control, no vector export |
| Phone Shortcuts (iPhone) or Google Lens share | Free, built in | No | Wi-Fi and contact codes on the go | Fixed output size, no logo space |
| Canva (free tier) | Free with paid Pro options | No on free codes | Codes that match brand colors and carry a logo | Free-tier export limits; sized for graphics, not vector precision |
| Dedicated dynamic-QR services | Subscription, varies by provider | Yes, via redirect | Campaigns, menus, packaging you'll repoint | Recurring cost; the code dies if you stop paying |
The Chrome route is the fastest for a one-off link and produces a static code with no expiry. Canva wins when the code has to sit inside a design, but check the export format before you build β a raster-only export scaled up for a banner will blur the modules. Dynamic services win whenever the destination is a campaign, because you can change where the code points without reprinting.
Verdict by reader: if you're printing once and the link won't change, use a free static generator and save the vector file. If you're printing menus, packaging, or anything you'll repoint seasonally, a dynamic service is worth the subscription β but verify the redirect survives a lapse in payment, because the code itself carries no destination once the service stops answering.
Error Correction Levels and the Module Math Behind Scan Failures
A QR code is a matrix of modules, and the total is governed by the standard's version number β versions 1 through 40, set by the specification maintained by Denso Wave, the company that invented the format in 1994. Version 1 holds 21 modules per side; each version adds 4 modules per side, and version 40 reaches 177 per side. The larger the version, the smaller each module prints at a fixed physical size, and the harder a cheap phone camera reads it.
Error correction is the setting with the most leverage and the least attention. Level L recovers roughly 7% of damaged modules, M about 15%, Q about 25%, and H about 30%. Higher correction means more redundancy modules, which pushes you toward a higher version for the same data β so a logo dropped in the center of an H-level code damages a smaller share of the recoverable area than the same logo in an L-level code.
Here's the practical consequence. A business card code printed at 2 centimeters square with a version 10 pattern (57 modules per side) gives each module under 0.4 millimeters, which is below what many front cameras resolve at arm's length. Raise the print size or shorten the URL to drop the version. A restaurant table tent printed at 5 centimeters gives comfortable module sizes even at version 15.
If you're printing on a curved surface β a bottle, a can, a wrapped package β test the scan at the curvature before the run. The distortion behaves like damage, and level H is the only margin that reliably survives it. The exact module counts per version for your data length are listed in the ISO/IEC 18004 standard, so confirm against the standard rather than a blog table if precision matters.
Making a Logo QR Code Without Killing the Scan
Logo-in-center is the most requested customization and the most common way people break their own codes.
Keep the logo under roughly 20% of the code's total area, and only do it at error-correction level H. At H, up to 30% of the pattern is redundant, so a 20% logo sits inside the recoverable budget. At level M, the same logo eats into the 15% margin and scans fail at distance. This is arithmetic, not opinion: the logo is damage by the scanner's logic, and the recovery percentage is your allowance.
Place the logo dead center and nowhere else. The three large squares in the corners are finder patterns β the scanner uses them to orient the code. Cover one and the code won't locate itself at all, regardless of error correction. The smaller alignment square near the bottom-right of higher versions matters too; keep logos off it.
Use high-contrast, solid logos. A light logo on a dark code inverts the module pattern the scanner expects. If brand rules demand a light logo, place it on a white circle so the surrounding modules stay readable. Test at the smallest print size and the worst lighting you expect, then test again on a phone three or more years old, because older cameras struggle with the reduced contrast a logo introduces.
Dynamic vs. Static: What You Actually Pay For and When It Expires
The static-versus-dynamic decision is the one with long-term consequences, and the marketing around it obscures the mechanism.
A static code stores the data inside the pattern. It never expires, never costs anything, and never changes. A dynamic code stores a short redirect URL in the pattern, and that URL is controlled by the provider. You get editability, scan tracking, and sometimes A/B routing β in exchange for a recurring fee and a dependency.
What the top pages underplay: a dynamic code is only as durable as the company behind the redirect. If the provider shuts down, changes its pricing, or you stop paying, the code points at a dead address even though the printed pattern is intact. Check the provider's stated policy on codes after cancellation before you print anything long-lived. Static codes have no such failure mode.
The cost math depends on your provider and volume, and prices shift β confirm current pricing on the provider's own site rather than trusting a roundup, since these figures change often. The structural comparison is stable: dynamic wins when you need to repoint a printed asset, static wins when the destination is fixed and the code must outlive any single vendor. If a campaign will run for years with a single URL, static is the lower-risk choice, full stop.
Print Specs That Determine Whether the Code Survives Paper
Paper decisions sink more codes than generator choices, and the specifications below are the ones worth enforcing.
Contrast is the first rule: dark modules on a light background, never the reverse. Inverted codes fail on many scanner apps even though the standard technically allows them in some readers. Second rule: matte finish over gloss, because a glossy laminate reflects the phone's own light and blinds the camera at the angle people naturally hold it. Third: leave the quiet zone β the blank border of at least four modules β and don't let a designer trim it to make the layout tight.
For size, the working minimum depends on the module count, not a single number. A code that scans fine at business-card size with a short URL fails at poster size with a long one, because the version number changed. Print the same code at three sizes on a proof sheet and scan all three. If the smallest fails, shorten the URL and regenerate rather than upsizing an existing raster.
Ink spread on uncoated paper can bleed into narrow modules. For newsprint or kraft paper, request a higher error-correction level and a slightly larger print. On dark packaging, print the code on a white panel instead of lightening the modules. Sensory check worth doing: hold the proof under the actual light of the space β a dim bar, a sunny window β because a code that scans on a bright desk can fail in a dimly lit room.
QR Codes for Wi-Fi, vCards, and Event Check-In
Different content types produce different failure modes, and the special cases below cover the ones people hit.
A Wi-Fi QR code encodes the network name, password, and security type. Generate it only after confirming the exact SSID, including capitalization, and the security mode (WPA/WPA2/WPA3) β a mismatch leaves the phone spinning on "connecting." Test it on both Android and iPhone, because the two platforms parse Wi-Fi payloads slightly differently. For guest networks, use a separate isolated Wi-Fi network rather than handing out your main password.
A vCard contact code stores name, phone, email, and sometimes a photo. Photos inflate the data and push the version number up, so skip the photo unless the code is printed large. Event check-in codes should be dynamic if you're scanning attendance and tracking, static if you're just sharing a schedule.
The edge case that trips people: codes containing uppercase/lowercase-sensitive text. A URL is case-sensitive in its path, so a generator that "helpfully" normalizes your link can send scanners to a 404. Copy the final decoded content from a test scan and compare it character by character with what you intended before you print.
Designing a Code That Scans From Distant Seating and Low-Light Bar Tables
Small-format and long-distance contexts β table tents, stage screens, expo booths β have their own rules, and the usual business-card advice fails there.
For distance, the governing ratio is roughly ten-to-one: a code should be at least one-tenth the scanning distance. At a booth where people scan from 3 meters, the code needs to be around 30 centimeters on its longest side. That figure is a working rule of thumb from the scanning community, not a standard clause, so treat it as a floor and test at the real distance. Under that rule, a table tent scanned from 40 centimeters needs a code at least 4 centimeters wide.
For low light, contrast swings harder than size. A dark code on white card under a dim pendant lamp reads worse than the same code on a bright screen. If the venue is genuinely dim, print the code larger and keep the background white, not cream or gray. A phone flashlight helps, but only if the finish is matte.
Keep designs simple around the code. A pattern or photograph crowding the quiet zone functions like damage. Give the code clear white space, and resist the urge to place it on top of a busy texture.
Static Codes and Longevity: Five Failures and Their Fixes
Generation is easy; keeping a code alive is the discipline. These five failures cover most of the post-print problems.
Failure 1 β the dead link. A static code pointing at a page you later moved. Fix: prefer permanent redirects at the domain level, and keep old URLs alive indefinitely.
Failure 2 β the expired dynamic subscription. A paid provider's redirect stops answering. Fix: check the provider's post-cancellation policy before printing; archive a static fallback for long-lived print.
Failure 3 β the trimmed quiet zone. A designer cropped the white border to fit a layout. Fix: rebuild with the margin intact; never re-crop a code in an image editor.
Failure 4 β the inverted print. Light modules on dark stock. Fix: print on a white panel or switch to a scanner-tolerant design; test on older phones.
Failure 5 β the rescale blur. A small PNG blown up for a banner. Fix: always export vector for large print; if you only have raster, regenerate the code at the target size.
Each failure has a cheap prevention step done once at generation and a costly repair done after printing. The prevention list is shorter than the repair list, which is the whole argument for the steps earlier in this guide.
FAQ
Can you edit a QR code after it's printed?
Only if it's a dynamic code tied to a redirect service, and only by changing where the service points. A static code's data is baked into the pattern and cannot be altered after printing β you must generate and print a new code. Before committing to a print run, confirm which type you have, because the visual difference is invisible.
What's the smallest size a QR code can be printed at?
It depends on the module count, not a universal number. A short-URL code at version 2 or 3 with about 25 modules per side can print clearly at 1.5 centimeters, while a long-URL code at version 10 with 57 modules needs roughly 3 to 4 centimeters for the same readability. Confirm your version's module count against the ISO/IEC 18004 standard, then test at the real size.
Do QR codes expire?
Static codes never expire β the data lives in the pattern and has no server behind it. Dynamic codes expire when the provider's redirect stops working, whether from cancellation, a pricing change, or a shutdown. For anything printed to last years, the expiration question is really a question about the vendor, not the code.
Why won't my QR code scan even though it looks fine?
The most common causes, in order: a trimmed quiet zone, low contrast or inverted colors, a glossy finish reflecting light, or a code printed too small for its module count. Test the quiet zone first β it should be a blank border of at least four modules on every side. Then check contrast and print size before touching the error-correction setting.
Is a QR code free to make?
A static code is free on built-in tools like Chrome's share menu and phone shortcuts, and on free tiers of design apps. Dynamic codes with editing and tracking usually carry a subscription, with pricing that varies by provider and changes over time β confirm current pricing on the provider's own site. The free-stays-free rule applies only to static codes.
What error correction level should I use?
Default to M for ordinary print and raise to Q or H when you're placing a logo in the center or printing on a curved or textured surface. H recovers about 30% of the pattern and is the right choice for logo codes, but it increases module density, so pair it with a larger print size. Never drop to L for anything that must survive handling.
Can a QR code carry a virus?
A QR code is just a container for data, most often a URL. The code itself can't execute anything, but it can send you to a malicious site, so treat an unfamiliar code the way you'd treat an unfamiliar link. Preview the destination before opening it if your scanner app offers that option, and avoid codes stuck over legitimate ones on signs and parking meters β a known tampering pattern.
How long does it take to make one?
With a built-in tool, under two minutes: open the generator, paste the URL, download, and test. The time goes into the steps around generation β shortening the URL, choosing error correction, exporting vector for print, and testing on two phones β which add maybe ten minutes and prevent the failures that cost a reprint.