You can create a working QR code in under a minute: open a reputable generator, choose the type of content you want to encode, paste the URL or text, and download the resulting image as PNG for screens or SVG for print. The parts that trip people up come later — picking the wrong error-correction level, printing a code too small for the scanning distance, or getting locked into a generator that stops working when a free trial ends. This guide walks through the actual steps on screen, the settings that matter, and the failure cases worth knowing before you print anything.
QR codes are an ISO standard, ISO/IEC 18004, and the current revision is ISO/IEC 18004:2015. That matters because "QR code" is not a proprietary format owned by one company — anyone can encode one, and the spec defines how the black-and-white grid becomes readable data. The centerpiece is a Reed-Solomon error correction scheme that lets a scanner rebuild missing pieces. On paper, a QR code with the highest error-correction setting can survive up to 30% of its area being obscured. In practice, the scannability depends on far more than that single number.
The single biggest decision you make before generating anything is static versus dynamic. A static QR code encodes your data directly into the black modules, so it never expires and needs no server. A dynamic QR code encodes a short redirect URL and sends the scanner to a host that resolves to your real destination — which means you can change the destination later, but you're now dependent on that host staying online and your plan staying active. The rest of this article handles both paths, plus the settings and edge cases that decide whether your code scans on a cheap phone or under fluorescent store lighting.
Pick Static or Dynamic Before You Generate
The static-versus-dynamic decision should be made first because it determines which generator you can use and what your code can do later. Static codes are free everywhere and permanent by construction — the destination lives inside the pattern itself. Dynamic codes require a subscription at most reputable providers and route through a short URL, so they're only worth it if you need tracking, editable destinations, or a scannable code that survives a typo fix.
Cost is the honest differentiator. Most reputable dynamic QR providers run paid plans in the low-to-mid tens of dollars per month per code after a free trial, with annual programs frequently around $100–$200 per year for a single code. Those prices shift constantly, so confirm the current rate on the provider's own pricing page before you commit — and read how many scans the plan includes, because per-scan ceilings on the cheap tiers are the most common billing surprise.
Static codes have zero ongoing cost and no expiration date. The trade-off is that every change requires a new code, which is usually fine for a business card, a Wi-Fi network, or a packaging label, and painful for a restaurant menu or a marketing campaign where the destination may change. If your content is permanently fixed, use static and skip the subscription question entirely.
There's a middle option worth knowing: some print shops and in-house tools generate "dynamic" codes through a provider you self-host. If you're technically comfortable running a small redirect service, you can get the tracking and editability benefits without a monthly fee — but you own the server uptime. For everyone else, the rule is: static unless you specifically need to change or count scans.
Choose a Generator You'll Still Be Using in Two Years
The generator you pick is a durability decision, not just a convenience one. A code printed on a product label or a shop window has to scan for years, and if the generator folds or changes its terms, a dynamic code can go dead. Static codes are safer by construction because the data is in the image. For dynamic codes, favor providers with a public track record, published uptime information, and a clear data retention policy — QR Code Generator (bit.ly family), QR Tiger, and Flowcode are among the well-known commercial names, and many print shops use them as white-label backends.
Free online generators are perfectly fine for a one-off static code and fine for nothing else. Many of them inject their own branding into the pattern, lock scanning behind an account, or quietly convert a "free" static code into a dynamic one at download — which is exactly the trap. Read the download screen carefully: a code labeled "static" should let you save the PNG without creating an account. If it doesn't, move on.
For dynamic codes, check three things before you pay: whether the destination is editable after purchase, whether scan data is exportable in CSV, and whether the plan continues to resolve scans if you downgrade. Providers vary on that last point, and a lapsed subscription killing a live campaign is a common complaint. The official specification lives with ISO, but the business terms live with the provider — read them.
If you're printing many codes at once — a batch of serials, a warehouse of shelf labels — skip the consumer web tools and use a scripted generator. Libraries like Python's qrcode or the qrcode npm package produce identical output to commercial tools and can encode thousands of unique values from a CSV. That's the right call for anyone generating more than a handful of codes regularly.
Create a Static QR Code in Seven On-Screen Steps
Here's the concrete walkthrough for a standard static code, using the layout you'll see on most reputable generators (the field names may vary by one or two words, but the order is consistent). The example is a business website URL.
1: Open the generator in a desktop browser — mobile web generators often hide options like SVG export. Enter the URL, text, or data in the content field. 2: Choose the type. "URL" is the default for a website; switch to "Text," "Wi-Fi," "vCard," or "Email" if you're encoding one of those instead. Each type has its own fields — Wi-Fi asks for SSID, password, and encryption mode. 3: Set the error-correction level. Most tools default to "M" (medium, ~15% recoverable). For clean digital use, "M" is fine. For print that may get scuffed or partially covered, choose "Q" (25%) or "H" (30%). 4: Pick a size. For printed codes, leave the module size at least 4 px per module at export, then scale up in print design — never stretch a small PNG. 5: Choose the output format. PNG for screens and most online use; SVG for print because it scales infinitely without blur. Some tools also offer PDF. 6: Set foreground and background colors. Standard black on white is safest. If you want branding, keep dark-on-light with at least a 3:1 contrast ratio; inverted (light-on-dark) codes fail on many older scanners. 7: Download, then test with at least two phones and one app — the built-in camera on both iOS and Android, plus a dedicated scanner if you have one.
Failure handling matters more than the happy path. If a code won't scan, check contrast first, then quiet zone (the blank margin; aim for at least 4 modules), then the physical print size relative to the viewing distance. A useful rule from the QR spec's guidance is roughly 10:1 — a code 2 cm wide should be readable from about 20 cm. If you encoded a long URL and the pattern looks dense, shorten the URL with a link shortener or switch to a dynamic code, because density is a major cause of scan failures on budget phones.
Set Error Correction and Module Size for the Real Printing Distance
Error correction and physical size are the two settings that decide whether a code survives real-world conditions, and they work against each other. Higher error correction means more modules, which means a denser, visually busier code — and a denser code at the same print size is harder to scan. The engineering answer is to hold the print size constant and raise the tolerance for damage only as much as the environment demands.
For a clean digital display or a well-protected label, medium (M) is fine. For packaging that ships, product tags, and outdoor signage, go to Q or H. A rough guide: Q when the code may get partial occlusion (a hand over a corner, a sticker on top), H when significant damage is expected or when you're embedding a logo in the center. Logo embedding is the one common reason to go H — a centered logo nibbles into the recovery budget, and H gives you the most headroom before scanning degrades. Many generators offer a logo option under "Design" or "Customize," and it's worth testing the result rather than trusting the preview.
Physical size is where most DIY print jobs go wrong. The relationship between code size, module count, and scan distance is documented in the ISO spec's guidance and echoed by print vendors like Avery Dennison and HP's print guidance: a code needs enough pixels or ink per module to resolve at the reader's distance. A short URL (around 20 characters) at M may be 21×21 modules; a long tracking URL can push past 40×40. At the same print size, the long one has smaller modules and fails sooner.
The practical rule is to decide the scan distance first, then work backward. For a restaurant table code scanned by a seated diner at arm's length or closer, 2–3 cm often works. For a poster scanned from across a room, aim for 10 cm or larger. If your content is dense, shorten it rather than enlarging the print — every extra character is bytes the pattern must carry.
Generate Wi-Fi, vCard, and Other Non-URL Codes Correctly
Non-URL QR codes carry structured payloads, and the format matters more than the visual. The Wi-Fi format is WIFI:T:WPA;S:NetworkName;P:password;; — the encryption type (WPA, WEP, or nopass) is embedded, and a missing field breaks the connection. Some generators hide the raw string behind friendly fields; still verify the encryption type matches your router (WPA2/WPA3 are typically encoded as "WPA" in the standard).
vCard codes encode contact information as a small CRM-style record. The critical gotcha is character set and length: names with accents, long job titles, and four phone numbers can push a vCard past what a cheap scanner will resolve. Trim to name, organization, phone, email, and website, and test on both iOS and Android, because the two platforms parse vCard fields slightly differently.
For Wi-Fi, security is the honest boundary. A printed Wi-Fi code hands a guest access without retyping a password, which is convenient — and also means anyone who photographs it gets the credential. Don't put a Wi-Fi code with the main network password on a publicly visible surface; use a guest network and rotate the password if the code circulates widely. This is a real risk, not a theoretical one, and it's the reason some venues prefer a staffed password instead.
Event ticketing, payment links, and multi-step actions are the wrong fit for static codes. A payment link is a URL and technically works, but every generator's "payment" template is just a URL wrapper — nothing about the code confirms the payment. For event tickets, use a platform that issues codes in its own system, so the code and the ticket validation live in one place. A static vCard or Wi-Fi code is genuinely useful; a static code pretending to be a ticket is not.
Follow the ISO Size and Density Rules Before You Print
Printing is where a technically correct code becomes a working one or a regret. The standard advice — quiet zone of at least 4 modules, dark modules on a light background, no stretching — is repeated everywhere because violating it is the single most common print failure. A quiet zone is the blank border around the pattern; crop it and many scanners can't find the code's edges. Inverted colors (white modules on dark background) fail on a meaningful share of budget scanner apps that assume dark-on-light.
Contrast is measured, not eyeballed. A 3:1 ratio between foreground and background is a workable minimum, and black on pure white is roughly 21:1. If brand colors are mandatory, test the actual printed proof under the actual lighting — fluorescent store light, sunlight, and phone-camera white balance all shift how the code looks. A color that passes on screen can fail in print.
Material choices interact with the code. Glossy lamination creates reflections that confuse scanners; matte lamination and uncoated stock scan more reliably. Curved surfaces — bottles, cups, vehicle panels — distort the pattern, so print smaller and place the code on the flattest available area, or wrap it around a cylindrical surface only with a dedicated test. For anything long-lived (outdoor signage, product labels), print one proof and scan it from the intended distance in the intended light before committing to a run.
Let me put one worked example on the table, since this is where a lot of printed codes fail silently. A 40×40-module code printed at 4 cm wide gives each module roughly 1 mm — only just enough for a phone camera at close range, and marginal under fluorescent light where reflections and motion blur eat the margin. If your content is a long dynamic URL and the print area is limited, shortening the URL to around 20 characters can drop the code from roughly 40×40 to near 21×21 modules, giving every module nearly twice the physical width at the same print size. That single edit is often the difference between a code that scans on the first try in a dim restaurant and one that sends customers hunting for a better angle. Shorten first; enlarge second.
Read Scan-Time Mistakes and Fix Them Fast
The failures people actually hit, in roughly descending frequency: low contrast or inverted colors, a quiet zone that got cropped, a code too small for the distance, a long dense pattern on a weak phone camera, and lamination glare. Each has a direct fix. If the code scanned in your hand but not on the poster, the failure is almost always size-versus-distance, not the pattern itself.
Scanning behavior on iOS and Android differs enough that testing on only one is a mistake. The built-in iOS Camera app has scanned QR codes since iOS 11, and Android's Google Lens and built-in camera scanners are robust on recent builds. Older devices and third-party apps are less forgiving, and budget Android phones sold in emerging markets may have weaker autofocus modules. Test on the worst phone you expect your audience to use, not the newest.
The dynamic-code failure mode is distinct: the code scans fine and the redirect fails. That happens when the destination changes, the plan lapses, or the provider's redirect service has an outage. Before a campaign or a print run, load the destination and confirm the provider is resolving it, and keep a static backup URL in the design if the code is load-bearing. For a menu at a restaurant, a static PDF URL is more robust than a branded dynamic redirect.
There's no scan-count limit built into a static QR code, and no way to know how many times it was scanned — tracking requires the dynamic redirect. If someone tells you a static code can count scans, they're describing a feature of the app or camera, not the code. For anything where you need numbers, go dynamic and accept the subscription; for everything else, let the code be a code.
Five QR Code Myths That Cause Real Damage
The persistence of QR myths costs businesses money every year, and most of them are easy to test. Here are the ones I hear most often, with the correction stated plainly.
Myth 1: "A QR code has a fixed maximum of 30 characters." False. The spec's capacity depends on the version and error-correction level, and the largest versions hold thousands of characters at low error correction. The practical ceiling is set by the print size and camera quality, not the format — a dense code is hard to scan, not impossible.
Myth 2: "Dynamic codes last forever." False unless the provider does. The destination lives on their server, and if the plan lapses, the redirect commonly breaks. Confirm the expiration terms before printing.
Myth 3: "You can't embed a logo without breaking the code." You can, at error correction H, with a centered logo and a test scan. The risk is real but manageable.
Myth 4: "Any black-and-white pattern is a QR code." False. The pattern must be a valid QR symbol with finder patterns in three corners. A decorative square grid won't scan.
Myth 5: "QR codes are insecure by nature." The code itself is just data; the risk is the destination. Quishing — malicious QR codes in phishing emails or on parking meters — is a real attack, and the fix is verification before scanning, not distrust of the format.
When a Different Format Beats a QR Code
QR is not always the right answer, and the honest cases where something else wins are worth knowing. For a single, low-value interaction with a short lifespan, a plain short URL or a link in text is simpler and has no scan-distance failure mode. QR adds value when a camera scan is faster than typing, when the content is too long to type (a full Wi-Fi password), or when the code is printed on a surface where a link can't go.
Barcodes (UPC/EAN for retail, Code 128 for logistics) beat QR for high-volume warehouse scanning where a laser scanner is faster than a camera and the data is short. NFC tags beat QR for tap-to-interact where the user has the choice and the tag is physically close — payment terminals and transit gates. For packaging, standard GS1 Digital Link is replacing static QR codes because it encodes product data in a structured, scanner-agnostic way, and GS1 — the body that owns the UPC standard — publishes the requirements.
If you're building a product where the code is central to the user experience, evaluate GS1 Digital Link before defaulting to a QR code, because it's designed for the manufacturer-to-regulator chain and avoids rebuilding the wheel. For everything else — a business card, a table card, a poster — QR remains the lowest-friction default, and the pitfalls in the earlier sections are the whole of the discipline.
For a small local business, a QR code on a table card that opens your menu is still the simplest solution. For a global brand, the code is one component in a much bigger labeling system, and it should be chosen against that system, not in isolation.
FAQ
Is a QR code still free to create in 2026?
Yes for static codes — most reputable generators still offer free unlimited static creation. The paid upgrade appears when you need dynamic redirects, tracking, or editable destinations, which are typically subscription products at most providers. Read the download screen to confirm you're getting a static file and not a trial-tied dynamic one.
How much data can a QR code actually carry?
ISO/IEC 18004 defines the capacity, and it depends on the symbol version and error-correction level. At the highest versions with low error correction, the standard allows several thousand numeric characters; the practical limit for scannable print is far lower, usually a short URL or a compact vCard. Denser codes still work but demand larger prints and better lighting to scan reliably.
Why does my printed QR code fail under store lighting?
Glare from glossy lamination and the shifting white balance of phone cameras are the usual culprits. Matte lamination, uncoated stock, and a test scan under the actual lighting catch most of it. If the failure happens only in one location, reproduce the light there before reprinting.
Do I need error correction "H" for every printed code?
No. Q or M is sufficient for most clean print, and H is worth it mainly when you're embedding a centered logo or the code may be partially covered. H also makes the pattern denser, so pair it with a larger print size or a shorter URL to balance the trade-off.
Can a QR code be changed after it's printed?
A static code cannot — the data is baked into the pattern. A dynamic code can redirect elsewhere through the provider's server, which is the whole reason to pay for one. If changeability matters, choose dynamic and keep the subscription active.
Are QR codes a security risk?
The code format itself is safe; the destination is the risk. Quishing attacks plant malicious QR codes in emails, parking meters, and flyers, so verify the source before scanning. For your own codes, ensure the destination is HTTPS and confirm the redirect link before printing.
Does a QR code work without internet?
The code doesn't need connectivity to be scanned — it's decoded by the camera and the device's software. The destination usually does need internet. Wi-Fi configuration codes are the main exception: the code carries the network name and password, so the device can join without going online first.
This article is general information, not a security, legal, or compliance opinion. For codes used in regulated packaging, payments, healthcare, or labeling, confirm the current ISO/IEC 18004 and GS1 requirements with the standards bodies and a qualified local adviser before committing to a print run.