Generador de Codigos QR vCard Gratis

The vCard format has been around since 1995, but two versions dominate today: 3.0 (defined in RFC 2426) and 4.0 (RFC 6350). Version 3.0 has the widest compatibility. Every major contact app on iOS, Android, Windows, and macOS reads it correctly. It supports name, phone numbers, email addresses, physical addresses, organization, title, URL, and a photo.

Version 4.0 adds useful features like multiple language support per field, a KIND property to distinguish people from organizations, and better handling of social profiles and instant messaging identifiers. However, compatibility is inconsistent. Some Android contact apps handle 4.0 well, while others silently drop unsupported fields. Outlook on Windows has historically been slow to adopt 4.0 features.

For QR codes, version 3.0 is the practical choice. The contact information you typically want to share (name, phone, email, company, title, website) works identically in both versions. The extra features in 4.0 rarely justify the risk of compatibility issues, especially when you cannot predict which phone or app will scan your code.

Not every vCard field behaves the same across platforms. Full name (FN), phone number (TEL), and email (EMAIL) work everywhere. Organization (ORG) and title (TITLE) are supported by all major contact apps. Physical address (ADR) works but displays differently across platforms; Google Contacts may split it into separate fields while iOS keeps it as one block.

Website URL works reliably, but only the first URL is consistently displayed. If you add multiple URLs, some apps show only the first. Notes (NOTE) are supported but some apps truncate long text.

Social media profiles are the most problematic area. vCard 3.0 has no standard field for social profiles, so generators often use X-SOCIALPROFILE or IMPP, which only some apps recognize. If you need to share social links, putting them in the URL or NOTE field is more reliable than using non-standard extensions. Phone number type labels (work, home, cell) are generally respected, but the exact label text may change between platforms.

vCard supports embedding a photo using base64 encoding, which means the image data is converted to text and stored directly in the vCard. A small profile photo (100x100 pixels, JPEG at moderate quality) takes about 4-8 KB, which adds roughly 5,000-11,000 characters to the vCard data. This dramatically increases QR code complexity.

A vCard without a photo might create a Version 5-8 QR code (small, easy to scan). Adding a photo can push it to Version 20-30 or beyond, creating a dense grid of tiny modules that struggles to scan on phone cameras. The practical limit for QR code data is around 2,953 bytes in the most compact encoding. A decent profile photo easily exceeds that. Some generators work around this by linking to an externally hosted photo URL instead of embedding it, but not all contact apps download the linked image.

For QR code-based vCards, the safest approach is to skip the photo entirely. The contact details will save correctly, and the code will scan reliably at a reasonable size. If the photo matters, consider using a URL QR code that links to a digital business card page where the full photo is displayed.

When someone scans a vCard QR code, their phone's default contact app handles the import. On iOS, scanning opens the Contacts app with a preview of all fields, and the user taps 'Create New Contact' or 'Add to Existing Contact'. On Android, the behavior varies by manufacturer and default contacts app, but the flow is similar. Google Contacts, Samsung Contacts, and most third-party apps all handle vCard 3.0 correctly.

For CRM import, vCard files (.vcf) are universally supported. Salesforce, HubSpot, Zoho, and Microsoft Dynamics all accept .vcf imports, either directly or through their contact import tools. If your sales team collects vCards at events, the scanned contacts can go straight from phone to CRM.

One edge case to plan for: character encoding. vCard 3.0 defaults to UTF-8, but some older systems expect ASCII. Names with accented characters, Asian characters, or emoji in the notes field may display incorrectly on legacy systems. Stick to UTF-8 and test with the specific CRM or contact app your team uses.