Can you change a QR code after it is printed?

The ten-second test

Scan your own code with a phone and look at the address it offers before you open it. Most phone cameras show the destination as a banner or a preview rather than jumping straight there.

• If it shows your own address — your website, your booking page, your donation form — the destination is baked into the pattern. This is a static code, and it cannot be changed.
• If it shows a short address you do not recognise, something like qrco.de/…, qrtiger.io/…, flowcode.com/… or elysiu.me/…, the pattern holds a link belonging to whoever made the code, and the real destination sits behind it. This is a dynamic code, and it can be repointed.

If your camera opens the link immediately without showing you anything, look at the address bar the moment the page loads, or use any free QR reader app that displays the raw contents. What you are looking for is whether the code contains your address or somebody else’s.

If it is dynamic

Then the answer is yes, and it was always yes. Sign in to whoever made it, find the code, and change the destination. The printed pattern is untouched because the pattern never contained the destination in the first place — it contained a short link, and you have edited what that link resolves to. Everything already printed, stuck to a window or sitting in a box of leaflets picks up the change the next time somebody scans it.

Two things to check while you are in there. First, whether the change is immediate or cached — a code that is scanned heavily may take a few minutes to settle. Second, whether your account has a record of what the code used to point at. You will want that far more often than you expect, and not every service keeps one.

If it is static

Then nothing can change it. Not you, not the tool that generated it, not a support ticket. The destination is physically encoded in the arrangement of the squares, which is why a static code also cannot be switched off, expire, or stop working when somebody stops paying a subscription. It is the same property, read from both directions.

This is worth being clear about, because a great deal of advice online is vague enough to imply otherwise. If you made your code in Canva, Adobe Express, a word processor, or most free generators with no account, it is almost certainly static. That was a reasonable thing to make. It is only a problem if the destination needs to move.

What you can actually do, in rough order of cost:

• Redirect at the destination instead. If the code points at a page on a site you control, you do not need to touch the code — you need the old address to forward to the new one. Any web host or CMS can do this, and it is the cheapest fix by a distance. It only fails if the address in the code was on a service you no longer control.
• Keep the old page alive as a signpost. If you cannot redirect, put a page at the old address that explains where things have moved. Ugly, but a scanned code that explains itself is much better than a 404.
• Reprint, and make the replacement dynamic. If neither works, you are reprinting. The thing to avoid is reprinting a second static code and being back here in a year.

The trade you are actually making

Every write-up of this treats dynamic as the upgrade and static as the beginner’s mistake. That is not quite right, and getting it wrong is expensive in a specific way.

A static code cannot be corrected, but it also cannot be taken away from you. There is no account, no subscription and no company that has to still exist in five years. For a phone number, a Wi-Fi password, or a homepage you will never move, it is genuinely the better choice, and anybody selling you a subscription for it is selling you something you do not need.

A dynamic code can be corrected, and the price is that it now depends on somebody answering that short link for as long as the printed material exists. That dependency is the entire risk, and it is why the question that matters before a print run is not “can I change it later” but what the provider does when you stop paying. We checked every major vendor’s own wording on that, and the answers vary more than you would hope.

The failure people actually run into is choosing static out of a fear of being switched off, and then discovering the destination has to move. That trades one irreversible problem for another. The fear is well founded; static is just the wrong answer to it.

Before the next print run

Whichever kind you end up with, the artwork itself is a separate way for this to go wrong, and it goes wrong after the money is spent. A code that scans on a screen can fail on paper because it was printed too small, because the quiet border was trimmed, or because a logo was dropped on top of it without raising the error correction to compensate. The print guide covers the numbers, including the minimum size in millimetres.

And if the code you are holding has already stopped working, that is a different problem with a different fix: start here instead.