vCard QR Code
Reader & Decoder

About vCard QR Codes

A vCard QR code encodes contact information using the vCard (Virtual Contact File) format, an international standard defined in RFC 6350. When scanned, the data can be directly imported into contacts apps on smartphones and computers.

vCard QR codes are widely used on business cards, conference lanyards, email signatures, professional networking platforms like LinkedIn, and event badge systems.

Fields a vCard QR Code Can Store

• Full name and display name
• Job title and organization
• Phone numbers (multiple — mobile, work, home)
• Email addresses (multiple)
• Physical address (street, city, country)
• Website URL
• Birthday
• Notes and custom fields
• Profile photo (Base64 encoded — version 3.0+)

vCard Versions

QR codes commonly encode vCard version 2.1, 3.0, or 4.0. Our decoder handles all three versions. Version 4.0 is the most feature-rich but least widely supported by older contact apps.

Business Card QR Code Best Practices

vCard QR codes on business cards have become standard practice in many industries. They allow recipients to add contact details to their phone with a single scan — eliminating manual data entry and typos.

Use Cases by Industry

• Sales & business development: Immediate contact exchange at meetings and trade shows
• Healthcare: Patient intake forms, doctor's contact details on referral cards
• Real estate: Property listing agent cards with direct dial and email
• Events & conferences: Attendee badges with sponsor and speaker contact details

Security Considerations

vCard QR codes typically don't pose the same direct security risks as URL QR codes since they don't initiate browser navigation. However, malicious vCards could potentially attempt to exploit vulnerabilities in contacts app parsers — a rare but documented attack vector. Always verify the source of a QR code before adding contact details from unknown sources to your phone's address book.

Reading a vCard Line by Line

The vCard format looks intimidating at first glance. Once you see the structure, it becomes obvious. A typical decoded vCard 3.0 block looks like the example below.

BEGIN:VCARD
VERSION:3.0
N:Smith;Alice;;;
FN:Alice Smith
ORG:Acme Corp
TITLE:Product Manager
TEL;TYPE=WORK,VOICE:+1-415-555-0198
EMAIL;TYPE=INTERNET:[email protected]
URL:https://acme.example/alice
ADR;TYPE=WORK:;;123 Market St;San Francisco;CA;94103;USA
END:VCARD

The N field uses the order "Surname;First;Middle;Prefix;Suffix" with semicolons as separators. The FN (formatted name) is what shows up in most address books as the display name. The TEL and EMAIL lines allow type markers (WORK, HOME, CELL, VOICE) so the receiving device knows which icon to show.

When our decoder parses a vCard, each of these fields is extracted into a labeled, readable result. You still see the raw vCard underneath if you need to copy and save it as a .vcf file to import into your contacts app.

Why vCard QR Codes Fail to Import

If a decoded vCard refuses to add cleanly to your phone's contacts, the problem is almost always one of four things. We have seen each of these hundreds of times in support requests.

• Missing VERSION line. Without VERSION:2.1, VERSION:3.0, or VERSION:4.0 immediately after BEGIN:VCARD, most address books reject the whole block.
• Wrong line endings. The vCard specification requires CRLF line endings. QR generators that output LF-only can produce files that look fine to humans but fail strict parsers.
• Photo encoded in the wrong version. A base64 PHOTO field belongs in vCard 3.0+. Dropping it into a 2.1 card breaks older iOS contacts imports.
• Unescaped special characters. Commas, semicolons, and backslashes inside a name or address must be escaped with a backslash. "Smith, Jr." should be written as "Smith\, Jr.".

If you run into any of these, the raw vCard text displayed by our decoder is the place to start debugging. Copy it, paste into a text editor, and you can see the exact line that breaks.

vCard vs MECARD vs hCard

Three formats compete for space in the contact-QR ecosystem. Knowing which one you are looking at prevents confusion when a scanned QR does not behave as expected.

• vCard is the international standard (RFC 6350). Full-featured, supports photos, notes, multiple phones and emails, and certificates. Works natively on iOS and Android.
• MECARD is a compact format created by DoCoMo in Japan. Starts with MECARD: instead of BEGIN:VCARD. Fits more data into a smaller QR code but supports fewer fields. Some Android phones and most modern QR scanners recognize it.
• hCard is an HTML microformat used on websites to mark up contact details. It is rarely encoded inside QR codes but occasionally shows up when a QR points to a webpage with embedded hCard markup.

Our decoder automatically detects all three formats and normalizes the output. You see the contact in a consistent, readable layout regardless of which flavor the QR code uses underneath.

Designing a vCard QR Code That Actually Scans

If you are generating vCard QR codes to print on business cards, three decisions make or break scan reliability once the card is in someone's hand.

• Use error correction level M or higher. Level L looks cleaner but fails the moment the card picks up a scratch or coffee stain.
• Print at 2 cm square minimum. Smaller QR codes on business cards are the top source of scan failures. If space is tight, drop the photo and notes field to reduce the data payload so the code simplifies.
• Contrast over brand colors. Light blue on white looks elegant and scans poorly. Pure black on pure white is boring and scans every time. A good middle ground is a dark brand color on white, tested under phone flash.

Once generated, drop a test scan through our decoder before sending the card to print. If we can decode it cleanly, real-world phone cameras will too.