The one-line difference
A static QR code encodes its destination — a URL, a Wi-Fi password, a vCard — directly into the pattern the moment it's generated, permanently. A dynamic QR code encodes a short redirect link to a third-party service instead, and that service is what actually sends the scanner to the real destination — so the owner can change where it points after the code is already printed. Everything else about the two — how they look, what they cost, what they can track — follows from that one design choice.
How each one actually works
A static code has no moving parts. Whatever you encode — a URL, a network name and password, a set of contact fields — gets written straight into the code's data modules, and that's it. No server involved, no account, no internet connection required to read it. Want to change the destination later? You'll have to generate and print a new code.
A dynamic code works differently. It only holds a short link, which points to a redirect service that looks up the current destination and forwards the scanner there. Because that encoded link is short, dynamic codes can carry a simpler, less dense pattern than a static code holding a long URL — or spend that spare capacity on a higher error correction level instead, worth doing on anything that'll get printed, folded, or scanned in bad light. QR codes support four correction levels, from L (about 7% of the data recoverable) up to H (about 30%), and higher levels do trade off against how intricate — and printable — the pattern gets.
Where you'll see each type
Static codes show up wherever the destination is never going to change: a Wi-Fi network at home, a vCard on a personal business card, a fixed URL on a one-off event flyer. No subscription, no expiration date — they'll still scan five years from now with no internet connection required.
Dynamic codes show up in QR code marketing, restaurant menus, retail packaging, and museum exhibits — anywhere the code's owner wants to update the destination without reprinting, or wants scan data back. Every scan passes through the redirect service, which can log the scan count, timestamp, approximate location from IP address, and device type. That's campaign-performance data a static code simply can't produce, since it never touches a server.
Picking the right one (and doing it on QRDock)
Here's the tradeoff worth knowing before you pick: a dynamic code depends on its redirect provider staying in business, and needs an internet connection to resolve at scan time. It also carries a risk static codes don't — because the destination can be changed anytime after the code is printed and handed out, a link that was legitimate on day one isn't guaranteed to still point somewhere safe months later. That's true even for codes you generated yourself, if you ever hand a dynamic code's management over to someone else.
If your content is fixed and you want it working forever with no third party in the loop — Wi-Fi, a vCard, a set destination — generate a static code. QRDock does that for free, no account or subscription needed, and its scan-time URL check runs as a best-effort safety layer on anything you scan, static or dynamic. Try it at qrdock.app.
Frequently Asked Questions
Can a static QR code become a dynamic one later?
No. A static code's destination is baked into the pattern at creation, so there's nothing to redirect — you'd need to generate and print a new dynamic code from scratch.
Do dynamic QR codes expire?
They can, if the redirect service that hosts them shuts down, your subscription lapses, or the provider stops supporting old links. A static code never expires on its own, since it doesn't depend on a third-party server to resolve.
Which type should I use for a Wi-Fi network or a business card?
Static. Wi-Fi credentials and contact details rarely change, and you want the code to keep working offline forever without paying a service to keep the redirect alive.
Are dynamic QR codes less secure than static ones?
Not inherently, but they carry a different risk: because the destination can be changed after the code is printed, a link that was safe when scanned last month isn't guaranteed to still be safe today. QRDock's scan-time URL check applies to both types, but it's a best-effort layer, not a guarantee.