Dynamic vs static QR codes

Every QR code is a static object: a fixed pattern of dark and light squares that encodes a fixed string of text. The word "dynamic" does not describe the code at all. It describes what the string points to. Once you see that, most of the marketing around dynamic codes gets simpler, and so does the decision about which kind you need.

What a dynamic QR code actually is

A static QR code stores your destination inside the pattern itself: the modules spell out https://your-site.example/menu and a phone opens that address directly. Nothing sits between the paper and your page. A dynamic QR code stores a different, much shorter address — a redirect link on a service you control through an account or licence, in this app of the form qr.bnj.app/r/CODE. When a phone scans it, it opens that short link; the redirect service looks up where that code currently points and forwards the phone there. The pattern on the paper never changes. What changes is a row in a database on the server. That is the whole mechanism, and it has two consequences worth holding onto. First, because the encoded string is short, the code has fewer modules than one carrying a long address, which makes it easier to print small and leaves room for a logo or a photo. Second, because every scan passes through the redirect, the service can count it — which is where scan statistics come from. Neither of these is magic; both follow from putting a short indirection between the paper and the page.

When a static code is the right choice

Static is the default, and for a great many uses it is simply better. A static code carries your link inside itself, so it works with no server, no account and no subscription, and it never expires. It works offline: a code that opens a Wi-Fi login page, dials a number, adds a contact card or shows a plain text note has no reason to go through anyone's redirect. It is permanent in a way nothing dependent on a service can be, which matters for things meant to outlive any particular provider — an engraved plaque, a museum label, a serial-number tag. And it has no tracking: the phone talks only to the destination, which is the honest choice when you do not need to count anything. In SWAPQR the static path is free and unlimited, with every module style, corner style, colour and logo option included, and it exports PNG and SVG. If the link is fixed for good, or if reprinting the paper is cheap, choose static and do not think about it again.

What happens if the redirect service disappears

This is the part most dynamic-QR marketing leaves out, so it should be said plainly: a dynamic code depends on the redirect service being online. If the service that owns the short link goes away, every printed code pointing at it stops working. The paper still scans — the phone will dutifully open the short address — but there is nothing at the other end to forward it. No error correction, no print quality and no goodwill changes this; it is built into the design. A static code has no such dependency at all. Between those two extremes there is a softer case, which this app handles explicitly: if you stop paying, your codes do not become dead links. Scans go to a neutral "on hold" page, and the code starts working again the moment you subscribe or free up a slot. Pausing a code yourself does the same thing. But an on-hold page is only possible while the service exists. Weigh the dependency honestly against what the code is for, and keep a record of which printed pieces carry dynamic codes so you know what is affected.

Why printed material is the reason to go dynamic

On a screen, a QR code costs nothing to replace; you regenerate it and the old one is gone. On paper it is different. A table tent has been laminated, a price list has been posted on two hundred shelves, a code has been printed on the box of every unit in a production run, a sign has been bolted to a wall, a card has been handed out. The paper is the expensive part, and the paper is what a dynamic code protects. The menu changes, the campaign ends, the form moves to a new address, the video is replaced — and the square that people already have in front of them keeps working, because you changed the row behind it instead of the print. The rule of thumb in the studio is the honest one: if reprinting is cheap, static is fine; if it is not, the code should be dynamic. Packaging, machine instruction labels, real-estate signs, shop windows, event posters printed in quantity and business cards are the usual candidates. Anything printed once and expected to last is the case.

Choosing in practice

Ask three questions. Will the destination ever change? If it genuinely will not — a permanent contact card, a fixed document — static wins on every count. Is the paper expensive or hard to replace? If so, the flexibility of a dynamic code pays for the dependency it introduces. Do you need to know whether anyone scans it? Only a redirect can count scans, and the count is the only honest reason to accept one when the destination is stable. In SWAPQR, static codes are free without limit; the free tier also includes one dynamic code with a monthly scan allowance, and a paid plan removes the cap, adds more codes, lets you pick your own short code, and shows scan statistics by day and by device. There is no account in the usual sense — you get a licence code, which you keep to restore your codes on another device. Whichever you pick, print one sample and scan it with a real phone before ordering the run; that advice does not change with the type of code.