Anyone about to print a code and unsure which kind
How to choose between a static and a dynamic QR code
The two look identical and scan identically. The difference is where the destination is stored.
A static QR code encodes the destination directly in the pattern. The squares literally spell out your URL, so nothing is looked up at scan time and nothing can be changed afterward without printing a new code.
A dynamic QR code encodes a short link instead. The pattern spells out something like rrte.link/abc, and where that resolves is a setting you control. Repoint it and every copy already printed follows on the next scan.
- 1
Ask one question: will this destination ever change?
That is the whole decision. Not scan volume, not print size, not whether you need it to look good. If the answer is no — and for a WiFi password or a phone number it genuinely is no — use a static code. If the answer is yes, or you are not sure, the cost of guessing wrong is a reprint.
- 2
Use static when the data IS the destination
A WiFi network, a vCard, a plain phone number, an email address, a Bitcoin address, a block of text. These encode the payload itself, so there is nothing to look up and nothing to break. They work with no account, no vendor and no internet lookup, and they keep working if every QR company on earth shuts down. That last property is worth more than most of the features sold against it.
- 3
Use dynamic when the code outlives the destination
Anything printed on something you cannot cheaply reprint: packaging, menus, signage, vehicle livery, business cards, direct mail. Print runs outlive campaigns, URLs, product pages and sometimes companies. A dynamic code is how you keep the printed object useful after the thing it pointed at moves.
- 4
Know what dynamic actually costs you
A dynamic code depends on a resolver staying up and staying yours. That is a real dependency, and it is the reason to check two things before committing a print run: whether destination edits are metered, and whether the code keeps resolving if you stop paying. Both are ordinary in this category and both turn a printed asset into a subscription.
- 5
If you are printing at volume, put it on a domain you own
A dynamic code on a vendor's domain is only as permanent as your relationship with that vendor. A dynamic code on your own domain is permanent regardless: if you ever need to move, you repoint DNS and every printed code keeps working. For a print run measured in thousands, this is the difference between an asset and a rental.
What this will not do
- Dynamic codes are not more scannable. Both types scan identically on every phone made since about 2017 — the camera does not know or care which it is reading.
- Static codes cannot be tracked. There is no lookup at scan time, so there is no scan to record. If someone offers you analytics on a static code, something else is going on.
- A dynamic code is denser than a static one only when the original URL was short. For a long URL the dynamic version is usually the simpler pattern, because a short link is fewer characters.
- Converting a printed static code to dynamic is not possible. The destination is in the ink. This is the one decision you cannot revisit later, which is why it is worth two minutes now.
Tools used in this guide
Questions
Other guides
- How to put a QR code on a menu you can update without reprintingOne code on the table tent that opens lunch at eleven and dinner at five, without a second print run.
- How to A/B test a printed QR campaign and measure real conversionsSplit traffic from a single print run between two destinations, and match the sale back to the scan that caused it.
- How to send iPhone and Android users to different app stores from one QR codeOne square on the poster that opens the right store for whoever scanned it, decided at the moment of the scan.
- How to get packaging ready for GS1 Sunrise 2027 with a Digital Link QR codeRegister a GTIN, point it at the destinations retailers and shoppers each need, and test it before artwork goes to print.
- What is a GS1 Digital Link? The web address inside the new product QR codesThe definitional companion to the packaging guide: what the standard actually is, how a scan resolves, and what a resolver does.
- How to password-protect, expire, or scan-limit a QR codeFor codes on things that stop being valid: a door ticket, a limited run, a document that should not outlive its meeting.
- How to make a digital business card you can update after printingOne code on the card that opens your details as they are today, not as they were at the print shop.
- How to put a QR code on a yard sign that outlives the listingThe sign is the durable object, not the listing. Give each sign a code you repoint as properties come and go.
- How to run QR codes across an event — badges, booths and sessionsCodes for the whole run of an event: the save-the-date, the badge back, the booth banner, and the swap to recordings after everyone goes home.
- Leaving Bitly: what moves, and what stays deadThe destinations come with you. The printed bit.ly square does not. Import creates new addresses; it cannot take over the old ones.
- Running Bitly and reRoute together until the print run turns overKeep Bitly live until the print turns over. New rrte.link on the next run. Drain the codes people actually scan.
- How big to print a QR codeSize follows scan distance, with a 2 cm floor for close range. Quiet zone and contrast matter as much as the millimetres.