Cookie preferences
We use cookies for analytics. Privacy Policy You can accept or decline non-essential tracking.
vCard 3.0 vs 4.0, required vs optional fields, photo encoding limits, iOS and Android compatibility, and batch generation for sales teams.
Go to tool
Create a contact-save QR, publish a public card, export VCF, and prepare digital business card assets.
vCard 3.0 is the safe default. It works on virtually every phone made in the last 15 years -- iPhone, Android, even older feature phones. vCard 4.0 adds support for richer data types (multiple languages, more address fields), but older Android versions (pre-8.0) sometimes fail to parse it.
Stick with 3.0 unless you have a specific reason for 4.0 features. vCard QR Generator uses 3.0 for maximum compatibility.
Required (the QR is useless without these):
Recommended (significantly improve the contact entry):
Optional (add only if needed):
Embedding a photo into vCard data encodes the image as Base64 text inside the QR. This dramatically increases QR density -- a 10 KB photo can add 13,000+ characters. The resulting QR code becomes too dense to scan from a business card. Skip the photo for printed codes. For digital-only use (email signature, on-screen display), a small photo (under 5 KB, 100x100px) may work.
For teams of 10+ people, create a standardized template: same company name, same company URL, same formatting. Only change per-person fields (name, title, direct phone, direct email). This ensures consistent branding when prospects save your team's contacts.
Open vCard QR Generator, create a test card with all recommended fields, and scan it on both iPhone and Android before finalizing your template.
This article is reviewed by the Tools Hub editorial team for factual accuracy, practical relevance, and consistency with current product workflows.
Last reviewed:
Practical guide to vcard qr code: formulas, workflow, implementation pitfalls, and a direct execution playbook with Digital Business Card Builder.
mailto URI parameters, URL encoding rules, template vs freeform body strategies, email client compatibility, and QR density limits for print.
smsto vs sms URI formats, iOS and Android message handling, pre-fill best practices, short codes vs long codes, and MMS limitations.
tel URI format rules, country code formatting, mobile-only limitations, fallback strategies for desktop, and call tracking via landing pages.