Do static QR codes expire?

No. The destination is encoded in the pattern, so there is nothing to expire and no server involved. A static code printed today will scan identically in twenty years. Any site telling you its static codes expire has made that a business decision, not a technical one.

Can I convert a printed dynamic code to a static one?

Not the printed code — its pattern encodes the vendor's short link, and that cannot be changed without reprinting. You can generate a new static code with the final destination and reprint. This is the trap: the switching cost is a reprint of everything already in the world.

Can I track scans without a subscription?

Yes, partly. Point a static code at a URL on your own domain with campaign parameters, and your own analytics or server logs record the visits. You lose per-scan detail such as device and precise timing, but you get placement-level measurement with nothing to renew.

Which type is more reliable at scanning?

Static, in poor conditions. It resolves with no network request at all, while a dynamic code must reach the vendor's server first. Dynamic codes can be visually simpler when the real URL is long, which helps in poor light or at distance — so the answer depends on whether your constraint is connectivity or print size.

What happens if the QR vendor goes out of business?

Every dynamic code they host stops resolving, and there is no recovery short of reprinting. Using a vendor that supports your own custom domain for the short links is the practical mitigation, since you can repoint the domain elsewhere.

Static vs dynamic QR codes

A static QR code contains the destination itself: scan it and your phone reads the URL, the WiFi credentials, or the contact details directly out of the pattern. A dynamic QR code contains a short link to a vendor's server, which redirects to wherever you have currently pointed it. That single difference produces every other difference between them. Dynamic codes can be edited after printing and can count scans, which is genuinely useful. They also depend on a third party staying in business, keeping that redirect alive, and on you continuing to pay — and a printed dynamic code whose subscription lapsed is a dead code on a permanent object. Neither is better; they solve different problems, and the wrong one is expensive in a way that is not obvious until later.

The mechanical difference

Scan a static QR code for this site and your phone reads the address out of the pattern itself. Nothing is contacted to resolve it; the data is in the ink. Scan a dynamic one and your phone reads something like qr-vendor.example/a7Bx2, requests it, and the vendor's server responds with a redirect to the real destination.

That indirection is the entire feature set. Because the printed pattern encodes only the short link, you can change what it points to without reprinting. Because every scan passes through the vendor's server, it can be counted, timed and geolocated.

It is also the entire risk. The printed pattern is now a pointer to somebody else's infrastructure, and its usefulness lasts exactly as long as that infrastructure and your relationship with it.

What dynamic codes genuinely give you

Editability after printing. This is the real value. A code on a restaurant menu stand can point at this season's menu; a code on packaging printed a year in advance can point at a support page that has since moved. Anything printed in volume, or fixed to something permanent, benefits from the destination not being set in ink.

Scan analytics. Counts, times, rough locations, device types. If you are running a campaign across several placements and need to know which poster worked, static codes cannot tell you — though pointing several static codes at different URLs with tracking parameters gets you most of the way for free.

A smaller, more reliable pattern. A short redirect link encodes into fewer modules than a long URL with campaign parameters, producing a visually simpler code that scans faster, from further away, and survives more damage. For a long destination URL printed small, this is a real practical gain rather than a marketing one.

What you give up

The code dies with the subscription. This is the one that catches people. Stop paying, or exceed a scan quota on a free tier, and every printed code stops working — often redirecting to the vendor's upgrade page, which is worse than a plain failure because customers see it. Codes on business cards, packaging, signage and vehicle livery outlive most subscriptions.

The vendor becomes a dependency. If they have an outage, your codes are down. If they are acquired or shut down, your codes are gone. Many QR vendors are small businesses, and a code printed on ten thousand product boxes has a longer expected life than the average startup.

Scanning gets slower and more fragile. Every scan makes a network request before reaching the destination. In a car park, a basement, a trade hall with congested WiFi, or anywhere with poor signal, the extra hop is where the scan fails. A static code carrying WiFi credentials works with no connectivity at all, which is precisely when you need it.

Scan data goes to a third party. Your customers' scan events are logged by a company they have never heard of, which may matter for your privacy notice.

What is actually being sold

Worth being clear about the economics, because it shapes the advice you find elsewhere. Generating a QR code is a solved problem — the encoding is a published standard and the libraries are free and open source. Nobody can build a subscription business on generating patterns.

What is being sold is the redirect service and the analytics dashboard: hosting a short link, logging scans, and letting you change the target. That is a real service with real running costs. But it explains why so many "QR generator" sites push hard toward dynamic codes, put static ones behind a smaller button, and sometimes make static codes expire — which is a business decision, not a technical constraint. A static QR code cannot expire. The pattern is the data.

Choosing

Use static when the destination will not change: WiFi credentials, contact details on a business card, a link to your homepage, a permanent product page, anything on a museum label or a plaque. Use it whenever the code needs to work without connectivity, and whenever the printed object will outlive your certainty about paying a subscription.

Use dynamic when the destination genuinely will change, when you are running a campaign that needs per-placement measurement, or when the URL is long and the printed code must be small. Then treat it as infrastructure: know what happens when the subscription lapses, whether you can export or redirect your codes if you leave, and whether the vendor offers a custom domain — which is the one feature that makes a dynamic code portable, because you can repoint the domain if the vendor disappears.

A reasonable middle path for measurement without lock-in: a static code pointing at a URL on your own domain, with a redirect you control. You get editability and analytics from your own server logs, and nothing expires but your own hosting.

Last updated: 2026-08-07

Generate a static QR code

Made in your browser, encoded in the pattern, no account and nothing to expire.

Frequently asked questions

Do static QR codes expire?: No. The destination is encoded in the pattern, so there is nothing to expire and no server involved. A static code printed today will scan identically in twenty years. Any site telling you its static codes expire has made that a business decision, not a technical one.
Can I convert a printed dynamic code to a static one?: Not the printed code — its pattern encodes the vendor's short link, and that cannot be changed without reprinting. You can generate a new static code with the final destination and reprint. This is the trap: the switching cost is a reprint of everything already in the world.
Can I track scans without a subscription?: Yes, partly. Point a static code at a URL on your own domain with campaign parameters, and your own analytics or server logs record the visits. You lose per-scan detail such as device and precise timing, but you get placement-level measurement with nothing to renew.
Which type is more reliable at scanning?: Static, in poor conditions. It resolves with no network request at all, while a dynamic code must reach the vendor's server first. Dynamic codes can be visually simpler when the real URL is long, which helps in poor light or at distance — so the answer depends on whether your constraint is connectivity or print size.
What happens if the QR vendor goes out of business?: Every dynamic code they host stops resolving, and there is no recovery short of reprinting. Using a vendor that supports your own custom domain for the short links is the practical mitigation, since you can repoint the domain elsewhere.