Dynamic vs static QR codes: what print shops need to know

What each type actually is, underneath the marketing

A static QR code is a direct encoding. The characters of your URL are converted into a bit stream, error-correction codewords are appended, and the result is laid out as the module grid you see. Everything the scanner needs is in the ink, and nothing else is involved. The consequence is that the length of your URL directly determines how dense the pattern is.

A dynamic QR code encodes a short link instead. That link resolves on a server you control, which then issues an HTTP redirect to the real destination. The scanner experience is identical — the phone opens a page — but there is now a hop in the middle where you can change the target, count the request, pause the code, or route by device or language.

Neither is a different kind of QR standard. Both are ordinary QR codes; the difference is entirely in what you chose to encode and what sits behind it.

Pattern density: the reason dynamic prints better

QR codes come in versions from 1 (21×21 modules) up to 40 (177×177). The version is chosen automatically based on how much data you encode and at what error-correction level. More characters means a higher version, which means more modules squeezed into the same physical square, which means each module is physically smaller.

A typical campaign URL with UTM parameters runs 90 to 120 characters and pushes the code to version 7 or above. At 20 mm printed, those modules land near the resolution limit of the press and well inside the range where dot gain on uncoated stock lets adjacent dark modules bleed into one another. Scan rates fall, and the failures are intermittent enough that nobody catches them in proofing.

A short dynamic link of 20 to 25 characters keeps the same code at version 2 or 3. The modules are visibly chunkier, the code tolerates ink spread, and it leaves headroom for a centre logo at error-correction level Q. On small-format work this is usually the single biggest reliability difference available to you.

The editability question, priced in reprints

A restaurant changes its menu PDF link. A retailer moves a product page during a site migration. An agency's campaign landing page is retired at the end of a quarter. In each case, with a static code, every printed piece is now waste and someone has to pay for the reprint.

With a dynamic code the printed link never changes — only the destination behind it does, edited from a dashboard in a few seconds. For any asset with a shelf life longer than a single campaign, the arithmetic is not close. One avoided reprint of a few thousand menus covers years of subscription.

This is also the strongest argument to put in front of a client who baulks at an ongoing cost. You are not selling them analytics; you are selling them the right to change their mind after the ink dries.

Tracking, and what it is worth to your clients

Only dynamic codes can be measured, because only they involve a request to a server you control. That gives you scan counts over time, device and OS breakdowns, approximate geography and referrer data where a scan came through a link rather than a camera.

For agencies and print shops this is often the difference between a one-off print invoice and a retained relationship. A monthly scan report attached to the campaign turns a commodity print job into a measurable marketing channel, and it makes the next quarter's budget conversation dramatically easier for your client to justify internally.

• Scans over time — did the campaign spike and die, or build steadily?
• Per-placement comparison — poster A versus poster B, branch A versus branch B.
• Device and OS split — informs wallet passes, payment options and page weight.
• Geography — proves distribution actually reached the areas that were paid for.

When static is still the correct choice

Static is not a legacy option; it is the right answer for several payloads. Wi-Fi credentials, vCards and plain text have no web destination to redirect to, so there is nothing a dynamic code could add. Codes handed out at a one-day event and thrown away that evening rarely justify tracking. Some regulated environments also prohibit an intermediate redirect entirely, and archival print — a book, a plaque, a certificate — may be better served by a permanent code with no dependency on any company staying in business.

The honest framing to give a client: dynamic is the default for marketing, static is the default for data payloads and permanence.

• Wi-Fi network credentials on a card or window sticker.
• vCard contact details on a business card.
• Plain-text instructions, serial numbers or short messages.
• Archival or regulated print where an external redirect is unacceptable.