How to Change the Link in a QR Code After Printing

The answer depends on one decision made before printing

A QR code is a pattern of black and white squares that spells out a piece of text. When that text is the destination itself — https://example.com/spring — the pattern *is* the address, and changing the address means changing the pattern. That is a static code, and nothing can edit it after printing, on any platform, at any price.

A dynamic code spells out a short address belonging to the service that made it, and that address forwards to wherever you point it. The pattern never changes; what changes is the forwarding rule behind it. Repointing takes seconds and the printed material keeps working.

So the honest version of "how do I change the link in a QR code" is: if it is dynamic, in a few clicks; if it is static, you cannot, and the rest of this page is about what to do instead.

How to tell which one you are holding

You do not need the original file or the account that made it. Scan the code and read what the phone shows before you open it.

If the preview shows your own long address — the campaign page, the PDF, the full URL you supplied — it is static. If it shows a short address on some other domain, one you did not type, the code is dynamic and that short address is the redirect.

Two things confuse this test. A code made with a link shortener also shows a short address but is not dynamic in the useful sense — the pattern is fixed to that shortener and your control ends wherever that account does. And a very short branded domain can look like a destination when it is really a redirect. If you are unsure, open the code in a desktop browser and watch the address bar: a redirect resolves to a second address, a static code does not move.

A rougher signal: dense pattern, many small squares, usually a long address written directly — static. Sparse, chunky pattern — usually a short redirect, so likely dynamic.

Repointing a dynamic code

The change happens in the workspace that owns the code, not in the artwork. Nothing is reprinted and nothing is regenerated.

• Open the code in your workspace and change its destination to the new address.
• Save. The redirect updates immediately for every copy already printed, everywhere.
• Scan a physical copy — a real printed one, not the preview on screen — and confirm it lands where you meant.
• Test on mobile data rather than office Wi-Fi, in a private window, so you are not seeing a cached version of the old page.
• Note the date of the change against the campaign, so that a scan spike or drop afterwards has an explanation attached to it.

What you can still do when the code is static

The pattern cannot change, but the address it points at can sometimes be made to lead somewhere new. Whether any of this is available depends on who controls the destination.

If the address is on a domain you control, you own the answer: add a server-side redirect from the old path to the new one, and every scan of the printed code follows it. This is the reason to print addresses on your own domain rather than on a third party — a URL you control is repointable even inside a static code.

If the address is a page in a system you administer, keep the page and replace its contents rather than deleting it and creating a new one. A page that stays put with new information is a redirect by other means.

If it points at a shortener, someone else's file share, or a third-party page, you have no way in and the code is spent. Print a corrected sticker over it where the material allows, and treat the rest as a reprint.

Reprinting: what to change so it does not happen twice

If a reprint is unavoidable, spend it well. The same run that fixes the link is the only cheap chance to fix the reason.

Make the replacement dynamic, point it at an address on a domain you control, and split it into separate codes for anything you might later want to compare — each placement, each location, each market. Codes cost nothing to create and cannot be separated retroactively.

Then give the destination an owner. Most dead printed codes were not badly made; they pointed at a page that someone later moved, and the person who approved the artwork had changed jobs by the time anyone noticed.

What changes and what does not when you repoint

Repointing a dynamic code is a small change with a few consequences worth knowing in advance.

• The printed pattern is unaffected — the artwork, the stickers and the packaging all stay valid.
• The change is immediate and global; there is no per-copy rollout and no way to change one printed batch but not another that shares the code.
• Scan history stays with the code, so the numbers before and after the change sit in one series. Mark the switch date or the comparison will mislead you.
• A phone that scanned the code recently may still hold the old page in its cache, which is why the confirmation scan should happen on a device that has never opened it.
• The redirect is only as durable as the account behind it. Whoever can log in can point your printed material anywhere, so that access deserves the same care as access to your website.