What Happens When a QR Code Company Shuts Down?

If the company behind your dynamic QR code shuts down, your codes stop working — instantly and permanently. The printed image still scans, but it points to a redirect server that no longer exists. Static codes survive; dynamic codes are only as alive as the company hosting them. This has already happened to real businesses.

A real case: 1,000 printed books, dead overnight

Consider SQR (sqr.co / sqr.link), a dynamic QR and short-link service that sold lifetime deals on AppSumo. Buyers paid once, believing they owned their codes forever.

One customer reported that "1000 books printed with this link and QR code and suddenly they stopped working" — a single sentence that captures the entire risk. The links in the sqr.link domain went dark, and every code in a print run of a thousand books became a dead end.¹

That's the sentence to sit with before reading any further, because it's the whole argument in miniature: nothing was wrong with the printed books. The paper was fine, the ink was fine, the QR pattern itself was fine. What died was a server the book's owner never saw, controlled by a company they had no relationship with beyond a one-time payment months or years earlier.

The full timeline: how SQR's lifetime deal collapsed

AppSumo's own reviews and Q&A threads for SQR document the collapse in enough detail to reconstruct a rough timeline. None of the entries below are direct quotes — they're paraphrased from public buyer reports, each linked to its source so you can verify it yourself.

Interleaved with this timeline is a separate exchange worth noting on its own: at one point a buyer asked outright whether SQR had "gone under," and another buyer replied that the site was back up, arguing that businesses depend on SQR and it should communicate better with customers.² That exchange matters because it shows the service wasn't down constantly — it flickered, came back, went down again, over roughly a year and a half. For anyone with printed material in circulation during that window, "flickering" is not meaningfully better than "gone." A code that works today and fails next week is still a code you can't trust for anything permanent.

The pattern across the full timeline is close to textbook: first a request for more money from people who already paid for a lifetime, then intermittent outages, then expired certificates, then a security warning, then silence, then confirmation it was over. And crucially — the "lifetime" promise didn't save anyone, because the codes still depended on SQR's servers to run. When those servers went, "lifetime" went with them.

Why dynamic codes die when the company does

To understand why this happens, you need to know what a dynamic QR code actually is. This is the difference between [dynamic and static QR codes](/blog/dynamic-vs-static-qr-codes), and it decides everything about your risk.

• A static QR code encodes your destination directly in the pattern. The URL (or text, or contact card) is the black-and-white image. Nothing sits between the scanner and the destination. No company can switch it off, because there is nothing to switch off — it works offline, forever, even if every QR company on earth vanished.

• A dynamic QR code encodes a short redirect URL that lives on the provider's domain (like sqr.link/abc). When someone scans it, their phone hits the provider's server, which looks up where you told it to point and forwards them there. That indirection is what lets you edit the destination after printing — a genuinely useful feature. But it means your code is a shell. The real destination lives in the provider's database. Turn off that database, and the shell points to nothing.

[Printed QR image]  →  [Provider's redirect server]  →  [Your real destination]  
        survives              this link breaks              never reached  

When a company shuts down, the middle box disappears — not gradually, but all at once, for every customer that provider ever had. It isn't that your specific code was singled out or that you did anything wrong. The image on your packaging is fine; the domain name resolves to nothing; the destination is unreachable. Every dynamic code that provider ever issued fails at the same moment, which is why a single company's shutdown can be traced through hundreds of unrelated buyer complaints on the same forum thread, as it was with SQR.

Which print use cases are most exposed

Not every printed QR code carries the same amount of risk if a provider disappears. What matters is how expensive or how possible it is to reprint, and how long the material stays in circulation.

The books-and-packaging end of this table is exactly where the SQR complaints cluster, and that's not a coincidence — those are the formats where a customer has no cheap way to undo a bad provider choice after the fact. If you're deciding how much company-risk you're willing to accept, weigh it against how permanent (and how expensive to redo) the specific thing you're printing actually is, not against QR codes as a category.

This is the same risk as a subscription lapse

Here's the part no subscription vendor will write down: a company shutting down and your subscription lapsing are the same failure mode. In both cases, your printed codes die because a server you don't control stopped forwarding them.

Think about what you're really buying with a dynamic code on a subscription. You are not buying a permanent asset. You are renting the provider's continued willingness — and continued ability — to keep your redirect alive. That willingness ends if you miss a payment. That ability ends if they go bankrupt, get acquired and sunset the product, or simply lose interest. From the perspective of your printed menu or your 1,000 books, the cause doesn't matter. The result is identical: a dead link.

This is why the question "do QR codes expire?" has an uncomfortable answer. The code itself never expires — but the service behind a dynamic code can, and does. It's also why going without a subscription entirely is worth evaluating on its own merits, separate from whether a given provider looks financially healthy today.

Warning signs a QR provider may be heading for shutdown

The SQR timeline isn't just a cautionary story — it's a fairly reliable early-warning pattern, because most small-vendor shutdowns follow a similar sequence rather than happening without any notice at all. Watch for these, roughly in the order they tend to appear

1. Retroactive fee requests. Being asked to pay for a new plan to keep using something you already bought outright is the single strongest signal — it usually means the underlying business model can no longer sustain existing customers for free.
2. Intermittent outages with no public status page. A service that goes down for hours or days with zero communication is already operating past the point of having support staff to spare.
3. Expired certificates or broken custom domains. SSL certificates need active renewal. A lapsed certificate on a paid feature is a sign that operational basics are being neglected, not just an isolated bug.
4. Support and community questions going unanswered for weeks. A single unanswered ticket is normal. A public Q&A thread with the same "is this still running?" question repeated by multiple customers over months, with no reply from the vendor, is not.
5. Public funding pleas or founder posts about the business struggling. By the time this becomes visible to customers, the company is usually already deciding how to wind down, not whether to.
6. Security warnings on generated links. This is close to a final-stage signal — it typically means the domain's reputation has already degraded, often because the certificate or DNS configuration was abandoned.

None of these alone is proof a shutdown is imminent — services recover from single outages all the time. But two or more appearing together, especially the first and fourth, is worth treating as a reason to start point 2 of the checklist below before you print anything new.

How to protect yourself: a checklist

You don't need to fear dynamic codes — you need to know which kind of dependency you're signing up for. Before you print anything at scale, run this check

1. Is your code static or dynamic? If you can log in and change where it points, it's dynamic and depends on a live server. If the destination is permanent, it's static and self-contained. For truly permanent print (monuments, book ISBNs, engraved signage), a static code carries zero company-risk — there is no server to lose.

2. Can you export or self-host the redirect? Some providers let you point a domain you own at their redirect, or export your full URL mapping as a spreadsheet. If you control the domain, you can survive the provider's death by re-hosting the same redirects yourself, on a different service, without reprinting anything. If the redirect lives entirely on their domain (like theirbrand.link/abc), you cannot — the moment that domain goes dark, every code is unrecoverable no matter how good your backup of the destination URLs is.

3. What do the terms say happens if service ends? Search the provider's terms and help docs for "account closure," "service termination," or "what happens to my codes." Silence is itself an answer — a provider that has thought about this scenario usually says so explicitly, because it's a reasonable question to plan for.

4. Does the payment model align incentives with permanence? A subscription only funds your code's survival for as long as you keep paying, which means a missed renewal produces the exact same outcome as a company shutdown. A one-time purchase, such as OwnQR's $15 model, removes that specific recurring-lapse trigger — though you should still confirm the redirect itself won't vanish if the company does (see point 2).

5. How financially healthy is the provider? A one-person AppSumo lifetime-deal shop and an established company are different risk profiles. Ironically, the very "buy it once and we'll host it forever" promise is hardest for the smallest operators to keep — which is exactly what happened to SQR's lifetime buyers.

What to do if your QR code provider already shut down

If you're reading this because it's already happening — your codes stopped working and you're trying to figure out next steps — here's the practical recovery sequence, in order

1. Confirm whether the affected codes are static or dynamic. If they're static, the printed image itself still encodes the correct destination and nothing is actually broken on your end — the issue is likely something else (a dead link on your side, not the provider). If they're dynamic, proceed to step 2.
2. Check if the destination URL itself still exists. The provider's redirect service may be gone, but if the page you were sending people to (your website, your menu PDF) still exists at its original address, you have something to redirect to — you just need a new way to get people there.
3. Generate replacement codes under a provider you control, ideally one offering a permanent redirect you can export or self-host, so this doesn't repeat. Point the new codes at the same final destinations.
4. Decide whether to reprint or patch. For small runs (business cards, signage you can swap), reprinting is usually cheapest. For large or expensive runs (bulk packaging, books already in warehouses), consider a supplementary fix: a sticker with the new code over the old one, or updated signage near the display directing people to a short, easy-to-type URL as a fallback.
5. Notify anyone who relies on the old codes — staff, retail partners, event organizers — before customers start reporting dead scans to them instead of to you.
6. Document the new provider's shutdown policy before you commit, using the checklist above, so this isn't a recurring cost every time a vendor's business model changes.

The honest takeaway

Static codes are the only QR codes that are truly immune to a company shutting down, because they depend on no one. Dynamic codes trade that independence for the ability to edit after printing — a trade that's often worth it, as long as you go in clear-eyed about the dependency, and as long as what you're printing can tolerate the risk level described in the table above.

If you want the edit-after-print convenience without the monthly renewal-cliff, a one-time-purchase model like OwnQR's $15 lifetime license removes the most common trigger — a lapsed subscription — while still letting you re-point the code. It doesn't repeal the laws of physics (any dynamic redirect needs a server), but it does mean your codes don't die the month you forget to pay, or the month a subscription vendor decides your plan needs a price increase. Whatever you choose, decide based on the checklist above, not on a "lifetime" label — SQR's buyers had one of those too.

¹ Buyer complaint, AppSumo Q&A, SQR product page: appsumo.com/products/sqr-qr-generator-plus-exclusive/questions
² Buyer exchange, AppSumo Q&A: appsumo.com/products/sqr-qr-generator-plus-exclusive/questions

Frequently asked questions

What happens to my QR codes if the company shuts down?
Dynamic codes stop redirecting the moment the provider's servers go offline, so anything you printed becomes a dead link. Static codes keep working, because their destination is encoded directly in the image and doesn't rely on any server.

How do I know if my QR code depends on a company staying alive?
If you can edit the destination after creating the code, it's dynamic and depends on the provider's redirect server. If the destination is fixed and can't be changed, it's static and self-contained. Check whether your provider's dashboard lets you "edit" a live code.

Can a "lifetime" QR code plan still fail?
Yes. A lifetime license only covers the price — not the physics. If the code relies on the vendor's redirect server, it lasts only as long as that server runs. SQR sold lifetime deals and its buyers still lost their codes when it shut down, some after first being asked to pay again.

How can I protect my printed QR codes?
For permanent print where you'll never change the destination, use a static code. Otherwise, prefer a provider that lets you export or self-host your redirects, read the terms for what happens on service termination, and favor models without a recurring-payment cliff.

Are static QR codes really immune to this?
Effectively yes. A static code encodes the destination in the pattern itself, so it works offline and needs no company's servers. The trade-off is that you can't change where it points after printing — if the destination URL itself dies, you'd need a new code regardless.

What should I do if my QR code provider already shut down?
First confirm whether your codes are static (unaffected) or dynamic (likely dead). For dynamic codes, generate replacements under a provider you control, point them at the same destinations, and update any signage or partners relying on the old codes.