Outlook can save any contact as a .vcf file by opening the People pane, choosing one entry, and selecting File → Save As with the vCard File format, and the resulting file is what other address-book apps call a vCard. That built-in export works, but it ties the export to Outlook itself, runs one contact at a time, and stores whatever formatting quirks your specific Outlook build produces. If you want a clean, RFC 6350-shaped vCard that you generated from the same contact details, with full control over what gets included, a local browser tool can produce the same .vcf without sending the contact data through an Outlook dialog or a remote service. The vCard Generator builds the file from the fields you enter, shows the exact text it will write, and hands you a download link that points to a temporary in-browser blob, so the contact data never leaves the device you are using. This page walks through both paths: Outlook's native save and the local-generator path that often produces a cleaner result.
What Outlook's Built-In vCard Export Does
Microsoft's own documentation walks through a short path for saving an Outlook contact as a vCard file, and the steps have stayed almost identical across Outlook 2016, 2019, 2021, 2024, and the Microsoft 365 versions. Open the People icon in the navigation bar (or press Ctrl+3), pick the contact you want, then go to File → Save As. In the Save as type dropdown, change the selection to vCard File (*.vcf), choose a folder, and click Save. Outlook writes a single .vcf file containing that one contact.
The .vcf that Outlook produces is widely accepted by other mail and address-book applications, including Apple Mail, Gmail contacts (via the web import), and most mobile address books. That portability is exactly why the vCard format exists. RFC 6350 defines it as a portable contact record so a single file can travel between apps without manual reformatting. The IANA vCard Elements Registry maintains the canonical list of properties an importer is expected to recognize.
There are real limits to that built-in path, though. You can only save one contact at a time through the Save As dialog, so extracting a small address book means repeating the same clicks for every entry. The output also follows whatever your specific Outlook build generates, which can include vendor-specific properties some importers ignore but none reject. If your contact data is sensitive, a personal phone, a private email, or a note you would rather not have pass through Outlook's UI, the built-in export still keeps that data inside Outlook's workflow until you save the file.
When the Local vCard Generator Is the Better Choice
There are several common situations where going through Outlook is more friction than it is worth, and where a local generator produces a smaller, cleaner file with the same portability.
- You want to share a contact without opening Outlook, for example sending a .vcf from a personal device where Outlook is not installed.
- The contact data is private and you would rather not route it through the Outlook save dialog, which can cache or sync depending on your account settings.
- You only have a few details to include (a name, an email, a phone) and you do not want to create or edit an Outlook contact entry just to export it.
- The target application expects a tightly written vCard 4.0 record without vendor extensions, and you would like to read the exact text before sending the file.
The vCard Generator handles each of those cases by accepting plain text fields in the browser, escaping characters the vCard grammar reserves (commas, semicolons, backslashes, and line breaks), and emitting a single .vcf file with CRLF line endings. Every step, typing, previewing, downloading, happens in the current tab, and there is no account, no upload, and no remote conversion service involved.
Get a vCard From Outlook Using the Local Generator
The generator's workflow is short, and each step has a specific job in producing a file that imports cleanly.
- Open the vCard Generator in your browser. In a separate Outlook window, open the contact you want to capture (People pane → double-click the entry) so you can copy the relevant fields without retyping from memory.
- Type the full name into the required Name field. The generator keeps the name field mandatory on purpose: a contact file without a formatted name is not a useful portable record. Add any optional fields you want carried over: organization, job title, email, phone number, website, and a note. Empty optional fields are dropped from the output rather than written as blank properties.
- Click Create vCard. The preview pane shows the exact vCard 4.0 text the file will contain, starting with BEGIN:VCARD and VERSION:4.0, including the FN property, every property you supplied, and ending with END:VCARD. Read the preview for spelling, country codes, the email domain, and the website path before you save anything.
- Click Download .vcf. The browser creates a temporary Blob URL and saves the file to your downloads folder. The downloaded file uses CRLF line endings, ends with a final CRLF, and folds any long line to at most 75 UTF-8 octets with a single leading space on each continuation, as RFC 6350 requires.
- Test-import the file in the application you actually plan to use, Outlook itself, Apple Contacts, Google Contacts, or a mobile address book, before distributing it. Import behavior and which optional properties a given app reads can differ, so a real import is the final compatibility check.
Reading the Preview Before You Download
The preview is not decorative. It is the literal byte sequence the .vcf file will contain, displayed so you can proofread it before saving. Three details in the preview are worth a close look.
Escaped punctuation. Names like "Doe, Jane," organizations that contain a semicolon, and notes with multiple lines all use characters the vCard grammar reserves for structure. The generator escapes commas, semicolons, backslashes, and line breaks inside text values so an importer cannot mistake punctuation for property syntax. If your preview shows a backslash before a comma, that is the escape working as intended.
Folded long lines. vCard content lines are measured in UTF-8 octets, not characters, and the format rule limits each physical line to 75 octets before folding. The generator handles that automatically and begins each continuation with one leading space, but the preview is where you can see the fold happen. If you typed a long note in non-ASCII text, the fold may split mid-word; that is still safe because it follows the UTF-8 octet rule and never breaks a Unicode code point in the middle of its encoding.
Empty fields are absent. Optional properties you did not fill in simply do not appear in the preview. The output is intentionally a small, conservative property set (version 4.0, a name, and only the fields you actually entered) rather than a row of empty properties that some importers display as "no value".
Outlook Export vs. Browser vCard: A Quick Comparison
| Aspect | Outlook's built-in Save As | vCard Generator (browser) |
|---|---|---|
| Where the file is built | Inside Outlook on your machine | Inside the browser tab on your machine |
| Contacts per export | One at a time | One record per use |
| Network activity | None for the save itself, but data passes through Outlook | None; typed locally, downloaded as a local Blob |
| Account required | An Outlook or mail profile | None |
| Format version | Generally vCard, exact version depends on Outlook build | vCard 4.0 per RFC 6350 |
| Escaping and folding | Handled by Outlook | Handled automatically, visible in the preview |
| Editable before download | Only by editing the Outlook contact | Yes, the preview shows the exact text |
| Output review | Open the .vcf in a text editor | Read the preview pane directly |
The comparison is qualitative rather than benchmark-driven: both paths produce a portable .vcf file. The deciding factors are usually whether Outlook is available on the machine you are using, how comfortable you are with the data passing through the Outlook dialog, and whether you want to read the exact bytes before saving.
Importing the .vcf Back Into Outlook or Elsewhere
Once the .vcf is on disk, the import path is straightforward. In Outlook, open the People pane, choose File → Open & Export → Import/Export, pick Import from another program or file, select vCard File as the file type, browse to the .vcf, and confirm the destination folder. Outlook will read the FN property as the display name and the other fields you included.
For Apple Contacts, double-click the .vcf and confirm the import. For Google Contacts, use the Import contacts option on the web interface and upload the file. Mobile address books on iOS and Android accept .vcf files through their respective share or import flows. The conservative property set the generator emits is read by all four destinations, though applications differ on which optional properties they surface. A real import is the only way to confirm the exact mapping for your specific app.
If the destination app needs broader coverage or stricter validation, the guide on creating a vCard file that imports cleanly anywhere walks through the same preview-then-download habit with additional considerations for different importers.
When This Method Fits and When It Doesn't
The local generator is built for a single-record export, not for bulk extraction. If you need to export dozens of Outlook contacts at once, the built-in Outlook path or the Import/Export wizard with a CSV intermediate is faster. The generator also does not embed photos, social-profile links, or vendor-specific synchronization extensions. It intentionally emits a small, conservative property set because those extras are the ones most likely to be ignored or rejected by importers. If you need a scannable representation of a short public value, a QR Code tool serves that purpose; this tool's job ends with a downloadable contact record.
For a single Outlook contact whose data you want to convert into a clean, RFC 6350-shaped .vcf without opening Outlook's save dialog or sending the data to a remote service, the workflow is short: type the name, add the fields that matter, read the preview, download, and test-import. The output is plain text and can be opened in any text editor if you want to confirm the exact bytes. It is not a digital identity, a verified signature, or a substitute for consent before sharing someone else's contact information.
Related reading: Create a VCF File Online (Standards-Aligned vCard 4.0).