Web
Static vs dynamic QR codes: make one that never expires
A static QR code holds your URL itself, so no service can switch it off. When to use one, how to pick error correction and how to test the print.
A QR code can stop working even though the print is perfect, because the link inside it points at a service that is no longer there. If you want a code on a menu, a poster or a business card that still scans in five years, you want a static code, and you want to know what that does and doesn't promise.
This guide covers the difference, what to put in the code, and how to check the print before it goes anywhere. I'm using my own QR Code Generator for the examples, so the numbers below match what it does.
#Static and dynamic, in plain terms
A static code stores your content directly in its pattern. Scan it and the phone reads the URL straight out of the squares. Nothing sits in between, so nothing can be turned off.
A dynamic code stores a different, usually short, URL that points at a server run by whoever made the code. That server sends the scanner on to your real destination. It's the same idea as a link shortener. The point of it is that the destination can change later without reprinting, and the service can count scans.
The cost is that you now depend on that server. If the account lapses, the service closes, or the plan changes, the printed code still scans, but it no longer reaches your page. The squares on the paper are fine. The link behind them is gone.
#The code never expires, but the URL can
A static code has no expiry date. It's a picture of some text. What can still fail is the thing the text points at.
- Use a domain you own. A URL on someone else's platform lasts as long as their platform does.
- Keep the path short and stable.
example.com/menuis better than a long path with tracking parameters. - If you move the page later, leave a redirect on the old URL. You control that on your own site, which is the whole advantage.
So a static code isn't permanent by magic. It moves the failure point from a service you rent to a domain you own, and that's a much better place to have it.
#What the generator does with your input
It encodes exactly what you type. It doesn't rewrite, shorten, validate or open the content, and it doesn't add tracking. If you type a URL with a typo, you get a working code for the typo. Your text stays in the browser; it isn't uploaded.
The limit is 1,200 UTF-8 bytes. Plain ASCII is one byte per character, but accented letters, emoji and many non-Latin scripts take two to four, so the byte counter next to the box is the number to watch, not the character count.
Shorter content also means fewer modules (the little squares). A code with fewer, bigger modules is easier for a phone camera to read at a distance or on rough paper. If your URL is long, shortening it on your own domain does more for scan reliability than any setting.
The tool makes text and URL codes only. It doesn't scan, keep history, add logos, or build contact or Wi-Fi forms.
#Pick an error-correction level
A QR code carries extra data so it can still be read when part of it is dirty, creased or covered. You choose how much extra. The tool offers three levels, and the standard (ISO/IEC 18004) gives these approximate recovery figures:
| Level | Option name | Approximate damage it can recover from |
|---|---|---|
| M | Medium | about 15% |
| Q | Quartile | about 25% |
| H | High | about 30% |
Medium is the default, and for a clean URL on a screen or a flat print it's fine. Move up to Quartile or High for things that get scuffed: stickers, outdoor signs, packaging, anything folded in a pocket.
Higher levels aren't free. They add more data modules for the same content, so the code gets denser and each square gets smaller at a given size. That's the tradeoff, and it's why High on a very long URL can scan worse than Medium on a short one. Those percentages are the standard's general figures, not a promise about a specific phone or print.
#Colors, quiet zone and file formats
The output is fixed black on white. There are no color or style options, which is deliberate: dark squares on a light background is what scanners handle best.
Every code gets a quiet zone of 4 modules, the blank border around the pattern. Scanners use it to find where the code starts. Don't crop it and don't let a design element run into it.
You can download two files:
- SVG for print. It's a vector, so it stays sharp at any size, from a business card to a banner.
- PNG for screens and documents. You pick a maximum size of 256, 512 or 1024 pixels. The PNG is drawn at a whole number of pixels per module, which keeps the edges crisp, so it can come out a little smaller than the size you chose.
#Test it where it will live
A code that scans on your monitor can still fail on the wall. Before you print a hundred of them:
- Print one at the real size, on the real material.
- Scan it with more than one phone, from the real distance.
- Scan it in the real light. Glare and shadow break codes more often than the pattern does.
- Open the page it lands on and confirm it's the right one.
I test builds the same way: the artifact you ship, not the one on your machine. The same idea is in Test the package you publish.
#When you actually want a dynamic code
Sometimes dynamic is the right call. If the destination has to change after printing, such as a campaign page you'll swap every month, or you need scan counts, a redirect service does that and a static code can't.
This tool doesn't do either. It makes static codes only. If you go dynamic, put the redirect on your own domain so you still own the link, and treat the service as something you can replace.
#Checklist
- The URL is on a domain you own and won't be reused.
- The content is as short as you can make it, and under 1,200 bytes.
- You typed it carefully, because nothing validates it for you.
- Error correction matches the wear: Medium for flat and clean, Quartile or High for rough use.
- You kept the 4-module quiet zone and black on white.
- SVG for print, PNG for screens.
- You scanned a real print, with real phones, in real light.
Make one in the QR Code Generator, or see the rest of the tools. If the flyer or post also carries a photo from your phone, remove its GPS and EXIF data before you share it.