How to Create a vCard QR Code and Check Every Contact Field

To create a vCard QR code, enter the contact details you want to share, generate the image and check the contact a recipient actually saves. A pattern that scans successfully can still contain a misspelled email, a misplaced surname or an address that imports poorly. Approve the saved contact as well as the printed image.

This tutorial follows the current vCard generator and focuses on field accuracy. If you have not decided whether your card should save contact details or open a webpage, start with the vCard versus website comparison. Once you choose a direct vCard, the information becomes part of the QR pattern and cannot be edited on printed copies.

Prepare a short contact record before opening the generator

Write down the details a new contact needs after meeting you. For a freelancer at a trade show, that might be a name, company, work email and portfolio. For a representative who arranges follow-up calls, the phone number may be the most useful field. These are illustrative workflows, not claims about conversion rates.

Decide which information is suitable for public distribution. A card may be photographed, forwarded or left on a desk. The code does not hide its contents. Use a business contact route you intend to publish, and leave out a home address or personal number when it is unnecessary. More fields also mean more encoded text, so adding a full biography is not a substitute for a useful profile page.

Keep an approved source record separate from the design file. If a colleague makes the artwork, send that record along with the spelling and capitalisation you want. This avoids a designer retyping a number from an old card or copying a job title that has already changed.

Fill the fields according to their actual purpose

The form supports a first name, last name, company, job title, one phone number, email, website and one address box. First name is required. Other fields can be left blank when they are not needed. Do not use a spare field for unrelated information just because it fits visually.

The first and last name fields are separate for a reason. If you put the complete name into First name and repeat the surname in Last name, the saved record can repeat it too. Display and sorting preferences differ between contact apps, so check the stored fields rather than assuming a surname-first display is an error. For a name that does not fit a simple two-part convention, test the exact representation the person wants before printing.

The current phone field is written with a mobile label. Enter one number, not a list separated by commas. A fixed office line may therefore receive an unsuitable label in the recipient's app. If you need several numbers with different labels, use a contact page or a tool whose contact fields meet that requirement. Putting a second number in the company field makes the record harder to use.

For cards shared across the United States, United Kingdom, Canada and Australia, verify the international dialling form with the owner of the number. Do not assume an overseas recipient's phone will infer the correct country from a local number. Extensions and special dialling instructions deserve their own test; a number that looks familiar on paper may behave differently when tapped.

Treat the address box as a limited field

This generator provides one address box. It does not offer separate inputs for street, city, region, postal code and country. Its current encoder puts the entered text in the street-address component of the vCard. That can preserve readable text without producing the structured address your contacts app or mapping app expects.

If a visitor needs directions to a studio or office, inspect the imported address and try the map action on a test device. Do not assume that a readable multiline address guarantees correct navigation. A public location page can be more suitable when visitors need opening hours, access instructions or a specific entrance. You can put that page in the website field or choose a website QR instead.

Leave the address blank for a professional who works remotely and does not receive visitors. Removing an unnecessary field reduces both public information and visual density. It also prevents someone interpreting a mailing address as a place they can visit without an appointment.

Generate a plain version before adding decoration

Start with a simple design so you can separate contact-data problems from artwork problems. Use the dedicated form or the embedded generator on the business-card page:

1. Enter the approved fields, checking each against the source record.
2. Select Next: Design and inspect the preview.
3. Begin with dark modules on a light background and leave the logo out of the first version.
4. Keep the clear border around the pattern intact.
5. Select Next: Download and choose SVG, PNG or JPEG according to your layout workflow.
6. Name the file so you can identify the person and contact-record version later.

An SVG remains vector artwork when used in a compatible design application. A PNG is a raster image and needs enough resolution at the intended output size. Neither format guarantees that a small or obstructed code will scan. The print-size guide explains why the actual pattern, placement and finished proof matter more than a universal minimum size.

Do not crop away the clear border when fitting the image into a card template. DENSO WAVE specifies a quiet zone of four modules around a QR code; a module is one small square in the pattern. Keep surrounding captions and graphics outside that area. Review the complete layout after adding the logo, background and other artwork, rather than testing only the original standalone image.

Check the decoded text before checking the contact app

A direct vCard contains labelled contact text. It is different from a website code that opens a hosted contact page. The generator currently uses vCard 3.0. A minimal fictional example looks like this:

BEGIN:VCARD
VERSION:3.0
N:Example;Alex;;;
FN:Alex Example
URL:https://example.com
END:VCARD

The structured name line and display-name line serve different purposes. In this example, Example is the surname and Alex is the given name. The name and domain are placeholders for documentation; replace them with your own approved information before producing a real card. Email is optional and omitted from this minimal example.

You do not need to write these lines yourself. If a scanner shows plain text, use it to check whether the expected fields are present. A contact app failing to offer an import action is a different problem from a camera failing to read the QR pattern. The vCard specification describes the format, but it does not guarantee identical behaviour from every scanner or contacts app.

For an automated check on October 7, 2026, we rendered and decoded the generator's vCard output with accented text, punctuation and a multiline address. The software check verified that the decoded payload matched the encoder output and that the expected escaped name, organisation and address fields were present. This was a software test of the generator, not a physical print test or proof of successful import on every phone.

Test the contact that a recipient would actually save

Use a clearly labelled test record so an existing contact does not hide a problem. A phone may merge information with a record already in its address book, making it harder to tell what came from the code. Check your test with permission on the devices you have available and record the device, scanner and contact app used.

The acceptance check has three stages. First, confirm that the pattern decodes. Second, follow the offered contact action and review the preview. Third, save the test record and open it from Contacts. Verify that the final saved fields match the approved source. A correct preview alone does not show how the app stores or labels every field.

Check accented names, compound surnames, company punctuation and line breaks deliberately. Open the website from the saved record. Inspect the email recipient without sending a message. Inspect the phone number without making an unsolicited call. For a live business card, confirm any actual call or message test with its owner beforehand.

Where possible, use both an iPhone and an Android phone representative of your audience. General camera support for QR codes does not establish vCard-import compatibility. Apple's QR instructions explain how to scan a code with the camera or Code Scanner; the next action still depends on the content and available software. If a device only displays text, provide a readable phone number or website on the card as a fallback.

Diagnose failures by the stage that failed

Avoid redesigning the code when the underlying issue is a misspelled field. Likewise, repeatedly editing a phone number will not fix glare on a laminated proof. Use the failed stage to choose the next check:

For a pattern-level failure, follow the broader QR code not scanning checklist. For a contact-field failure, correct the source record, regenerate and repeat the import check. Replace the QR image in the artwork too; correcting the form does not change an SVG you already downloaded.

Approve the physical proof and plan for updates

Print one finished proof at its intended size, using the actual layout and material where possible. Scan it under the lighting and distance expected during use. Keep readable contact information beside the QR code, and use a caption such as “Scan to save contact details” so the invitation is clear.

Record what passed: source-record version, artwork filename, printed size, devices tested and approval date. This is especially useful for a team ordering cards for several staff members. Test each person's code; one successful card does not verify another person's email or phone number. Check that names printed on the card and names encoded in the image belong to the same person.

When a role, number or address changes, a printed direct vCard continues to contain the previous text. Updating your own contact record does not update copies someone else saved. Keep a process for replacing artwork and withdrawing outdated stock. If frequent changes make that impractical, consider a stable website destination you maintain.

A direct contact import also does not create a pageview on your website. Downloads from this generator, recipient scans and saved contacts are separate actions. The QR campaign measurement guide explains what website analytics can measure when the destination is a page you control. Choose that journey intentionally instead of promising scan statistics from a direct vCard.

Sources and format notes

• RFC 2426: vCard 3.0, the format currently emitted by this generator. It is an older specification, superseded by vCard 4.0.
• DENSO WAVE: determining the QR code area, including the four-module quiet zone.
• Apple: scan a QR code with iPhone or iPad, for the general scanning workflow rather than a guarantee about contact import.

Ready to make the record? Open the vCard creation form, keep the information focused and approve both the contact and its printed proof.