Convert vCard Version: 2.1, 3.0 and 4.0 Differences and Conversion Guide

Introduction

Version incompatibility is the number one technical issue in VCF file work. For example, an Android phone exports vCard 2.1, iCloud rejects it because it expects 3.0, and your CRM wants 4.0 for UTF-8 support. Understanding the exact differences between the three versions and knowing how to convert vCard version files is therefore essential for anyone who works with contacts across platforms.

This guide provides the complete property-by-property syntax comparison, working conversion steps for every direction (2.1 to 3.0, 3.0 to 4.0 and downgrade paths), and a platform compatibility table so you know exactly which version to target. We have been converting vCard files across every version at Univik since 2013.

If you are unsure whether VCF and vCard are the same format (they are), see our VCF to vCard guide for the full explanation of the naming difference and when conversion is actually needed. For a broader overview of when and why you actually need to convert VCF files (including encoding, splitting and merging scenarios beyond version changes), see our VCF to vCard compatibility guide.

Property Syntax Differences: 2.1 vs 3.0 vs 4.0

The three versions look similar at first glance, but the syntax rules are different. Here is the same contact written in each version:

Which Version Do You Need?

Convert vCard 2.1 to 3.0

This is the most common conversion because Samsung phones and older Android devices export vCard 2.1, but iCloud and Google Contacts work best with 3.0. If you are importing contacts exported from a Samsung phone into iCloud, this is the conversion you need.

Command-line shortcut (Linux/Mac): For a quick conversion of a file with ASCII-only contacts (no quoted-printable text), use sed:

sed -e 's/VERSION:2.1/VERSION:3.0/g' -e 's/;CHARSET=UTF-8//g' -e 's/ENCODING=BASE64/ENCODING=b/g' contacts.vcf > contacts_v3.vcf

This handles the VERSION and ENCODING changes but does not convert bare type parameters or decode quoted-printable text. For files with non-Latin characters or complex properties, use a dedicated converter tool or open the VCF file to inspect the properties first.

Convert vCard 3.0 to 4.0

Less common, but still needed for CardDAV servers and some modern CRM APIs that require the latest specification.

Downgrade vCard 3.0 to 2.1

This conversion is rarely needed, but some legacy systems and older industrial scanners still require vCard 2.1.

Encoding: The Hidden Conversion Issue

To check if your VCF file contains quoted-printable encoding, search for “ENCODING=QUOTED-PRINTABLE” or look for sequences of =XX in contact names. If these are found, then you need a tool that properly decodes QP text during conversion. A simple find-and-replace in a text editor is not enough for these files because it will leave the encoded sequences as literal text.

Platform Compatibility Table

“Partial” means the platform will import the file but may drop some properties or display formatting issues. Therefore, for the safest results, always convert to the version marked “preferred” for your target platform before importing.

Common Problems and Fixes

Frequently Asked Questions

Can I just change the VERSION line without changing anything else?

For some lenient platforms (Google Contacts, Android), changing only the VERSION line may work because their parsers accept mixed syntax. However, strict platforms like iCloud will reject a file that declares VERSION:3.0 but uses vCard 2.1 syntax. So for reliable results, always apply all the syntax changes for the target version.

Which vCard version should I use for maximum compatibility?

vCard 3.0. It is accepted by every major platform (iCloud, Google, Outlook, Android, Mac, Thunderbird) and supports UTF-8 for international characters. vCard 2.1 is only needed for legacy systems and vCard 4.0 has limited support on some platforms.

How do I check what version my VCF file is?

Open the VCF file in a text editor and look for the VERSION property inside the first BEGIN:VCARD block. It will say VERSION:2.1, VERSION:3.0, or VERSION:4.0. If different contacts in the same file have different versions (which can happen after merging), you need to standardize them all to the same version.

Can a single VCF file contain contacts with different versions?

Technically yes, since each BEGIN:VCARD block has its own VERSION line. However, most platforms expect all contacts in a file to use the same version. Mixed-version files cause unpredictable import behavior. If you have a mixed file, standardize all contacts to one version before importing.

Why does Samsung export vCard 2.1 instead of 3.0?

Samsung’s One UI Contacts app has historically used vCard 2.1 for backward compatibility with older devices. This is a Samsung-specific behavior, not an Android standard (Pixel phones export 3.0). For Samsung-specific export details and workarounds, see our export Samsung contacts to VCF guide. The simplest fix is to import the Samsung VCF into Google Contacts and re-export, which produces a clean vCard 3.0 file.

Conclusion

Last verified: February 2026. Syntax differences verified against RFC 2426 (vCard 3.0) and RFC 6350 (vCard 4.0). Platform compatibility tested on iCloud (iOS 18, macOS 15), Google Contacts, Samsung Galaxy S24 (One UI 6.1), Pixel 9 (Android 15), Outlook 2024, Thunderbird 128, and Zoho CRM.

To convert vCard version files, the most common need is upgrading from 2.1 to 3.0: change the VERSION line, convert bare type parameters to TYPE= syntax, remove per-property CHARSET and ENCODING declarations (while properly decoding quoted-printable text), and update photo encoding from BASE64 to b. vCard 3.0 is the recommended target for maximum platform compatibility. For files with non-Latin characters, use a dedicated converter tool rather than manual text editing to avoid encoding corruption.