A static QR code carries its destination inside the pattern itself, so it is free to create, works forever, and can never be changed once printed. A dynamic QR code is a short link that redirects through a service, which makes it editable and trackable but dependent on that service staying online. Which one you need comes down to three questions: will the destination ever change, do you need scan data, and who controls the link?
What a static QR code actually is
The pattern of a static QR code is the data. Whether it holds a web address, plain text, Wi-Fi credentials or a contact card, the information is encoded directly into the black-and-white modules. Any phone camera can decode it on the spot — no app, no account, no server involved.
That has three practical consequences. First, static codes are free: any decent generator, including QRCodeMax.Vip, produces them without a subscription. Second, they never expire, because there is nothing to renew and nothing to keep online. Third, they are permanent in the strictest sense: if you need to change what the code points to, you generate a new pattern and reprint it. The code already on the wall will point to the old destination for as long as the ink lasts.
What a dynamic QR code actually is
A dynamic QR code does not contain your destination. It contains a short URL owned by the QR service, and when someone scans it, that service redirects them to your real destination. The pattern on paper never changes; the redirect behind it can.
This unlocks two things a static code cannot do. You can edit the destination after printing: fix a typo, swap a landing page, refresh a menu, retarget a campaign. And you can measure: most dynamic services log scans, often with rough time and location data, which is why marketers favour them on flyers, posters and ads.
The trade-offs are just as real. Dynamic codes usually require a paid subscription, and they only work while the provider is online and your account is in good standing.
The differences that actually matter
- Where the data lives: inside the pattern itself (static) or on the provider's redirect (dynamic).
- Cost: static is free; dynamic is typically a subscription.
- Editability: static is fixed at print time; dynamic can be repointed at any moment.
- Analytics: static offers none; dynamic usually includes scan counts and timing.
- Lifespan: static works as long as the print and the destination exist; dynamic works as long as the provider does.
None of these points is inherently "better". A free code that cannot be corrected and a paid code that cannot outlive its provider are each the right tool in the right situation.
When a static code is the right choice
Choose static when the destination is stable and the print will live a long time. A link to your homepage, a product manual that will not change, a contact card, Wi-Fi credentials for a guest network — all of these are set-and-forget data, and a static code handles them at zero cost with zero maintenance.
There is also a middle path worth knowing: a static code that points to a URL you own. If the code leads to yourdomain.com/menu rather than to a document baked into the pattern, you can change what appears at that address whenever you like — new menu, updated prices, revised brochure — without touching the printed code. You get most of the flexibility of a dynamic code with no third-party dependency and no subscription, because the redirect lives on your own domain.
When a dynamic code earns its keep
Pay for dynamic when at least one of these is true.
The destination changes often. Seasonal menus, campaign landing pages, event schedules — editing a redirect beats reprinting every time the content moves.
The print run is large or expensive. Thousands of brochures, product packaging, a painted mural: if a mistake or an update is even plausible, dynamic lets you correct it without reprinting. A static code with a typo in the URL is permanently dead plastic.
You need scan data. If you want to know whether the flyer or the poster actually brought people in, dynamic analytics are the only way to get that from a printed code.
A decision guide for everyday examples
Business card
Static. A card sits in wallets and desk drawers for years, and nobody wants to renew a subscription to keep it working. Encode a vCard or a link to your own site. If you later redesign the site, keep the old address alive with a redirect on your own domain and the card stays valid.
Restaurant menu
Dynamic is a genuinely good fit here. Menus change with prices, seasons and stock, and editing a redirect beats reprinting table tents every week. The caveat: if the menu depends on a QR subscription and you cancel it, every table sign dies at once. A static code pointing to a page on the restaurant's own domain delivers the same editability without that risk.
Product packaging
Packaging can sit in warehouses and on shelves for years, so a long-lived, stable destination — a manual, a registration page, a support hub — argues for static, or for a redirect you host yourself. Dynamic makes sense if you need to update the target over time or track engagement, but only with a provider you would bet a production run on. A useful rule of thumb: the longer the print's expected life, the stronger the case for static.
One-off Wi-Fi sign
Static, without hesitation. A Wi-Fi QR code encodes the network name, password and security type directly into the pattern, so a phone can join the network even with no internet connection and no service involved. The only reason to reprint is a changed password.
The risks of dynamic codes
Service shutdown
This is the defining risk. If the provider shuts down, drops its free tier, or you cancel the subscription, every printed dynamic code becomes a dead link: the pattern still scans, but the redirect goes nowhere. You cannot simply move the codes to a new provider either — the pattern physically encodes the old provider's short domain, so recovery means reprinting. This is why dynamic codes suit campaigns with a measurable lifetime better than prints meant to last a decade.
Short-link trust
A dynamic code scans to an opaque short link, and people cannot see where it leads before opening it. The same short URL could lead to your menu or to something hostile, which is why some people — and some phone safeguards — treat unfamiliar short links with suspicion. If you use dynamic codes, choose a provider whose domain people are comfortable seeing, and remember that trust in your print partly rests on theirs.
Lock-in
Subtler than shutdown, but related: your redirect rules, your analytics and your printed codes all live inside one vendor's system. Before committing, check what happens when you stop paying and whether destinations can be exported — while keeping in mind that the printed codes themselves will still point at the provider's domain either way.
Conclusion
Static if the destination is fixed and the print is permanent; dynamic if you need to edit after printing or measure scans, and you accept the dependency that comes with it. When in doubt, use a static code pointing to a URL you control: it is free, it works forever, and you can still change what people see when they arrive.