What a static QR code is
A static QR code holds your content directly in the pattern of squares. If you encode a web address, the address itself is in the image. A phone camera reads the squares, decodes the text and acts on it. There is no server in between.
That has one important consequence: the code cannot change. If the content must be different, you make a new code. In return, the code depends on nothing but the phone that reads it. Print it once and it works for as long as the destination exists.
What a dynamic QR code is
A dynamic code does not hold your final content. It holds a short link that points to a service run by the code provider. When someone scans, the phone first goes to that service, which then forwards them to your real destination.
Because the redirect lives on the provider's server, you can change the destination later without reprinting. The same step lets the provider count scans, record roughly when and where they happened, and show you a report.
How the data sits inside each one
Take the address https://example.com/spring-menu-2026. A static code stores all 36 characters, and the code is fairly dense. A dynamic code stores something like https://short.example/aB3x, a shorter link the provider generates. The squares are larger and easier to scan, but the real address is stored on the provider's side.
You can see this for yourself. Scan any code with the QR code scanner and read the decoded text. If the address shown belongs to a company other than your own, you are looking at a dynamic code.
The trade-offs
| Question | Static | Dynamic |
|---|---|---|
| Change the destination after printing | No | Yes |
| Scan counts and reports | No | Usually yes |
| Depends on a provider staying online | No | Yes |
| Can stop working if a plan lapses | No | Often, depending on the plan |
| Extra step when scanned | None | One redirect |
| Works for WiFi, UPI, contact cards | Yes, stored in full | Only for links |
The row that people overlook is dependence. A dynamic code printed on 5,000 packages is only as durable as the account behind it. If the subscription ends, the scan may land on an error page or an advertisement. Before you pay for any dynamic code, ask what happens to the printed ones on the day you stop paying.
When static is enough
Static covers a large share of everyday jobs, especially when the content is something that does not move:
- WiFi login for a home, cafe or office: use a WiFi QR code.
- Payment to a fixed UPI ID: a UPI QR code is a static payload that opens the payer's app.
- A contact card on a visiting card.
- A WhatsApp chat link, a map location or a Google review link.
- A link to your own website, where you control the page and can change what it shows.
That last point is a useful trick. If you own the destination page, you get most of the benefit of a dynamic code without a middle service: print a static code pointing to a stable address on your site, and change the page whenever the offer changes.
Choose dynamic when you really need one of its two features. You are printing a large run, you do not own the destination page, and the target may change. Or you need scan statistics to judge a campaign. In both cases, pick a provider you trust, keep the account details somewhere safe, and write down the renewal date.
If you only want to know whether a poster works, a simpler approach is a separate page address for each placement, such as /poster-mall and /poster-station, and compare visits in your site analytics.
A worked example: a shop owner decides
Meera runs a tailoring shop and wants a QR code on her shop board that opens her price list. She first thinks of a dynamic code so she can change prices. Then she notices the price list is a page on her own website. She prints a static code that points to that page. When prices change, she edits the page, and the board stays the same. She spent nothing beyond the print, and has no account to keep alive.
Her cousin Arjun sells packaged snacks and prints 20,000 pouches with a link to a recipe campaign that may move between sites. He has no page of his own to edit, so a dynamic code with a paid plan fits him. He sets a calendar reminder for renewal and tests the code after every plan change.
Run through these four before printing anything in volume. Do I own the destination page? Will the destination change before the print wears out? Do I need counts from the code itself rather than from my site? And what is the worst thing that happens if the provider disappears? If the answer to the last question is a loss of money or trust, prefer static or own the redirect on your own domain.
What this site makes
Every code on this site is static. The text is stored in the code, generated in your browser, and nothing is uploaded. There is no tracking redirect, no account and no expiry date, so a code you download keeps working as long as its content does. It also means this site cannot edit a code after you print it or count scans. Start with the QR code generator and check the text shown under the code before you download.
Questions people ask
Can a static QR code expire?
The code itself cannot expire, since it only contains your content. It stops being useful only if the thing it points to, such as a web page, is removed.
Can I track scans with a static QR code?
Not from the code. If it opens a web page you own, your site analytics can show visits to that page, and a unique page address per placement tells you which one was scanned.
Are dynamic QR codes less safe?
Not by nature, but you trust the provider with your traffic and the redirect. Preview where a code leads before opening it, and prefer providers that explain what happens when a plan ends.
Can I convert a static code to dynamic later?
No. A printed static code has its content fixed. You would need to print a new code that points to a redirect service.
Which is better for a restaurant menu?
If the menu is a page on your own site, a static code is enough, because you can change the page whenever the dishes change.
Updated 2026-10-14 · Written by the CodingMarble team