Why Your QR Code Stopped Working?

When a QR code stopped working, the code itself may be the least interesting part of the problem. A camera can read the pattern perfectly while the link behind it returns an error, sends visitors to the wrong page, or depends on a service that is no longer available.

Start with a simple question: does the code fail to scan, or does it scan and then fail to open? That distinction separates a printing problem from a destination or redirect problem. This guide walks through both, so you can diagnose the failure before reprinting every sign, package, or flyer.

Start here: does it fail on every phone?#

Scan the QR code with at least two phones, ideally using different camera apps. Try the code in good light and from a normal distance. If one phone fails but another opens the link, the code may be marginal rather than completely broken. Camera focus, glare, and browser settings can affect the result.

If every phone reads the same URL, copy that URL instead of repeatedly scanning. Open it directly, then look at the address bar after the page loads. A changed final URL, an error page, or a long pause tells you to investigate the link infrastructure.

Physical causes: size, contrast, quiet zone, and damage#

A QR code needs enough detail for a camera to distinguish its modules. A code printed too small, stretched by a layout tool, or placed where the camera cannot focus may fail even when the encoded URL is healthy.

Check the basics: strong contrast between the code and its background, a clear margin around all four sides, and a size appropriate to the distance from which people will scan. Avoid placing a logo or decorative element over too much of the pattern. If you add a logo, preserve enough error correction for the code to remain readable.

Printed materials introduce other failure modes. Scratches, folds, water, ink spread, reflections from packaging, and low-quality photocopies can obscure modules. Compare the physical code with the original export. If the original scans but the printed copy does not, fix the artwork or print production before touching the URL.

The destination moved or was deleted#

A static QR code stores a URL. It does not know that your website later changed its page structure. If the encoded address now returns a 404, points to a deleted campaign page, or lands on a generic homepage, the code can still be scanned while the visitor experience is broken.

Restore the old path when possible, or create a redirect from the old address to the closest current page. Check the exact path, capitalization, query string, and protocol. Sending every retired QR link to the homepage may remove the immediate error, but it also loses the context that the visitor expected.

The redirect service stopped resolving#

Many campaign QR codes use a short URL or redirect instead of encoding the final destination. That gives the owner a chance to edit the destination later, but it adds another dependency. The redirect domain must resolve, the redirect record must exist, and the service must return a usable response.

Use a redirect checker to inspect the response. Look for DNS errors, certificate errors, redirect loops, a missing record, or a final status that blocks mobile visitors. Test the link outside your office network too. A local cache or allowlist can hide a failure that customers see immediately.

Your plan lapsed and the code went with it#

Hosted dynamic QR services often keep the redirect active as part of a subscription. If the account is cancelled, the payment fails, or the provider shuts down, the printed code may stop working even though the graphic is undamaged. The same risk applies when the redirect uses a domain that expires or is transferred without its DNS being restored.

This is why ownership matters. A QR graphic is only a container for data. The durable part of the setup is the domain and redirect path your team can keep renewing, inspect, and update. An own-domain QR is not automatically secure, but it gives visitors a recognizable link and gives the business a clearer place to troubleshoot.

Preventing the infrastructure failures#

Before a code goes to print, scan the production file on several phones and record the exact URL it contains. Open the link on mobile data, follow the complete redirect chain, and confirm that the final page is the one the printed material promises.

For campaigns that may change, use an editable QR redirect rather than encoding a temporary destination directly. Keep an owner and renewal date for the domain, document the destination, and check important codes after launch. Monitoring is useful only when someone knows which failure needs attention and can update the redirect.

A central redirect management workflow also makes handoffs safer. Keep the source path, current destination, campaign owner, and status together. When a page moves, update the redirect record and test the printed code again instead of asking a designer to recreate every asset.

A quick diagnosis checklist#

• Scan the code on two or more phones and note whether it fails before or after reading the URL.
• Inspect the printed size, contrast, quiet zone, glare, folds, scratches, and logo coverage.
• Open the scanned URL directly and check the full redirect chain, DNS, certificate, and final path.
• Confirm that the destination page, redirect record, domain, and hosted service account still exist.
• Repair the destination when you control the redirect. Replace the code only when the encoded URL itself cannot be changed.

Conclusion#

A QR code stopped working for one of two broad reasons: the camera cannot read the physical pattern, or the link behind it no longer works. Test both layers before you reprint anything. If the code points to a redirect you control, you can often repair the visitor journey by fixing the destination, domain, or redirect record while leaving the printed code in place.