Why Your Dynamic QR Code Won't Redirect (and How to Fix It)

Quick answer

A dynamic QR code that won't redirect is almost always failing at one of three points: the redirect service the code depends on, the destination URL, or the app doing the scanning. The code itself is usually fine — something downstream of it changed. That's different from a code that won't scan at all, which is a physical-readability issue. Here are the four causes, in the order they're fastest to rule out.

How a dynamic QR code actually redirects

A dynamic QR code — as Wikipedia describes it — doesn't encode your final destination directly. It encodes a short redirect URL that points to a service, and that service looks up the destination you configured and forwards the scanner there. This indirection is the whole point — it lets you edit where a code points after it's already printed on a menu, sign, or product label.

The catch is a dependency chain. A static QR code has no server in the loop and decodes to the same string forever. A dynamic code has one or two extra links in front of it — the redirect service, and sometimes a tracking layer — and either can break even when the printed code hasn't changed at all.

Cause 1 — the redirect service lapsed

Because the lookup runs on someone's server, dynamic codes typically require an active account with a provider. Let that subscription lapse, or have the provider shut the account down, and every code tied to it stops resolving at once — this is the subscription trap that catches people who set up a code years ago and forgot the billing behind it. To the scanner, it looks like a timeout or a blunt "this link has expired" message, even though the code itself hasn't degraded one bit.

Cause 2 — the destination changed or the redirect chain broke

Sometimes the redirect step works fine and the failure is one hop further down: the destination URL was edited, taken down, or the wrong field got changed. Scanning resolves the redirect but the final page 404s — fixed by checking the destination, not the provider's uptime. Redirect chains stacking too many hops (shortener → tracking layer → real page) can also time out on their own, producing the same symptom as a dead destination.

Cause 3 — the scanner app is mangling the URL

Occasionally the code and the redirect service both work, and the problem is the scanning app itself. In 2021, Google's Camera app had a bug on Android 12 that silently rewrote scanned URLs before opening them — inserting extra dots into certain country-code domains, truncating top-level domains like .travel or .cat to two letters, and mangling subdomains containing numbers. A code pointing to a valid address would fail to redirect purely because of what the scanner did to the link on the way there. If a code won't redirect on one phone, try a second app, or a different phone, before assuming the code or destination is broken.

Cause 4 — HTTP-vs-HTTPS mismatch

An http:// destination can get flagged or silently blocked by a phone's browser before the page loads. That reads as "the QR code doesn't do anything." Fix it on the destination side: always point a dynamic code at https://, not http://.

Doing this on QRDock specifically

If a code you manage on QRDock stops redirecting, start in your dashboard: confirm the destination loads on its own in a browser, then check scan analytics to see whether scans reach the redirect step at all. QRDock's URL safety check reviews destinations for known phishing patterns as a best-effort layer, not a guarantee — it's still worth confirming a destination loads correctly yourself after any edit.

Frequently Asked Questions

Why does my QR code say the link has expired?

That message comes from the redirect service, not the printed code. Most dynamic QR platforms run redirects on a subscription — if the plan lapses or the account is deleted, every code that depends on it stops resolving, even though the pattern hasn't changed.

Can a QR code stop working even if I never changed the destination URL?

Yes. The redirect platform's servers can go down, the destination site can move or go offline, or the scanning app can mangle the URL before requesting it. Test the same code with a second scanner app to rule out the last one.

How is a static QR code different when it comes to redirect failures?

A static QR code has no redirect step — it encodes the final URL directly, so there's no subscription or server dependency to fail. The tradeoff: you can't fix a typo or update the destination after printing; you'd need a new code.

What's the fastest way to tell if the problem is the code, the redirect, or the destination page?

Open the redirect URL directly in a browser rather than through the QR code. If it loads fine, the problem is likely the scanner app on your phone. If it times out or 404s, check your QR platform's dashboard next.

Conclusion

A dynamic QR code that won't redirect almost never means the code is damaged — it means something in the chain behind it changed: the service lost its subscription, the destination moved, or the scanner mishandled the link. Work through the four causes above and you'll usually isolate which one it is within a minute or two. If the code isn't scanning at all, that's a separate, physical-readability problem — see the five-minute troubleshooting checklist instead.