You printed the thing. You stuck it on the wall, the table, the packaging, whatever. It worked fine for weeks. And now someone tells you it's broken, or worse, you scan it yourself and get a blank screen. Cool.
The instinct is to blame yourself, or your phone, or "QR codes in general." But most of the time, a dead QR code comes down to one of five specific problems. And most of them have nothing to do with anything you did.
The destination disappeared
This is the most common reason by a wide margin. The QR code itself is fine. It's doing exactly what it was built to do: sending people to a URL. But the page at that URL is gone.
Maybe you deleted a Google Drive file. Maybe your Linktree got deactivated. Maybe your website host expired and nobody noticed for two weeks. Maybe you just reorganized your site and the old link now 404s. The code scans perfectly. It just has nowhere useful to send people.
The fix is usually boring: check the URL your code points to. Open it in a browser. If the page doesn't load for you, it won't load for anyone else either. If you're using a dynamic QR code, you can update the destination without reprinting. If it's a static code (the kind where the URL is permanently baked into the pattern itself), you're reprinting.
Your QR code service killed it
This is the one that makes people angriest, and honestly, it should. A lot of QR code generators route scans through their own servers. That means if you cancel your subscription, or if the company shuts down, or if they just decide free codes expire after 30 days, your printed code dies.
You didn't change anything. Your destination page is still live. But the middleman disappeared, so the chain breaks.
This happens more often than you'd think. Some services deactivate codes the moment a trial ends. Others quietly expire free codes after a set period without warning. It's a business model that depends on you not noticing until it's too late, at which point you either pay up or reprint everything.
DSQR's Codes Never Die guarantee exists specifically because of this. Your codes keep redirecting even if you cancel or delete your account. But regardless of what service you use, it's worth understanding whether your provider holds your codes hostage before you print a few hundred stickers.
The code is too dense or too poorly printed
Sometimes the problem isn't the destination or the service. It's the code itself. Two flavors of this come up constantly.
The first is density. Encoding a full paragraph of text, a lengthy URL stuffed with tracking tags, or a vCard with every field filled in produces a QR code so packed with tiny modules that phone cameras struggle with it at any real-world distance. Static codes are especially prone to this because the entire URL lives in the pattern. A short link like dsqr.page/m3kx produces a clean, easily scannable grid. A 200-character URL produces something that looks like static on a broken TV. The practical fix: shorten the encoded URL, or use a dynamic code where the actual pattern only contains a short redirect link.
The second is print quality. The code scanned fine on your screen, so you assume the file is good. But then it gets printed on a textured surface, or scaled down to fit a business card corner, or printed in low contrast colors that looked fine on a monitor but wash out on paper. Common culprits: printing a small PNG at a size larger than its resolution supports (it gets blurry), putting a dark code on a dark background, or printing on a material that warps or reflects. QR codes need contrast and clean edges. If you're printing larger than a couple inches, export as SVG so the edges stay sharp at any size.
Your logo or design broke the pattern
QR codes have built-in error correction, which means they can tolerate some damage or obstruction. But "some" is doing a lot of heavy lifting there. A logo placed in the center that covers too much of the pattern, or color choices that confuse the scanner's ability to distinguish light modules from dark ones, will kill scannability.
I'm honestly not sure there's a universal safe percentage for logo coverage. It depends on the error correction level, the scanning app, the phone camera, and probably the phase of the moon. The reliable test is just to scan it. From multiple phones, at the distance someone would actually hold their phone, in the lighting conditions where it'll actually live. If it works on your desk but fails at arm's length on a sunny wall, you know.
If you're not sure what went wrong
Start from the top of this list and work down. Check the destination URL first. Then check whether your QR service is still active. Then look at the code's complexity, print quality, and design. Nine times out of ten, it's one of the first two.
If you want codes you can update anytime without reprinting, and that won't break if you change your mind about the service, you can create one here.