What actually happens when you scan each kind
With a static code, a scanner reads the pattern and decodes your data right there — a URL, a Wi-Fi password, a contact card, whatever you encoded. That's the entire transaction. No server is involved in the decoding itself.
With a dynamic code, what's actually encoded in the pattern is a short link on the provider's own domain (something like qr-provider.com/r/a1b2c3). When scanned, the phone opens that link, which hits the provider's server, which looks up what you originally wanted it to point to, and redirects there. That lookup step is the whole point — it's what lets them let you edit the destination later without reprinting — but it also means the code now depends on that server being reachable, indefinitely, for as long as the code exists in the world.
Why "free" dynamic generators can turn into a problem later
The business model behind a lot of free QR tools is exactly this redirect step. A static code costs them nothing to give away — it's just math, generated once in your browser or theirs. A dynamic code, on the other hand, needs their servers to keep running forever, so it's usually the feature that gets gated behind a free trial, a scan limit, or a subscription.
- Free tiers commonly cap how many scans a dynamic code can handle per month before it stops resolving.
- Trial periods (often 14–90 days) can end with the code silently breaking unless you upgrade.
- If the company shuts down, gets acquired, or discontinues the product, every dynamic code they ever issued can stop working at once — including ones you paid for.
None of this is obvious at the moment you generate the code. It only shows up months later, after the code is already printed on packaging, signage, or a menu that's expensive to replace.
What a static code does differently
Your entire payload — the literal URL text, the WIFI:... string, the vCard fields — sits inside the black-and-white pattern itself. There's nothing to host and nothing that requires an ongoing service to keep working. The tradeoff is real: you can't edit a static code's destination after it's printed, and there's no built-in scan-count analytics, since nothing is being tracked or routed through a server.
| Static | Dynamic | |
|---|---|---|
| Editable after printing | No | Yes |
| Needs a live server to work | No | Yes |
| Can expire or get paywalled | No | Often |
| Built-in scan tracking | No | Usually |
| Cost over time | Free forever | Often free at first, then paid |
When dynamic actually makes sense
Dynamic isn't a scam — it's a real tradeoff that's worth it in specific cases: marketing campaigns that need scan analytics, or a code that's physically hard to replace (engraved on a monument, molded into a product) where the destination genuinely might need to change later. If that's you, just go in with eyes open: pick a provider you actually trust to still exist in five years, and read their pricing page before you commit a printed design to it.
How to tell which kind you already have
Most phone camera apps show you the decoded text in a preview before opening it. Look at that preview:
- If it shows your actual destination directly — your domain, your Wi-Fi network name, your contact details — it's static.
- If it shows a short link on a domain that belongs to the QR tool you used (not you), it's dynamic, and that domain is now a permanent dependency.