Choosing a contact QR is mostly a decision about what the code contains and what the recipient should do next. A static vCard QR embeds contact details, a website Save Contact button serves a saved contact file, and Wallet cards support separate contact or website journeys. QREasy offers a free browser-based option for people who want a simple code without confusing it with a hosted landing page.
Key takeaways
A free vCard QR generator can create a browser-based code with contact details embedded directly in it
Updating embedded contact details means generating a new static QR and redistributing it
A practical guide to building a massage practice website with QREasy, choosing a template, separating plans, adding contact routes, and using QR codes and Wallet cards.
Organize the text, images, links and QR setup for a QREasy Business Card website, understand Free and premium sections, and prepare every customer contact route.
A practical guide to a three-page law firm website with QREasy, including consultation content, contact links, QR routes, Wallet journeys, and plan requirements.
A practical look at service provider website examples, the one-page QREasy Services template, free and premium sections, contact routes, publishing and QR access.
A practical guide to structuring a photographer website, separating template defaults from recommended content, and choosing free or premium sections without confusing contacts, bookings and QR codes.
Build a restaurant contact page and digital menu with QREasy, distinguish native website content from external contact actions, and update the same QR-linked page as your menu changes.
Website Save Contact details and Wallet card behavior are separate from the static contact QR
Contact Wallet cards are free; website-linked Wallet cards require Lite SME or Business
What a Free vCard QR Actually Creates
The basic free contact QR generator in QREasy creates a static vCard QR: the contact details are encoded in the code itself rather than fetched from a webpage after scanning. The basic code is generated in the browser. A recipient uses a compatible phone camera or QR reader to open the contact information, review it, and choose whether to save it.
Unlike a static URL QR, it is not merely a shortcut to a page that may later change. The encoded contact snapshot stays the same until a new QR is generated. For the wider set of sharing formats, explore QREasy’s digital business card creator before deciding which journey fits the people you meet.
How to Create a Static Contact QR in the Browser
Start with QREasy’s browser-based vCard QR tool and enter the contact details you want to share. Check names, phone numbers, email addresses, and any other supported fields for accuracy before generating the code. The generator’s job is to embed the submitted details in a static vCard QR; it does not turn the code into a link to a generic contact page.
Test the complete journey rather than only the graphic. Some phones handle a scanned vCard differently from a browser button, so confirm that the intended recipient can see the details and make the save decision. If you also manage codes for pages, compare the QREasy QR code generators rather than assuming every generator produces the same content.
Open the vCard QR generator in a browser and enter the exact details recipients should receive.
Generate the static code, then scan it with a second compatible phone or reader before publishing.
Place the code where people can reach and scan it, such as on a business card, poster or email signature.
Keep a plain-text contact method available in case a recipient’s device cannot read the code.
Scan this code with your phone camera to open the QREasy digital business card page.
Static Contact QR Versus the Website Save Contact Button
A static contact QR and the website Save Contact button can deliver similar contact information, but they are different interfaces. The static code contains the contact data. The Save Contact button is part of a QREasy website and, when selected, downloads or opens a vCard file using the contact details saved in that website section. A visitor does not scan this button with a camera.
When the website owner edits and saves that contact section, the website button serves the updated details. This does not require a replacement static contact QR unless the owner also wants a separate printed or embedded code to contain those new details. Whether the contact is actually saved depends on device and browser handling and on the visitor confirming the action, so the button is not a one-step automatic save.
Use the static QR when the code itself must carry the details, such as on a poster. Use the website button when the destination is already a QREasy page and recipients should select a visible control instead of scanning a code.
Contact Wallet Cards Versus Website-Linked Wallet Cards
Contact Wallet cards and website-linked Wallet cards should not be grouped together simply because both appear in a phone’s wallet. A Contact Wallet card shares contact data and supports a review-and-save contact journey. Its QR is not the direct website-opening route offered by a website-linked Wallet card. Contact Wallet cards are included in QREasy’s free offering.
A website-linked Wallet card works differently: its QR encodes the website URL, so scanning opens that site in the phone browser rather than running it inside Wallet. It requires Lite SME or Business, so check QREasy plans if this is the journey you need. Google Wallet also includes a Visit Page link for the hosted website.
Wallet generation is server-side, unlike the basic browser-generated contact QR. QREasy’s first one-page website is free, and you can begin with website templates, but adding the website-linked Wallet journey still depends on the eligible plan. Choose Contact Wallet when saving contact details is the goal; choose website-linked when opening the hosted site is the goal.
When to Regenerate a QR After Changing Contact Details
Regenerate a static contact QR when any detail embedded in that QR changes. A changed phone number, email address, name, or organization is part of the encoded snapshot, so the existing code still carries the old value. Generate a new code and distribute or reprint it wherever the old code appeared. Scanning the old code cannot update a contact that has already been saved.
This rule does not apply to every QR. Editing and saving a website’s contact section updates the details served by its Save Contact button without requiring a new static contact QR. Likewise, ordinary content changes on a hosted page can appear at the same website address, so a website-linked Wallet QR that encodes that address does not need replacement solely because the page content changed.
Regenerate the static vCard QR whenever any embedded contact detail changes.
Do not replace a static QR merely because the website’s separate Save Contact section was edited.
Keep a website-linked Wallet QR when the hosted page changes but its URL stays the same.
Keep a static URL QR when content at the same URL is replaced; regenerate only if the encoded URL changes.
How Recipients Scan, Review and Save a Contact
For a static vCard QR, the recipient points a compatible phone camera or QR reader at the code, reviews the contact details presented, and chooses to save them. The QR does not save a contact automatically. Nothing in these flows saves a contact automatically, and there is no NFC tap exchange, CRM matching or contact identification step; the recipient confirms the save.
For a website Save Contact button, the recipient selects the button instead of scanning a page. The browser or device may download or open a vCard file, and the recipient still confirms the action. For a Contact Wallet card, the supported Wallet journey lets the person review and save the contact details. For a website-linked Wallet card, scanning leads to the hosted site in the phone browser.
Before rolling out any format, test with more than one phone and browser available to you. QR reading behavior is not guaranteed to be identical everywhere, and a Wallet path may differ from the basic contact QR path. Keep the choice deliberate: embedded static contact data for a code, a website button for a hosted page, or the Wallet journey that matches the intended next step.
Frequently asked questions
The basic static contact QR is generated in the browser, and QREasy provides free QR tools. Contact Wallet cards are also free. Website-linked Wallet cards are different and require Lite SME or Business, so the free contact QR should not be confused with that paid journey.
A static vCard QR embeds contact details in the code and is scanned with a camera or QR reader. The website Save Contact button is a separate control that downloads or opens a vCard file from saved website details. Editing that website section does not require replacing the static QR.
Only if the changed details were embedded in that static QR. Updating the website contact section and its Save Contact button can serve new details without a new code. If the contact data itself is printed into a static vCard QR, generate and redistribute a replacement.
A website-linked Wallet card opens the hosted website in the phone browser after scanning; the site does not run inside Wallet. A Contact Wallet card instead shares contact data for review and saving. Website-linked Wallet cards require Lite SME or Business.
Get started
Create a static contact QR
Open the free vCard QR generator, enter the details to embed, generate the browser-based code, and test it on a second phone before sharing.
A practical, section-by-section checklist for reviewing a four-page QREasy beauty salon website, including services, images, external enquiries, navigation, QR codes and Wallet connections.