Dynamic vs static QR codes, what's the difference?
From the outside they look identical: a square of black and white modules. The difference is what's encoded inside the pattern, and that decides whether you can ever change the destination after printing.
Static QR codes: the URL is baked in
A static QR code encodes your destination URL directly into the pattern. If you want the QR to open https://mybiz.com/menu, those characters are literally embedded in the black squares.
Print it once, and that URL is the URL. Forever. There is no server, no redirect, no dashboard, the phone reads the URL straight off the paper and opens it.
Upside: simple, free, nothing depends on a third party staying online.
Downside: if the URL changes, your printed QRs become dead. If your menu moves from /menu to /winter-menu, every poster is firewood.
Dynamic QR codes: the QR points to a redirect
A dynamic QR encodes a short, permanent URL hosted by a service, for QRFixed, that's qrfixed.com/<id>. When someone scans it, that URL opens, and the service immediately redirects them to whatever destination you've configured in your dashboard.
The QR image itself is still locked the moment it's printed. But because the URL inside it points to a redirect you control, you can change the final destination as often as you want.
Upside: editable forever, scan counts, can be disabled if abused.
Downside: depends on the redirect service staying online. Slightly slower (one extra HTTP hop). Often costs money on big platforms.
Side by side
| Static | Dynamic | |
|---|---|---|
| Change destination after print | No | Yes |
| Scan count / analytics | No | Yes |
| Depends on a third party | No | Yes |
| Pattern density | Depends on URL length | Always short & clean |
| Cost | Free | Free on QRFixed up to 3 codes |
When to pick static
- The destination genuinely will never change (e.g. a Wikipedia article, your own company homepage).
- You're embedding the QR in a one-time mailing, postcard or event ticket that becomes irrelevant after the date.
- You absolutely don't want any external dependency in the loop.
When to pick dynamic
- You're printing the QR on something durable: stickers, packaging, signage, business cards.
- The destination is a payment link, campaign URL or anything else that's likely to change.
- You want to know how many times the QR was scanned.
- You might want to disable the link later (e.g. an old promo that you don't want still active).
A subtle trap with static codes
Long URLs make for dense, hard-to-scan QR codes. A URL with tracking parameters can easily push a static QR into a high-density version that looks like noise on a poster from any distance.
Dynamic codes sidestep this entirely: the QR always encodes the same short redirect URL, no matter how long the final destination is. The pattern stays clean.
The pragmatic recommendation
If the QR will be on anything that costs more than a single sheet of paper to reprint, go dynamic. The minute you've reprinted one batch of stickers because a URL changed, you've already lost more than the cost of any QR service.
Try it
Generate a free static QR if you just need a quick one, or create a free account to get up to 3 dynamic codes whose destination you can edit anytime.