Dynamic vs static QR codes: which should you use?

What a static QR code is

A static QR code encodes its final content directly — the URL, Wi-Fi credentials, or contact card are baked into the code itself at the moment it's generated. It never needs to phone home anywhere, works forever, and costs nothing ongoing.

The trade-off: if the destination changes — you move your menu to a new site, or a campaign URL needs updating — the printed code stops being accurate. You'd need to print a new one.

When static is genuinely the right choice

Static codes get a bad reputation from the marketing of dynamic QR services, but for a large class of use cases they're the correct tool — simpler, cheaper, and with no dependency on a third party staying in business.

• Digital-only display — a QR code shown on a screen (a presentation slide, a TV display, a website) can be regenerated instantly if the destination changes. There's nothing to reprint. Static is always sufficient here.
• One-off or short-run campaigns — a code printed for a single event, a limited-run flyer, or a temporary promotion where the destination won't change after printing.
• Content encoded directly in the code — Wi-Fi credentials, vCard contact details, an email address, a phone number. These aren't URLs and there's nothing to redirect. The data is the code.
• Codes that won't be printed in volume — if you're printing 20 table tents rather than 20,000 product labels, reprinting to fix a URL change costs almost nothing. The break-even point where dynamic redirection saves meaningful effort is higher than most people assume.
• Privacy-sensitive contexts — a static code pointing at a URL you own produces no scan data unless you've added tracking yourself. A paid dynamic QR service logs every scan by design.

What a dynamic QR code is

A dynamic QR code encodes a short redirect URL controlled by a service, which then forwards the scanner to your real destination. Because the printed code only ever points at the fixed redirect URL, you can change where it forwards to at any time — without reprinting.

This is genuinely useful when a code is printed somewhere expensive or slow to replace: a billboard, a vehicle wrap, packaging already in a warehouse. It usually also unlocks scan analytics, since the redirect service can log every scan.

The simplest way to get 'dynamic' behaviour for free

You don't need a paid dynamic-QR service to get the core benefit — redirectability. Point your static QR code at a URL you control (your own domain, or a page on your own site) rather than directly at the final content. Then update that page's content or its own redirect whenever you need to, and every already-printed code keeps working.

This is exactly the approach the restaurant-menu guide recommends: link to a stable URL you own, not a PDF baked into the code. You get the editability of a 'dynamic' code without paying for a redirect subscription or accepting a third party logging every scan.

Scan analytics: what you get and how to get it

Analytics is one of the main selling points of paid dynamic QR services. Understanding what they actually provide — and what you can replicate yourself — helps you decide whether the subscription is worth it.

A paid dynamic QR service typically provides: scan count over time, country and city of the scanner (derived from IP geolocation), device type (iOS vs Android, phone vs tablet), and the time and date of each scan. Some services also show the referrer and allow you to define conversion events.

You can get equivalent or better data for free by pointing a static QR code at a URL on your own domain and using a web analytics tool:

• Plausible Analytics or Fathom — privacy-friendly, lightweight trackers that record page views, country, device, and referrer without cookies or personal data. Free tiers available; self-hosted Plausible is free indefinitely.
• Google Analytics 4 — free, records the same scan-derived signals (country, device, time) plus richer behaviour data if the user browses further on your site.
• UTM parameters — append a UTM source/medium/campaign to the URL before encoding it (e.g. ?utm_source=table-tent&utm_medium=qr). Any analytics tool will then break down scans by campaign without any extra setup.
• Server-side logging — if you control the server, a simple redirect endpoint can log every hit with timestamp, IP (for geolocation), and user-agent without any client-side script.

When a paid dynamic QR service is worth it

• You need analytics without touching any code or server — the service handles it entirely through a dashboard.
• Non-technical staff need to repoint codes through a dashboard without your involvement.
• You're managing hundreds of codes across campaigns and need centralised management, bulk editing, and folder organisation.
• The codes are printed somewhere physically expensive or slow to replace and redirectability genuinely matters.

Frequently asked questions

Related guides