Static vs dynamic QR codes: which one you actually need

Choose a static code when the destination is settled and must keep working for years. Choose a dynamic code only when the destination genuinely has to change after printing — and treat the redirect service as a dependency you will have to maintain for as long as the code is in the wild. Everything else is fashion.

The distinction matters because it is invisible on the printed page. A poster looks identical whether it holds a self-contained address or a pointer to somebody else's redirector, and the second kind quietly stops working when a subscription ends. Here is how the two differ underneath, and how to pick.

What a static QR code really is

A static code encodes your content directly into the module matrix. This generator takes the bytes of your text, picks the smallest version that fits, applies the Reed–Solomon error correction and draws the result. There is no server in the loop because there is nothing to look up: the scanner decodes the characters and acts on them.

Three consequences follow, and they are all good ones for a printed asset:

  • No moving parts. A static code does not need DNS, a redirect endpoint, an account or a monthly fee to keep decoding. It behaves the same in ten years, offline, in a basement.
  • Verifiable. You can scan your own code, read the decoded text, and know exactly what every future scanner will see. With a redirect you only ever verify the first hop.
  • Private. A WiFi or contact code puts the actual value on the page. Nothing about the scan — time, place, device — reaches a third party, because nothing is contacted.

The limit is obvious too: the bytes are baked in. Change the URL, the password or the phone number and the printed code is wrong. There is no edit button on a printed poster.

What a dynamic code adds, and what it takes away

A dynamic code encodes a short URL on the provider's domain. The scanner opens that URL, the provider records the hit and forwards the browser to a destination stored in their database. Because the destination lives in a database rather than the matrix, it can be changed after printing.

That is a real capability. A menu whose prices change seasonally, a per-branch landing page, a campaign that needs UTM parameters — all of these are easier with an editable target. The trade is a dependency chain: the provider must stay in business, keep its domain registered, keep the redirect service online, and keep honouring the plan you bought.

When any link in that chain breaks, the code becomes a decorative square. The paper is intact, the print quality is perfect, and the phone opens an error page. This failure mode is common enough that it is the first thing worth checking when someone says "our QR codes stopped working" — see the five failure modes.

The comparison that actually decides it

QuestionStaticDynamic
Where the destination livesInside the matrixIn the provider's database
Editable after printingNoYes
Survives the provider shutting downYesNo
Scan analyticsNone, unless you read your own server logsStandard
Works with the phone offlineDecodes offline; the link still needs a networkNeeds the redirector before it can even resolve
Recurring costZeroUsually a subscription
Data in the symbolWhole payload, so codes get denserOnly a short URL
Privacy of the encoded valueOnly what you chose to publishEvery scan is visible to the provider

Where static is the only defensible choice

Some payloads have no business passing through a third party at all.

WiFi credentials

A WiFi code contains the network password. Routing it through a redirect would either break the join entirely — phones expect the WIFI: string, not a URL — or force a landing page that leaks the password to anyone who reads the page source. Generate it statically, print it, done.

Contact cards

A vCard code is read by the camera app and stored in the address book locally. A redirect version would need the phone to fetch the record from a server before adding it, which is slower and puts a copy of your contact details on someone else's disk.

Permanent signage

A plaque, a machine label, a door sign or a product package that will be in service for a decade should not depend on a company that may not exist in a decade. Static codes age perfectly; redirects age like milk.

Anything you cannot reprint

Engraved plates, printed circuit boards, cast metal, book interiors, tattoos. If re-cutting the artwork costs more than the flexibility is worth, encode the final destination and move on.

Where dynamic earns its cost

Being honest about the trade means admitting the cases where the subscription is worth paying.

  • Large print runs tied to a campaign. Ten thousand flyers with a destination you might need to correct next week is a strong argument for an editable target.
  • Attribution. If you need to know how many scans came from the poster in the window versus the one in the lift, only a redirect gives you that number.
  • Content that changes on a schedule. Seasonal menus, event schedules, price lists.
  • Codes that must stay short. A long tracking URL with parameters can push a symbol to a higher version and a denser grid; a short redirect keeps the module count down, which helps at small print sizes.

How to tell which kind you are looking at

Scan the code with any camera app and read the decoded text before it opens. A static code shows the full address, for example https://example.com/qr/spring-menu. A dynamic code shows a short domain you do not recognise, typically three to six characters long, that redirects when opened. If the decoded text and the address bar after loading differ, you are looking at a redirect.

That same check catches the most expensive mistake in this area: a code that was static when it was proofed and dynamic when it was printed, or the reverse, because two files got mixed up in a design handoff.

Switching later costs more than deciding now

You can go from dynamic to static at any time: resolve the redirect, encode the final URL, print the new code. You cannot go from static to dynamic without reprinting, because the matrix itself would have to change.

So the decision is asymmetric. Print static when you are confident in the destination; print dynamic when you are not, and accept the maintenance. Do not print dynamic because it sounds more modern — an unresolved redirect is strictly worse than a fixed URL that still points somewhere useful.

Frequently asked questions

Does a dynamic code die if the provider disappears?

Yes. The matrix only contains the provider's short URL, so when their domain or redirect service goes away the scan lands on an error. There is no way to recover the destination from the printed symbol, because it was never in there.

Can I edit a static code after printing?

No. The content is part of the pattern. Editing means generating a new symbol and replacing the printed copy.

Can I get scan counts with a static code?

Only indirectly. If the code points at your own site you can count requests in your server logs or analytics, but you are counting all traffic to that URL, not scans specifically, and you get nothing for codes that never touch your server.

Build a static code in the generator — text, WiFi, vCard or SMS, with the exact payload shown so you can confirm what is inside the symbol before you print it. If you are unsure how much data fits, read the capacity and error-correction guide first.

Written by the QRQuick team. Last updated November 19, 2026.