Static vs dynamic QR codes: which one you actually need
Dynamic codes let you edit the destination and count scans. Static codes cost nothing and cannot be switched off. Here is how to choose without paying for something you will not use.
Every QR generator that charges money is selling you dynamic codes. Some of them need it. Most people do not — and the ones who do usually should not rent it from a QR company.
The mechanical difference
Encode https://mysite.com/summer-campaign as a static code and the pattern contains those 38 characters. A phone reads the pattern, decodes the text, opens it. Done.
Encode the same thing as a dynamic code and the pattern contains something like https://qr-provider.io/x7Bq. The phone opens *that*, the provider's server looks up where it should go, and issues a redirect to your real page.
Everything that follows comes from this one difference.
What the redirect buys you
Editable destination. Change where the code points without reprinting. If 5,000 flyers are already in the world and the campaign URL changes, this is worth real money.
Scan analytics. Because every scan touches the provider's server, they can report counts, times, locations, and device types. A static code cannot do this — nothing is watching.
A simpler pattern. A short redirect URL encodes into fewer modules than a long link. At small print sizes that genuinely matters: bigger squares scan more reliably.
Those three are real. Anyone who tells you dynamic codes are pure upsell is wrong.
What the redirect costs you
A dependency you do not control. A company now sits between your customer and your content. If it raises prices, changes its free tier, gets acquired or shuts down, your printed codes are affected — and you find out from a customer, not from an email.
A recurring bill. Dynamic codes are almost always subscription-based, because the provider is paying for a server that must answer every scan, forever.
A slower scan. Every scan is two round trips instead of one. Barely noticeable on good mobile data, noticeable in a basement restaurant with one bar of signal.
Privacy exposure. The provider sees who scans your codes, where, and when. For a marketing campaign that is a feature. For a payment code or an internal asset tag, it is a liability.
The decision, honestly
| Situation | Use | Why |
|---|---|---|
| --- | --- | --- |
| WiFi password on a table card | Static | Nothing to edit, and no server should ever hold a password |
| Business card | Static | The card outlives any subscription you take out today |
| Payment: PIX, UPI, crypto | Static, always | Never put a third party between a payer and your account |
| Restaurant menu | Static, pointing at a stable file URL | Replace the file, keep the filename |
| Product packaging, years on shelf | Static, pointing at a URL you own | The code must outlive any vendor |
| Print campaign that may need redirecting | Dynamic, or self-hosted redirect | Genuine need for editability |
| Client work where you must prove scan volume | Dynamic | The analytics require a server |
| A/B testing two destinations | Dynamic | No other way to do it |
The middle path most people miss
You can have editability and independence: encode a URL on a domain you own, and control the redirect yourself.
Print yoursite.com/menu. Today it redirects to a PDF on Google Drive. Next year to a page on your new site. The printed code never changes, no subscription exists, and no third party can switch it off.
Every hosting service does redirects in a couple of lines of configuration. On Firebase Hosting it is three lines in firebase.json. On Netlify or Vercel, one line in a config file.
You lose the ready-made analytics dashboard — but your server logs already have the same data, and any analytics tool will chart it.
This is what the QR industry does not advertise: the useful half of "dynamic" is just a redirect, and you can own the redirect.
When dynamic really is right
Do not read the above as "never pay". Dynamic codes earn their price when:
- You are running campaigns for clients who need reported scan numbers
- You manage dozens or hundreds of codes and need them in one dashboard
- You need per-code analytics without building any infrastructure
- Someone else on the team must be able to change destinations without touching code
If two or more of those describe you, a dynamic provider is a reasonable business expense. If none do, you are paying a subscription to avoid writing one redirect rule.
How to tell what you already have
Scan your own code with our QR reader and read the decoded text, not the page it opens.
Your actual content? Static, permanent, yours. A short link on a domain you do not recognise? Dynamic, and its lifespan is that company's lifespan.
Do this before any print run. It takes ten seconds and it is the single check that most often saves a reprint.
In short
- Static: free, permanent, no dependency, no analytics, cannot be edited
- Dynamic: editable and trackable, for a fee, forever, from a company you do not control
- For payments and WiFi, static is the only defensible choice
- For everything printed at volume, static aimed at your own URL gives you both
Every code from QRWisp is static and free — including vector SVG, PDF and EPS, which is precisely the point where most generators start asking for a card.