Most vCard and WiFi QR codes are printed once and wrong forever. Someone generates the code in a free tool, prints it on a business card or a café wall, and then the phone number changes or the WiFi password rotates. The code still scans. It just points at the old details, and there is nothing to fix because the details were never stored anywhere you can reach. This is the difference between encoding content into the image and hosting it behind the image.
What is a vCard or WiFi QR code?
A vCard QR code holds contact details and a WiFi QR code holds the credentials a phone needs to join a network, and both come in a static form and a dynamic form. A vCard code carries a name, title, phone, email, and company; a scanner reads it and offers to save the contact. A WiFi code carries a network name and password; a scanner reads it and offers to join. The question that decides everything else is where those details actually live.
Why can’t you edit a static vCard or WiFi code?
You cannot edit a static vCard or WiFi code because the generator encodes the full payload directly into the pattern of dots, and the printed image never changes. There is no server in the path and nothing pointing anywhere. The dots are the data. When a static tool builds your vCard code, it writes your phone number into the grid itself; when it builds a WiFi code, it writes the password into the grid itself. Change the number or rotate the password and every printed copy is now wrong, because the only place the old value exists is the ink. Fixing it means generating a new code and reprinting everything that carried the old one.
How does a dynamic content type work?
A dynamic content type encodes a short redirect link in the dots and hosts the actual vCard or WiFi details on a page you control. The printed square holds only the short link. When someone scans it, they land on a hosted card that presents your contact details or your network credentials, and you can change what that page holds at any time from the console. The next scan follows the new rule, no reprint. redireo supports this for the content types it ships — URL, PDF, vCard, WiFi, plain text, email, and SMS — so the same editable redirect layer that powers a normal dynamic link also powers a business card or a guest network.
That means a printed vCard can survive a job change. Update the title and phone number in the console, and the card that was printed in January hands out the correct details in November. A guest WiFi code behind reception can survive a password rotation the same way: change the credential on the hosted page, and the next guest to scan joins the current network.
What is the trade-off with a dynamic WiFi code?
The trade-off is that a dynamic WiFi code routes the scanner through a hosted join page instead of firing the phone’s native join sheet directly. A static WiFi code encodes the raw WIFI: payload, so a scanner can offer to connect without any network in between — which is exactly why it also can never change. A dynamic code lands the guest on a page first, which needs the redirect to be online, and in exchange gives you an editable password and a record of how often the code is used. For a home fridge magnet that never changes, static is fine. For a café, an office lobby, or an event that rotates its guest password, the editable version is the one that stays correct. This is the same honest trade every dynamic code makes: you gain editability and data, you take on a dependency on the redirect staying live.
When should you keep a static vCard instead?
Keep a static vCard when the details will never change and you want the code to work with no vendor in the loop. A personal card with a number you have held for a decade, engraved on something permanent, is a reasonable static code — it costs nothing, never expires, and depends on no one. The moment the details might change, or you want to know how often the card is scanned, the hosted version is the one that will not strand you. Contact details and passwords both tend to change more often than the paper they are printed on, which is why editable is usually the safer default.
See how the shipped content types work, and build a vCard or WiFi code you can edit after it is printed, on the content types feature page.