Google Contacts exports your entire address book as a single vCard file — there is no built-in option to download a vCard for a single Gmail contact. The Gmail contact export in the web interface bundles every saved entry into one .vcf download, with no per-contact vCard button anywhere on a contact's detail page. To get a vCard for one contact, or to compose a new vCard that you can hand off to someone for import into Gmail, you need a different path: a local generator that follows the vCard 4.0 specification and produces a standards-aligned .vcf file you control. The vCard Generator does exactly this work in your browser — no account, no upload, no remote conversion service. You type in the contact details, review the exact vCard 4.0 text in the preview, and download a .vcf file that imports cleanly into Google Contacts and other address-book applications. This route is most practical when you only need one contact file, when the contact data is private enough that you do not want it passing through Google's servers, or when you want a portable .vcf you can email, message, or archive without going through the bulk export flow.
What Gmail's Built-In vCard Export Actually Does
Google Contacts — the address book that powers Gmail's contact suggestions — has an Export option inside its left-hand menu. When you open it, you can choose vCard (the file format for contact cards) or CSV as the output, and either export every contact or a manually selected batch. The result is one .vcf file that contains a separate vCard record for each contact you exported, all packed into a single archive-like file. This is the only official way to get vCards out of Gmail's address book from the web, and the same flow is the one Google documents in its support pages.
Three limits matter for most readers searching for a single vCard from Gmail. First, the granularity is "all or selected batch" — there is no per-contact vCard download button on a contact's detail page. Second, the file you receive typically uses vCard 3.0 encoding, which is older and less strict about text escaping than vCard 4.0. Third, the export runs inside your signed-in Google session, so the data leaves your machine and passes through Google's servers even though it is your own information.
When a Locally Built vCard Is the Better Route
A local generator solves the three limits above in one move. If you want a vCard that contains exactly one contact, you do not need to export a hundred-card .vcf and then split it open in a text editor. If you want vCard 4.0 — the version specified in RFC 6350 — you can produce it directly instead of relying on whatever version Google's exporter hands you. If the contact details are private, building the file in your own browser means the names, phone numbers, and notes never travel to a remote conversion service.
The vCard Generator is also useful in the opposite direction: when you need a clean .vcf to hand to a Gmail user. Instead of sending a contact card that some other app generated and that may fail to import, you can build one locally that follows the core serialization rules, then attach it to an email or message. This keeps the recipient's address book tidy and avoids the broken-import surprises that happen when vendor-specific extensions or non-standard escaping slip into the file.
Building a vCard Locally With vCard Generator
The flow is short and stays inside one browser tab.
- Enter the full name. The full name is the one field the tool requires because a portable contact record without a formatted name is not useful. Type it as you want it to appear in the recipient's address book — for example, "Jane Doe" or "María González".
- Add optional fields. Fill in any organization, job title, email address, phone number, website, or note you want included. Leave anything you do not need blank, and the generator will simply omit the property rather than emit a vague empty line.
- Select Create vCard and read the preview. The preview shows the exact vCard 4.0 text that will be written to the file. Read it carefully — escape sequences such as backslash-comma for a literal comma appear in the preview and are decoded by importers at the other end.
- Download the .vcf file. The download link points to a temporary local Blob assembled from the preview, so the file is built without any server round-trip.
- Test-import before sharing. Open the .vcf in the address-book application you actually plan to use — Google Contacts on the web, Apple Contacts, Outlook, or your phone — and confirm the name, country code, email domain, and website path all look right.
Sending the Generated .vcf Into Gmail or Another App
To bring a locally built .vcf into Gmail, open Google Contacts on the web, click Create contact in the top-right, choose Create a contact, then use the Import option in the left-hand menu to upload the .vcf file. Google will parse the vCard 4.0 record and add it as a new contact. Because the file follows the standard's core escaping rules, fields such as organization names that contain semicolons and notes that contain line breaks should arrive intact rather than being split across empty properties.
For desktop and mobile apps, the import path is usually an Import command inside the address book. macOS Contacts, Microsoft Outlook, Thunderbird, iOS, and Android all accept .vcf files from a file picker or share sheet. The IANA vCard Elements Registry lists the standard properties these importers expect to see, and the generator emits exactly that conservative property set rather than vendor-specific photo, social-profile, or synchronization extensions. If your target application supports more properties than the generator emits, the extra fields simply remain blank rather than causing the import to fail.
Why the Standards-Aligned Format Matters for Gmail Imports
vCard 4.0 has a few rules that are easy to break by hand. Text values must escape commas, semicolons, backslashes, and line breaks so an importer does not mistake them for structural delimiters. The IANA vCard Elements Registry records the property names and parameters that conforming parsers recognize. Content lines must be folded so no physical line exceeds 75 UTF-8 octets, with each continuation beginning with a single space. The file must end with CRLF line endings and a final CRLF. Without these details, an importer may silently misread the record, drop fields, or refuse the file altogether.
The vCard Generator handles each of these rules automatically. It escapes commas, semicolons, backslashes, and embedded line breaks in your text values. It folds long lines at no more than 75 octets without splitting a Unicode code point — so an emoji or accented character never gets cut in the middle of its UTF-8 encoding. It writes CRLF line endings and adds a final CRLF. It also rejects embedded usernames and passwords in website fields and rejects unsupported control characters in other text fields, so a stray newline in a note cannot accidentally inject an extra vCard property into the output. All of this appears directly in the preview — the preview shows the exact vCard 4.0 text with escaped characters and folded lines, so you can verify the output before downloading.
Gmail Export vs. vCard Generator at a Glance
The table below summarizes where the two paths differ in practice.
| Aspect | Gmail / Google Contacts native export | vCard Generator |
|---|---|---|
| Output file | One .vcf containing every selected contact | One .vcf per generated record |
| Granularity | All contacts or a manually selected batch | Exactly one contact per session |
| Data leaves the browser | Yes — runs inside your signed-in Google session | No — processing stays local |
| Account required | Yes | No |
| vCard version produced | vCard 3.0 in most cases | vCard 4.0 per RFC 6350 |
| Field control | Whatever Google Contacts already stores | Typed fresh, optional fields can be omitted |
| Import target on the other end | Any address book that reads .vcf | Any address book that reads .vcf 4.0 |
For moving your full Gmail address book to a new platform, the native export is the right tool because the granularity matches what you need. For getting a single vCard out of Gmail data, building a fresh record locally, or producing a portable file that imports cleanly elsewhere, the vCard Generator is the better fit. If you want a vCard that you know will import in the broadest set of applications, see the practical guidance in How to Create a vCard File That Imports Cleanly Anywhere.
A Quick Note on Privacy
Because the vCard Generator builds the file from the data you type in the same browser tab, the contact details never reach a server. The download link is a temporary Blob URL that points at an in-memory file. Closing the tab or reloading the page discards the entered data and the generated download. That makes this route appropriate for vCards that include private numbers, internal organization details, or notes you would not want submitted to a remote conversion service.