Introduction
Got a PST file full of Outlook contacts you need to move somewhere — Android, Gmail, a new CRM, or just a portable backup that doesn't require Outlook? VCF is how you do it. Every contacts app on the market reads vCard files natively: Google Contacts, iPhone, Android, macOS, Salesforce, HubSpot — all of them.
This guide covers the fastest path to convert PST to VCF, what Outlook's built-in tools miss (and why that matters if photos are involved), and how to get your contacts imported wherever they need to go. I've run this process on archives ranging from a few dozen contacts to tens of thousands — there are a few things worth knowing before you start.
What Is a VCF File? (And What It Actually Holds)
VCF stands for Virtual Contact File. It's the file format behind vCards — the open standard for contact data. Open one in a text editor and you'll see plain text starting with BEGIN:VCARD and ending with END:VCARD. Every contact is its own block.
A VCF contact block can hold:
- Full name (first, last, middle, prefix, suffix)
- Email addresses — multiple, with labels (work, home, other)
- Phone numbers — multiple, with type labels (mobile, work, home)
- Mailing address
- Organization and job title
- Birthday
- Contact photo
- Notes
- Website URL
- Categories and tags
For vCard versions, I consistently reach for 3.0. It's the most widely adopted standard, handles UTF-8 for international characters without issue, and works across virtually every platform. Version 4.0 is technically more capable — but in practice, adoption is still patchy. Several apps I've tested quietly discard 4.0-specific fields on import, without any warning, and you only find out when you check individual records afterward. Unless you have a specific reason to need 4.0's extended fields, 3.0 avoids the guesswork.
The key difference from PST: a PST file is a container — it holds emails, calendars, contacts, and tasks all in one place. A VCF file holds contact records only. When you convert PST to VCF, you're pulling out just the contacts folder and writing it into a portable, open format any app can read.
| Feature | PST | VCF |
|---|---|---|
| Platform support | Windows / Outlook only | All platforms |
| Contains | Emails, contacts, calendars, tasks | Contacts only |
| Photos preserved | Yes (binary format) | Yes, when properly converted |
| Human-readable | No (binary) | Yes (plain text) |
| File size | Can be very large (GBs) | Lightweight, text-based |
| Import anywhere | Outlook only | Any contacts app |
When Do You Actually Need to Convert PST to VCF?
Platform migration is the most common trigger — moving from Outlook to Google Workspace, setting up a new phone, or bringing contacts into a CRM. In my experience, VCF is the format that virtually every destination accepts without complaint. If you've tried exporting from Outlook before and hit compatibility issues at the destination, this is usually why.
Switching to Apple? VCF is the only practical path into iCloud Contacts. Android is even simpler: drop the VCF file onto the device and the contacts app imports everything in one go, without needing any account setup or syncing step in between.
CRM migrations work the same way. Salesforce, HubSpot, and Zoho all import VCF files directly. If your sales team's contact history lives in a PST archive and you're moving to a CRM, VCF gets you there without rebuilding records by hand.
There's also the simpler case: you need a portable backup of your address book, or you need to share contacts with someone who isn't on Outlook. VCF handles both — it's lightweight, plain text, and opens in anything.
Why Outlook's Built-In Export Falls Short
Outlook does let you save contacts as VCF, but there's a real limitation: it's one contact at a time. The File → Save As method on an open contact record works fine if you need three or four contacts — but when you're dealing with hundreds, it becomes impractical fast.
The bulk option Outlook offers — File → Open & Export → Import/Export → Export to a file — exports to CSV, not VCF. That's a spreadsheet, not contact cards. And CSV drops photos entirely.
My first big migration, a 400-contact job, taught me this the hard way. Outlook's wizard showed everything looking right — all the headshots, emails, the lot. The CSV output looked fine too. No warnings, no errors. I only caught the problem when I randomly opened a contact in Google Contacts and noticed the photo field was blank. By then, I'd imported the whole batch. That was a frustrating afternoon. CSV just can't carry binary data, and the export won't tell you — it silently strips photos every single time. If your contacts have photos that need to survive, don't go through CSV.
Field mapping is a separate problem. Outlook's CSV headers don't map 1:1 to vCard properties. On my first attempt converting that CSV to VCF manually, every contact's Business Phone landed in Other Phone on import. Nothing flagged it. The contact list looked complete until I started checking individual records.
- No bulk VCF export: The native Save As method is single-contact only. No batch option exists.
- CSV strips photos: Binary data like contact photos can't be stored in CSV — they're always dropped silently.
- Field mapping errors: CSV column headers don't map cleanly to vCard properties without manual correction.
- Notes often don't survive: The Notes field and custom Outlook fields are frequently dropped or truncated in CSV-to-VCF workflows.
How to Convert PST to VCF (Fastest Method)
For anything beyond a few individual contacts, a dedicated converter reads the PST directly and outputs VCF — without the field mapping and photo issues that come with Outlook's native tools.
When I'm dealing with more than a handful of contacts — especially when photos are non-negotiable — I typically reach for MailExel. What makes it work well for this, in my experience, is that it reads the PST directly and embeds photos as base64 in the VCF's PHOTO property. That's the step most free tools skip entirely. I've put it through large archives and it's been consistently reliable — no dropped photos, no fields landing in the wrong place.
To follow these steps, you'll need the software installed. If you haven't set it up yet, download it below — installation takes about a minute, then come back and pick up from Step 1.
Launch the application. Use the Add Files option to bring in your PST file — or several, if you have archives from different accounts or time periods. Loading them together is much more efficient than running separate jobs for each. Once added, everything appears in the main panel, ready for scanning.
Once files are added, the software automatically scans all content in the PST — emails, contacts, calendars, tasks, notes. Nothing required on your end. On most archives this finishes in a couple of minutes. Larger PST files take proportionally longer.
Before you run the full export, check the preview panel. Your Contacts folder should appear with a record count next to it. Spend about 60 seconds here — it's worth it.
On a recent job I caught a contacts sub-folder in the preview I hadn't accounted for — over 200 records sitting separately from the main Contacts folder. Without checking, I would have exported only part of the address book. Spotting it in the preview was a ten-second fix. Catching it after a completed run would have meant starting over.
In the output settings, choose vCard / VCF as the target format. Set a destination folder that's easy to find later. If a version option is available, pick vCard 3.0 — maximum compatibility across Google Contacts, iPhone, Android, and CRMs. Choose one combined VCF file over individual files per contact; that's what most platforms prefer for bulk imports.
Start the export. The tool processes the contacts from the PST and writes the VCF output to your destination folder, preserving all standard fields including photos and notes. A PST with a few thousand contacts usually wraps up in under five minutes. The output file imports directly into any contacts app — no extra steps needed.
How to Import VCF Into Your Contacts App
Okay, VCF file in hand? Getting it into your target platform is surprisingly quick — usually just a couple of minutes. Here's how it breaks down for the major apps:
Google Contacts:
- Go to contacts.google.com
- Click Import in the left sidebar
- Choose your VCF file and click Import
- Contacts appear immediately in your Google account
iPhone (iCloud Contacts):
- Email the VCF file to yourself or save it to iCloud Drive
- Tap the VCF file on your iPhone
- Tap Add All Contacts when prompted
Android:
- Copy the VCF file to the device via cable, Google Drive, or email
- Open the Contacts app
- Menu → Import → select the VCF file from storage
macOS Contacts:
- Open the Contacts app
- File → Import
- Select your VCF file — contacts are added immediately
Outlook (reimporting or a different account):
- File → Open & Export → Import/Export
- Select Import a vCard file (.vcf)
- Browse to your VCF file and open it
The Free Manual Method (For Small Contact Lists)
If you only need a handful of contacts and Outlook is installed, the built-in Save As route is the quickest option available.
Open Outlook, switch to the People view, double-click a contact, then File → Save As. The default save format is .vcf. Pick a location and save. Repeat for each contact you need.
For a slightly larger set, Forward as Business Card moves faster: select multiple contacts in the People view while holding Ctrl, then Home → Forward Contact → As a Business Card. Outlook creates a draft email with each contact as a VCF attachment. Save each attachment to disk instead of sending.
Neither method scales. For anything past 20 or 30 contacts, the time spent doing this manually is more than running a dedicated converter. Worth noting too: both approaches are Windows-specific. If you're on Outlook for Mac, the Save As path is similar but the Import/Export wizard behaves differently, and many third-party PST tools are Windows-only.
There's a third free route if you need a single merged VCF file but only have Outlook available: export contacts to CSV from Outlook (File → Open & Export → Import/Export → Comma Separated Values), import that CSV into Google Contacts, then re-export from Google Contacts as VCF. Google outputs one combined file. It's a three-step workaround and photos won't survive the CSV step, but it does produce the merged format phones and CRMs prefer.
Common Problems and How to Fix Them
A few issues come up consistently on PST-to-VCF jobs. Watch for these before you start.
Contact photos vanish.
Classic one, and it almost always points back to Outlook's CSV export. CSV just can't handle binary data — photos
get silently stripped every single time. The only real fix is using a converter that reads the PST directly and
embeds photos as base64 in the VCF's PHOTO fields. It's the only method I've found that actually works reliably.
International names or characters look garbled after import.
Encoding mismatch. The VCF should be saved in UTF-8. Older Outlook versions export vCard 2.1 with Quoted-Printable
encoding, which some apps misread. Open the VCF in a text editor — if you see strings like =D0=9A=D0=B8=D1=80 where
names should be, the file needs re-encoding. A converter set to output UTF-8 vCard 3.0 avoids this entirely.
Fewer contacts in the output than expected.
Two common causes: the PST was open in Outlook during conversion (a running instance locks the file — close Outlook
first before you start), or the tool only grabbed the top-level Contacts folder and missed sub-folders. The preview
panel shows all discoverable folders with counts. Check it before you run.
Phone numbers landing in the wrong field after import.
This is a type label mismatch — "Business Phone" in Outlook exports as TEL;TYPE=WORK in the VCF, but some apps read
that differently on the way in. I've seen mobile numbers end up under Home and work numbers under Other after an
otherwise clean import. Check a few records after the conversion. If numbers are in the wrong slots, look for a type
label setting in your converter's output options.
Notes and custom fields not appearing in imported contacts.
Custom Outlook fields have no equivalent in the vCard spec — they'll be lost in any conversion, no workaround.
Standard Notes fields should come through intact. If they don't, the converter may not be writing the NOTE property
to the output file.
Thinking about using a web-based converter?
PST files contain private contact data — phone numbers, email addresses, organization details. Uploading to an
unverified third-party server creates a privacy problem that's hard to undo. Many services retain uploaded files or
have unclear data retention policies. For anything sensitive, use a local tool that processes files on your own
machine.
Before you hit start, here’s a short checklist worth running through on every PST job:
- Close Outlook before you start — a running instance locks the PST file.
- Work with a copy of your PST, not the live file.
- Check the preview panel and confirm your contacts folder count before running.
- Set the output to vCard 3.0 for broadest compatibility.
- After import, spot-check a few records: photos intact, phone labels in the right fields.
- Keep the original PST. The converter writes a new file and never modifies the source.
Frequently Asked Questions
Can I convert PST to VCF without Outlook installed?
Yes — a dedicated converter reads the PST file directly without needing Outlook on the machine. That's one of the main advantages over the built-in Save As method. It means you can process archived PST files from old machines, or run conversions on a Mac or Linux system where Outlook was never installed.
Will the VCF file include contact photos?
Depends on the method you use. The CSV route through Outlook's export wizard always drops them. A converter that reads the PST file directly can preserve photos — they end up embedded in the PHOTO field of each vCard. Check the tool's documentation or test with a single contact first if photos are critical to your migration.
How do I export all Outlook contacts to a single VCF file?
Outlook's native Save As creates one file per contact — no built-in combined export option. A dedicated converter handles this automatically, merging all contacts into one VCF file that any platform can import in a single step. The free workaround is to export to CSV, import into Google Contacts, then re-export from there as VCF — it works but photos won't make it through.
Which vCard version should I use for the output?
My recommendation is always vCard 3.0. It's the workhorse — compatible with Google Contacts, iCloud, Android, Outlook, and macOS Contacts. vCard 4.0 looks better on paper, but real-world adoption is still patchy; I've seen apps quietly drop 4.0-specific fields on import without any warning. And honestly, just steer clear of vCard 2.1 unless you enjoy troubleshooting garbled international characters afterward.
Does converting PST to VCF delete or modify the original PST file?
No. The converter reads from the PST and writes to a new VCF file. Your original PST is never touched. Keep it somewhere safe — if you need to re-run with different settings, or extract other data types like emails or calendar events, you'll want the source file available.
Wrapping Up
For a handful of contacts, Outlook's built-in Save As method gets the job done. For anything bigger — a full address book migration, a batch export where photos need to survive, or any situation where Outlook isn't installed — a dedicated converter is the practical path. It reads the PST directly, preserves photos and notes, catches sub-folders, and outputs one combined VCF file ready to import anywhere.
Once you have a clean VCF file, getting it into Google Contacts, an iPhone, or a CRM takes about two minutes — that part is genuinely quick.
These migrations can occasionally throw unexpected issues depending on the age of the archive or how Outlook had things organized. If you're hitting something not covered here, drop a question in the comments and I'll take a look.
