A vCard contact file (.vcf) is the standard format iPhone accepts when you tap an attached file from Mail, receive it through AirDrop, or open one from the Files app. The vCard Generator produces that exact file in your browser by collecting the contact details you enter, escaping the punctuation vCard 4.0 treats as structural, and folding long Unicode lines so importers like iOS Contacts can reassemble them cleanly. Because every step happens locally in the page — no upload, no account, no remote service — the contact record stays private until you intentionally share the downloaded file. The resulting file is plain text that any editor can open, and it follows the core serialization rules in RFC 6350, the IETF specification that defines the vCard 4.0 format. iOS Contacts is one of many address-book applications built to read these files, and it interprets each property such as FN (formatted name), ORG (organization), TITLE, EMAIL, TEL, and URL into the matching field on the new contact card. Once the .vcf reaches the iPhone, a single tap adds it as a new contact, and the structured properties map directly to the matching fields in iOS Contacts.
What the vCard Generator Does for iPhone Users
Most iPhone contact workflows assume the file already exists — someone else sent a .vcf, or iCloud exported one. The generator covers the case where the file does not yet exist and you want to create it yourself without installing software, signing up for an account, or pasting contact data into a remote web form. You type the details into a form, the page assembles the vCard 4.0 text record, and a download link offers the .vcf straight from a temporary browser Blob. The IANA vCard Elements Registry lists the standardized properties the generator emits, and the RFC 6350 specification defines the serialization rules those properties follow.
Because the assembly happens in your current browser session, the contact details never leave the device. Closing or reloading the page discards the entered values and the download URL. This makes the tool a reasonable choice when the contact is private, when the file is for one-off use, or when you simply need a portable record faster than opening a desktop contact manager.
Build the .vcf File With vCard Generator
Creating a contact file that iPhone will accept without complaint is a three-action workflow on the page: enter, preview, download. Each step keeps the contact values visible so you can correct a typo before the file reaches an importer.
- Enter the required full name. The page marks the name field as required because a vCard without a formatted name is not a useful portable record — most importers will reject the file or display an empty card.
- Add any optional details that belong on the card. Useful additions include an organization, a job title, an email address, a phone number with the appropriate country code, a website, and a short note. Empty fields are omitted from the output rather than appearing as blank properties.
- Select Create vCard and read the preview. The preview pane shows the exact vCard 4.0 text the file will contain, so confirm the spelling of the name, the country code on the phone number, the email domain, and the website path before continuing.
- Download the .vcf file. The download link is a temporary browser Blob assembled from the preview, which keeps the contact details local to the device. Save the file with a recognizable name such as jane-doe.vcf so it is easy to find when you transfer it to the iPhone.
After the download, open the .vcf in any text editor to confirm the file begins with BEGIN:VCARD, declares VERSION:4.0, contains the FN property with the formatted name, includes the optional properties you supplied, and ends with END:VCARD. That plain-text inspection is the fastest sanity check before moving the file.
Move the .vcf File Onto Your iPhone
Once the .vcf is on a computer or in a cloud account, the iPhone offers several import paths. Each one treats a single tap on the file as an invitation to add a contact, so the choice is mainly about where the file already lives.
- AirDrop from a nearby Mac or another iPhone: the receiving iPhone prompts to accept the file, then opens it as a contact card.
- Mail attachment: email the .vcf to yourself, then tap the attachment in the iPhone Mail app.
- Messages: send the .vcf to your own iMessage or SMS thread and tap the bubble.
- Files app: place the .vcf in iCloud Drive, On My iPhone, or a third-party cloud folder that the Files app can reach, then tap or long-press the file.
- Safari download: visit iCloud.com or any site that hosts the file, and download it directly in Safari — the file then appears in the Downloads location.
AirDrop and the Files app work without an internet connection for the transfer itself; the Mail, Messages, and Safari paths require the iPhone to be online to receive the file. All five routes produce the same import prompt on the iPhone, so the choice is whichever is fastest from the device that already holds the .vcf.
Import the vCard Into iPhone Contacts
After the .vcf is on the iPhone, the import is a single tap from the receiving app. Tap the file in Mail, accept an AirDrop prompt, or open it from the Files app. iOS previews the contact card and offers a Create New Contact button; for files that contain multiple vCards in one document, the prompt becomes Add All Contacts or a similar option to import the whole set.
The new entry appears at the top of the iPhone Contacts list, and each vCard property maps to a labeled field:
| vCard Property | Purpose | iPhone Contacts Field |
|---|---|---|
| FN | Formatted name (required) | Display name on the contact card |
| ORG | Organization name | Company |
| TITLE | Job title | Job Title |
| Email address | ||
| TEL | Phone number | Phone |
| URL | Website | Website |
| NOTE | Free-form note | Notes |
If the .vcf contains a phone number with a country code, iPhone stores it as-is and offers to dial with the appropriate international prefix when called. Email addresses become tappable links in the contact card, and website entries open in Safari when tapped.
What the Generator Handles So Importers Don't Trip
When a .vcf is assembled by hand, four details are easy to miss and each one can prevent iPhone Contacts from importing the file cleanly. The generator handles them automatically:
- Text escaping. vCard 4.0 treats commas, semicolons, backslashes, and line breaks as structural delimiters inside text values. A name like Doe, Jane or an organization containing a semicolon would otherwise be split into separate property values. The generator escapes each character that the spec marks as significant.
- UTF-8 octet line folding. vCard content lines have a length rule measured in UTF-8 octets, not characters, with a default cap of 75 octets before a continuation. The generator folds long lines and begins each continuation with a single space, and it processes complete Unicode code points so an emoji or a multibyte character is never split in the middle of its UTF-8 encoding.
- CRLF line endings. The downloaded file uses CRLF line endings and ends with a final CRLF, matching the line-terminator rule in RFC 6350. Importers on different platforms handle mixed line endings inconsistently, so a uniform CRLF file is the safest portable form.
- Input validation. Website entries must be public HTTP or HTTPS URLs — embedded usernames and passwords are rejected. Other contact fields reject unsupported control characters and have practical length limits. Line breaks inside a note are encoded within the property value rather than allowed to inject an additional vCard property.
The generator intentionally emits a small, conservative property set rather than vendor-specific photo, social-profile, or synchronization extensions. That scope keeps the file compatible with the widest range of address-book applications, including iOS Contacts.
Verify and Troubleshoot the Import
The final compatibility check is a real import. After downloading the .vcf, transfer it to the iPhone using one of the methods above and tap it. If the contact card opens with the expected name and fields, the file is portable enough to share with confidence. If anything looks wrong — a missing email, a phone number with a stray comma, a note that got truncated — return to the generator, edit the input, and download a new .vcf rather than trying to patch the existing file by hand.
Import behavior and supported optional properties can differ between applications, so the same .vcf may render slightly differently in iOS Contacts, Google Contacts, and Outlook. A test-import in the destination that matters most is the closest thing to a guarantee. For a closer look at building a vCard that travels well across address-book apps, the guide on creating a vCard that imports cleanly anywhere walks through the same conservative property set from a different angle.
The generator does not claim that an email address or phone number belongs to a real person; it serializes the values you provide. It is also not a digital identity, a verified signature, or a substitute for consent before sharing someone else's contact information — keep that distinction in mind when distributing the resulting .vcf.