Free QR Codes That Do Not Expire: What Can Actually Be Switched Off
Five hundred flyers went out in March. In May somebody scans one and gets a page saying the QR code has expired and can be reactivated by upgrading. The flyer is intact. The pattern on it is exactly what it was in March, and it still decodes to exactly the same string of characters. Nothing about the code expired.
Almost every generator on the market promises free QR codes that never expire. A good number of them do what the flyer just did. The promise is not usually a lie so much as a sentence carefully built so that the part that can be switched off is not the part being described.
Nothing in the format can expire
A QR symbol is a fixed arrangement of dark and light modules. The standard has no date field, no scan counter, no phone-home behaviour, no licence check. A camera reads the modules, reconstructs a string, and hands it to the operating system. That process involves nobody's server and asks nobody's permission, and the read sequence in how QR codes work will behave the same in twenty years as it does today.
So when someone says their codes never expire, they may be saying something perfectly true and completely empty. Of course the codes do not expire. The codes cannot expire. The question is what the code points at.
Three things can expire, and only one of them is the tool's fault
The redirect. A dynamic code does not encode your URL. It encodes a short address on somebody's domain, and a server at that address answers each scan with a redirect to wherever you configured. That is what makes the destination editable and the scans countable, and it means three things have to stay alive: the domain registration, the redirect service, and your account in good standing. Any one of them lapsing turns every printed copy into a dead end, which is the whole subject of what happens when a generator shuts down.
The destination. A static code encodes your URL directly, so it has nothing behind it to switch off. It still dies if you delete the page, restructure the site, or let the domain lapse. The code delivered the visitor faithfully to a 404. Do QR codes expire walks through this case by case.
The print. Sun, scuffing, a laminate gone yellow, a code printed too small for the distance people stand at. To the person holding the phone, a code that has degraded past reading is indistinguishable from one that was switched off. Plenty of reported expirations are this, and the blurry code checklist is where to start.
The thirty-second check
Do not take any generator's word for it, this one included. Decode the code and read what comes out.
- Point a phone camera at it and long-press the preview instead of tapping through, or upload the image file to the online scanner.
- Read the decoded string, character by character.
- Decide which of three cases you are in.
It is your own destination, verbatim. The code is static. Nobody can switch it off, and the only way it dies is if your page does.
It is a short link on the generator's domain. The code is dynamic. It works for exactly as long as that company keeps the redirect resolving and your account in whatever state their terms require.
It is your own domain, but a path nobody remembers creating. Somebody routed it through a shortener. Find out whose account that is before it becomes a surprise.
Do this on a printed copy before every run. It also catches typos, which kill more codes than expiration ever has.
The questions that get a straight answer
Since the claim itself is worthless, ask about the mechanism instead. In order of how much they matter:
- What exactly is encoded in the code? Not what the marketing page says, what the decoder shows.
- If it is their domain, what happens to the redirect when the trial ends? Some tools are explicit that trial codes stop resolving, and Scanova states as much.
- What happens if you stop paying after the trial? A 404, an upgrade page, or a working redirect through an interstitial you did not choose. ME-QR keeps free dynamic codes alive and pays for it with advertising in the scan path, which is a real answer and worth knowing in advance.
- Is there a scan cap, and what happens at the cap?
- Can you export the mapping of every short code to its destination, so a migration is a scheduling problem rather than a scramble?
- Can you put the codes on a domain you own?
A tool that answers all six plainly is a safer bet than one with a stronger promise.
What QRolling does, without dressing it up
There is no static generation here. No download hands you a file with the destination fixed inside the pattern, because the code is always a redirect we host. That is a deliberate choice with a cost attached, so here is the whole shape of it.
The file itself has no expiry. No watermark on the SVG or the PNG, nothing counting down inside the download, and no trial clock attached to the image. Building and styling a code are free and need no login at all. Downloading needs a free account, email or Google, no card. Editing the destination after something is printed, and reading scan counts, are on the paid plan.
And the part that follows from all of that: a QRolling code resolves for as long as its redirect is live, and that redirect is a service we run. That is the trade for an editable destination and scan analytics. We are not going to tell you our codes never expire, because a thing that is run is a thing that can stop, and the flyer in the first paragraph is what that sentence costs when somebody else says it.
If permanence matters more than editing for your job, the honest answer is a static file from a tool that issues one. QRCode Monkey and goQR.me both hand over a static file with no account, and goQR.me includes vector exports. Take the static file. The static code page sets out what you give up in exchange, and the dynamic code page sets out what you get back.
Which one your job actually needs
Permanence wins when the object outlives any plausible plan and cannot be reprinted cheaply:
- engraved plates, machine labels, memorial markers, anything cast or etched
- printed manuals inside packaging with two years of stock in a warehouse
- anything on a body, which is its own conversation in QR code tattoos
Editability wins when the destination is the thing most likely to change: campaigns, menus, event pages, seasonal offers, anything where you would rather repoint a link than reprint a run. The static versus dynamic comparison is the long version of that trade.
The hedge that ends the argument
Put the durable part in your own name and the question mostly stops mattering.
Register a domain, keep auto-renew on in a company account rather than somebody's personal one, and encode a short path on it: yourbrand.com/go/menu. Behind that path, either your own server's redirect rule, or a dynamic provider on a custom hostname you point at them with a CNAME. The printed code now contains an address you control. Change providers later and you re-create the paths and re-point DNS, and every code already in circulation carries on working.
Two conditions make it real rather than theoretical. The domain has to stay registered, and you have to keep an export of every path and its destination somewhere outside the provider's dashboard, because recreating the paths is the part that saves the codes. An audit of what is already printed is how you find out where you stand today.
Before the next print run: decode the code and read the string, decide whether this asset needs permanence or editability, and if it needs permanence, get a static file from a tool that issues one. If it needs editability, find out in writing what happens to the redirect the day you stop paying. That answer, not the word never, is the thing worth having.
