Static QR codes are free and never expire. Dynamic ones cost a little and let you fix the link later. Here's how to pick without overpaying.
Someone on your team is about to order 2,000 printed stickers with a QR code on them, and the honest question nobody's asking is whether that code can be fixed if the link behind it ever changes. Most people find out the answer the hard way, months later, when the destination page moves and every sticker in the warehouse is now pointing at a 404.
That's the entire difference between static and dynamic QR codes, and it's simpler than the pricing pages make it sound.
What's actually baked into the square
A QR code is just a pattern that encodes text, almost always a web address. There are two ways to build one, and they behave completely differently after you hit print.
A static code has the destination written directly into the pattern. Scan it and the phone reads that exact address, permanently. There's no server involved, no account needed, and no way to change it once it's printed. If you need the link to go somewhere else, you need a new code.
A dynamic code encodes a short redirect URL that you control, something like `nx.lnk/abc123`. The camera reads that short link, your account looks up where it currently points, and it bounces the phone straight there. The printed square never changes. What changes is the redirect sitting behind it, which you can edit from a dashboard in seconds.
Same job, same scan, same phone experience. The difference only shows up the day you need to change something.
The decision most people should make
Ask yourself one question: will this link ever need to change after it's printed, or do you want to know how many times it got scanned? If the honest answer to both is no, get a static code and stop reading. If either answer is yes, get dynamic.
| Situation | Static is fine | Get dynamic |
|---|---|---|
| Business card or vehicle decal that points to your homepage | Yes, homepages rarely move | Only if you want scan counts |
| Product packaging already printed and shipped | No choice, use static | Not an option after printing anyway |
| Menu, price list, or seasonal promo | Risky | Yes, content changes |
| One flyer for a single event | Yes | Overkill |
| Anything on a building sign, banner, or vehicle wrap | No | Yes, this stuff outlives its first purpose |
| You want to A/B test where the code sends people | No | Yes |
Most single-use, short-lived print is fine static. Anything durable, expensive to reprint, or reused across a campaign should be dynamic. Generate either kind free and decide per print run, not as a blanket policy. If the specific job is a restaurant menu, we've written a full menu QR setup guide that covers this same static-or-dynamic call in more detail.
The mistake we see constantly
The failure isn't picking static when you needed dynamic. That's annoying but fixable: you reprint. The expensive mistake is the reverse, pointing a static code at something that changes on its own, like a file you re-upload periodically. Re-upload a PDF to most storage or website tools and it gets a new address. The QR code doesn't know that. It keeps pointing at the old, now-dead address, and every printed copy in the field goes stale on the same day, with zero warning.
We've fixed this exact problem for clients twice: a static code baked into a vehicle wrap pointing at a "current specials" PDF that got replaced monthly. The wrap lasted three years. The PDF address didn't survive the first month. The fix each time was the same, swap to a dynamic code pointed at a fixed redirect, then update the redirect target whenever the file changes. The vehicle wrap never needs to be touched again.
Where dynamic earns its cost
- You're tracking a campaign. Scan counts by day and location tell you whether a print run is working before you commit to the next one. A static code can't tell you anything happened.
- The destination is genuinely temporary. Seasonal menus, event pages that get replaced yearly, a promo that ends and gets swapped for the next one, all good reasons.
- The print medium outlasts your content plans. Vehicle wraps, building signage, embroidered uniforms, anything expensive or slow to replace.
- You want one code across many print runs. Print the same QR code on business cards, a truck, and a trade show banner, then send all three to whatever page fits this quarter.
Where it isn't worth paying for
A one-off flyer for a single Saturday event doesn't need a subscription. A code on the back of a physical product going straight to your homepage, which almost never changes its root address, doesn't either. If you're printing five business cards for yourself and the link is your own static contact page, dynamic buys you a dashboard you'll check twice and then forget. Static, custom short domains, and scan analytics live on the paid plans; free static generation covers the rest.
If you already printed static and need to change it
You can't edit a static code after the fact, full stop. Your two options are reprinting or leaving the old link alive somewhere. The cheaper fix, if the volume justifies it, is a one-time redirect page at the old address that forwards to the new one. It's not elegant, but it buys you time without touching the print run, and it's exactly the situation dynamic codes exist to prevent next time.
Frequently asked questions
Can I convert a static QR code to dynamic later?
No. The destination is physically encoded into a static code's pattern, so there's nothing to redirect. Your only options are reprinting with a new dynamic code or setting up a redirect at the old static address, if you still control it.
Do dynamic QR codes expire?
Only if the account or subscription behind them lapses. As long as the redirect service stays active, a dynamic code works indefinitely, the same as a static one. What can change is where it points, which is the entire feature.
Is a dynamic QR code slower to scan?
The difference is a fraction of a second, an extra network hop to look up the redirect before the phone loads the destination. On a normal connection nobody notices it. It only becomes visible on a very weak signal, which would slow any web page down anyway.
Which one should a small business default to?
Static, unless you specifically want scan tracking or expect the destination to change. Most everyday uses, business cards, packaging, a link to your own stable homepage, don't need anything more than a free static code.
Can I track scans on a static QR code?
No. Static codes have no service in the loop to log anything, they're just a pattern pointing straight at an address. Scan counts, timestamps, and location data all require a dynamic code routed through a redirect you control.