Static: the content is the code
A static code encodes the link, text, Wi-Fi details or contact card directly. Phones read it without contacting anyone, so it works forever, even if the company that made it disappears. It is free and private: nobody sees who scans it.
The trade-off: it can never change. A typo in the printed link stays there, and long content makes a denser code that needs more space.
Dynamic: a short link you can repoint
A dynamic code encodes a short link such as qrbc.de/AB12CD34EF56. When someone scans it, our redirect service sends them to the destination you set — and you can change that destination anytime without reprinting. You also see how many scans each code gets per day.
The trade-off: the code relies on the redirect service, and on your account staying in good standing. The printed pattern itself never changes.
Which one to choose
- Wi-Fi access, contact cards, plain text: static — the content has to be inside the code.
- A link printed on menus, packaging or posters you might update: dynamic.
- You want to know whether a campaign gets scanned: dynamic.
- A link that will never change, shared once: static is enough.
What scan counts can and can't tell you
Scan counts are redirect hits, not people. One person scanning twice counts twice, and link previews in chat apps can count too. We show which share looks automated, but we don't claim to count unique visitors.
Questions people ask
Can I turn a static code into a dynamic one later?
No. A static code's content is part of the printed pattern. Create a dynamic code and print it instead; from then on you can change its destination whenever you like.
What happens to my dynamic codes if my plan ends?
Your existing short links keep redirecting and your static codes keep working. See pricing for the full policy, which we also show before you create a dynamic code.
Does the redirect slow people down?
The extra step is a single, fast redirect — people won't notice it.
Put it into practice
Free, no account needed for static codes.