Do QR codes expire, and what happens when they do

A printed code has two ways to stop working, and only one of them is about the paper. What providers actually do when you stop paying.

5 min read
  • qr-codes
  • printing

A poster goes into a window in March. Somebody scans it in November and gets nothing at all. The ink has not changed, nobody has touched the paper, and the phone is working perfectly well on everything else.

Whether that code still worked was decided by somebody else entirely, months earlier, in an account nobody was looking at. It is worth understanding before anything goes to a printer, because the answer depends on which of two quite different things you printed. They look identical on the paper.

Only one kind of code can expire

A QR code is a grid that holds text. In the simple case the text is the destination itself: the address is written into the squares, exactly as the format intends, and reading the code is the whole job. Nothing is looked up, no server is asked, and nobody is asked for permission.

That kind cannot expire, because there is nothing to switch off. It keeps working for as long as the thing it points at does, so a code holding your own web address outlives the company that printed the poster. It fails only on the day that page fails, which is a problem you already know how to think about.

The other kind holds a short address belonging to a provider, and that address redirects to wherever you have said. This is what people mean by an editable or dynamic code, and it is the reason you can print something in March and change where it goes in June. It is genuinely useful, and it is why the category exists.

The indirection that lets you change the destination is the same indirection that lets somebody switch it off. You cannot have the first without the second. It is not a flaw in any particular product, it is what the arrangement is, and every provider in the market has it. We make Tessera, so we sell one of the things this article is about, and our editable codes carry the same dependency as everybody else's.

What providers actually do

Most of them stop your code, and they are not hiding it so much as filing it where nobody reads before buying. Scanova says so on its own pricing page: “Your Dynamic QR Code will stop working once the free trial ends. You will need a subscription to keep Dynamic QR Codes functional.” The same page is equally clear about the other family, saying a static code “will work forever without any ongoing cost”.

QR TIGER's frequently asked questions go further, and the second half is the part worth reading twice. On the code itself: “If your plan expires, it will stop working.” On the record of it afterwards: “we will retain your data for a maximum period of 1 year”, after which “it is possible that we remove all data from your account.” So there are two clocks rather than one.

The first clock stops your printed code working. The second decides how long you have to change your mind before the destination you carefully configured is gone as well, and only the first is usually mentioned while you are deciding what to buy. Those quotations were read in August 2026 and providers change terms without telling anybody, so treat them as the shape of the thing rather than as a promise about a company you are about to pay.

The question to ask before you print

Pricing pages are written to tell you what you get. This question is about what you lose, so it tends to live somewhere quieter. Ask a provider what happens to codes you have already printed if you stop paying, and ask where that is written down.

A company confident in its answer will point you at a page, because it has one. A company that will answer only in a chat window has told you something as well, and it is worth hearing. Ask also how long your data is kept after a lapse, because reactivating an account only helps while the destination still exists.

One more question separates the careful providers from the rest: does the code keep working during a downgrade, as opposed to a cancellation? Those are often different policies, and usually only one of them is documented. None of this applies to a static code, which is the quiet argument for using one wherever you can.

Choosing, with the cost in view

Print a static code when the destination is settled and you want the paper to outlive the arrangement. A menu pointing at your own website, a Wi-Fi password on a card, a phone number on a van: none of these need a provider sitting between the square and the answer. The code is then exactly as permanent as the thing it names.

Print an editable code when you genuinely need to change where it goes after printing, and go in knowing you have taken on a dependency. That is a real trade rather than a trap. For a campaign whose destination will move twice before Christmas it is plainly the right one, and the dependency is simply the price of the thing that makes it work.

What turns the trade into a trap is only ever finding out late. A printer will not ask, the code will not look any different, and the first evidence usually arrives as somebody telling you their phone did nothing.

A checklist before it goes to print

  • Decide whether the destination can ever change. If it cannot, print a static code and remove the question entirely.
  • If it can change, find the provider's written answer on what happens when you stop paying, before you pay anything.
  • Check how long they keep your data after a lapse, not only whether the code stops.
  • Point editable codes at a destination you control, so the worst case is re-pointing rather than reprinting.
  • Keep a note of what every printed code should resolve to. A code nobody can identify is a code nobody dares change.

Everything in a QR code is decided once and then set in ink. The part that is not in the ink is the part worth choosing carefully, because it is the only part anybody can take away while the poster is still on the wall.