# What happens when a QR code service shuts down

> Static codes are unaffected — they contain the destination directly. Dynamic codes stop resolving the moment the provider's redirect stops, and every printed copy dies at once. There is no recovery for material already distributed.

Source: https://useqr.app/vs/what-happens-when-a-qr-service-shuts-down · Last reviewed 2026-08-21 · UseQR is free forever, MIT licensed, no signup.

---

## Which codes are affected

| Code type | If the generator disappears |
|---|---|
| Static, pointing at your own domain | **Unaffected** |
| Static, pointing at a third-party shortener | **Dead** when the shortener goes |
| Dynamic | **Dead** immediately |
| Static WiFi, vCard, text, payment | **Unaffected** — no network involved at all |

A static code is a printed copy of your data. The generator was a tool, not a service, and it
is not in the path afterwards.

## If it has already happened to you

**1. Decode one of the codes.** Use a [scanner](/scan) that shows the raw text. That tells you
what the printed codes actually contain — usually a short URL on the provider's domain.

**2. Try to acquire the domain or a redirect.** Occasionally a defunct provider's domain
becomes available, or an acquirer honours existing links. Rarely, but it costs an email to
find out.

**3. Recover your destination list.** Export from the provider's dashboard while it still
exists. Once it is gone, the mapping from short code to destination is gone with it.

**4. Reprint.** For material still in your control. For material already distributed, there
is no fix. This is the whole risk.

## Preventing it next time

**Own the redirect.**

```
Printed code → https://yourdomain.com/p/abc → 302 → today's destination
```

Your domain, your server, your rules. If a vendor disappears, nothing happens.

**Write it down.** The realistic failure for long-lived codes is not a vendor collapse — it is
an engineer removing an unfamiliar redirect during a site rebuild years later. Document every
printed path in a file that survives staff turnover, with a note saying it is referenced by
physical material.

**Renew the domain for the longest term available**, and put the renewal somewhere it will not
be missed.

**Never use a public shortener on print.** The shared domain can also be blocklisted because
of someone else's abuse, which kills your codes without anyone shutting anything down.

## What UseQR's disappearance would break

Being specific, since this page is about honesty:

- **Nothing** for static codes — URL, text, WiFi, vCard, payments. The data is in the pattern.
- **The hub page** for multi-link social codes, which resolves on our domain.
- **The app-download redirect**, which detects the OS on our domain.

For those two, host the equivalent yourself and point a plain URL code at it. And because the
whole thing is MIT-licensed, you can [self-host UseQR](https://github.com/rajkaria/useqr)
and remove us from the picture entirely.

## FAQ

### Do QR codes stop working if the generator shuts down?
Static codes do not — the destination is encoded in the pattern and the generator is not involved after the image is made. Dynamic codes stop immediately.

### Can I recover a dynamic QR code after the provider closes?
Only by acquiring the domain or persuading a successor to honour the links, which is rare. Material already distributed cannot be fixed.

### How do I make QR codes that survive a vendor disappearing?
Use static codes pointing at a redirect on a domain you own, and document those paths so they survive future site rebuilds.

### Is a link shortener safe for printed QR codes?
No. Beyond the shutdown risk, shared shortener domains get blocklisted because of other users' abuse, which breaks your codes without anyone closing anything.

## Try it

- https://useqr.app/url
- https://useqr.app/scan