A vCard generator creates a downloadable vCard 4.0 contact file from the details you enter, and the vCard Generator assembles the .vcf entirely in your browser. In practical terms, the tool takes a full name plus any optional organization, job title, email address, phone number, website, or note, then shows the exact text before offering it as a download. That preview matters because a contact file can look plausible in a form yet contain a spelling error, punctuation that needs escaping, or a line that needs folding. The result begins with BEGIN:VCARD, declares VERSION:4.0, includes FN, adds only the optional properties you supplied, and closes with END:VCARD. Empty optional fields are left out, while commas, semicolons, backslashes, and text line breaks are encoded so they remain part of the value rather than becoming unintended vCard structure. The file is plain text, so you can inspect it before use, but your final compatibility check should be a real import into the address book you plan to use. No account, remote conversion service, or upload is required for this workflow.

What the generator produces
A .vcf file is a plain-text contact record rather than a designed digital business card. This tool produces a compact vCard 4.0 file containing the standard opening and closing markers, a version declaration, the required formatted name in the FN property, and the optional details you chose to include. The core layout follows the vCard format defined by RFC 6350.
| Contact detail | Entry rule | What to check in the preview |
|---|---|---|
| Full name | Required | It appears in FN; verify the exact spelling. |
| Organization | Optional | Included only when supplied; check the company wording. |
| Job title | Optional | Included only when supplied; check capitalization and spacing. |
| Email address | Optional | Check the domain; the tool does not verify that the address belongs to a real person. |
| Phone number | Optional | Check the country code and number format; no ownership verification is performed. |
| Website | Optional | Use a public HTTP or HTTPS URL without embedded usernames or passwords. |
| Note | Optional | Text line breaks are encoded within the property value. |
Many address-book and contact applications can import a .vcf file, but “many” is more accurate than “every.” Import behavior and support for optional properties can differ between applications. The generator therefore keeps its property set conservative instead of adding vendor-specific photo, social-profile, or synchronization extensions.
Create and download a contact file
Use the generator’s form to turn the information you want into a portable contact record. The process has four clear stages:
- Enter the required full name. A contact file needs a formatted name to remain a useful portable record, so the full name is the one required entry.
- Add any details you want included. You can add an organization, job title, email address, phone number, website, or note. Leave unnecessary optional fields empty because blank properties are omitted. Website entries must be public HTTP or HTTPS URLs, embedded usernames and passwords are rejected, and other contact fields reject unsupported control characters and have practical length limits.
- Select Create vCard and review the exact preview. Read the generated vCard 4.0 text for spelling and formatting. Pay particular attention to the name, phone country code, email domain, and any path in the website address.
- Download the .vcf file and test-import it. Save the file, import it into the address-book application you intend to use, and confirm that the resulting contact contains the details you expect before distributing it.
The download link points to a temporary browser Blob assembled from the preview. Closing or reloading the page discards the entered information and generated download, so save the .vcf before leaving the page if you need to keep it.
Read the preview correctly
The preview is the serialized vCard record, not a visual rendering of a contact card. Some characters and line breaks therefore look different from the form values because they have been encoded to protect the structure. For example, a name such as “Doe, Jane,” an organization containing a semicolon, or a note containing several lines needs text escaping. Without that treatment, an importer could interpret punctuation as vCard structure instead of part of the contact value.
- Escaping: Commas, semicolons, backslashes, and text line breaks receive the escapes required for vCard text. These sequences are expected, and importers decode them when reading the card.
- UTF-8 folding: A long physical content line is folded at no more than 75 UTF-8 octets, and each continuation begins with one space. Octets are bytes rather than visible characters, so a line containing multibyte characters can be shorter in appearance while still using its full byte allowance.
- Unicode integrity: The generator processes complete Unicode code points, so it does not split an emoji or multibyte character in the middle of its UTF-8 encoding.
- Line endings: The downloaded file uses CRLF line endings and ends with a final CRLF.
Do not remove backslashes, join folded lines, or rewrap the record manually. Importers are expected to unfold and decode the content. Reading the preview as generated gives you the best chance of spotting a spelling mistake before the file reaches your contacts.
Test the file in the destination app
After downloading, import the .vcf into the contact application you plan to use and compare the result with the preview. Confirm the name spelling, phone country code, email domain, and website path. A successful import is the final compatibility check because the generator can create a standards-aligned file without guaranteeing identical behavior in every address book.
The output is plain text, so you can also inspect it with a text editor if something appears missing. For an Outlook destination, the practical Outlook vCard walkthrough provides additional guidance for the surrounding import workflow. Keep the original .vcf as the portable record even after importing it, so you can repeat the process or provide the file without recreating the contact.
The generated card does not establish identity, authenticate a phone number, or prove ownership of an email address. Share another person’s information only with appropriate consent.
Choose a vCard file or a QR code
Use a vCard when the destination expects a downloadable contact record that can be imported into an address book. Use a QR code when you need a scannable representation of a short public value. These are different deliverables, and the vCard Generator produces the .vcf file rather than a QR image.
| What you want | Suitable output | Why |
|---|---|---|
| Create a contact record for import | vCard 4.0 .vcf file | Use the vCard Generator for a downloadable contact record with an inspectable preview. |
| Share a short public value for scanning | QR code | Use QR Code Generator when a scannable representation is the appropriate format. |
| Inspect the exact contact serialization | Plain-text .vcf file | The preview and downloaded file reveal the generated properties directly. |
Choosing the correct format prevents a QR workflow from being mistaken for a contact-file workflow. If the recipient needs to import a contact record into an application, download the .vcf and test it there. If the goal is a quick scan of a short public value, use the QR-oriented tool instead.
Know the privacy and format boundaries
All processing happens in the current browser. Your contact details are not submitted to Lizely, saved in an account, or sent to a remote conversion service. The download uses a temporary local Blob assembled from the preview. This local design is useful when contact information is private or when you need a file without creating an account.
The generator serializes the values you provide; it does not claim that an email address or phone number belongs to a real person. Ordinary international text, punctuation, phone formatting, and notes are preserved while the required escaping protects the vCard structure. Unsupported control characters are rejected, website credentials are not accepted, and practical input-length limits apply.
The property set is intentionally small and text-based. It does not embed a photo or vendor-specific social-profile and synchronization extensions. The result is a plain-text contact record, not a digital identity, a verified signature, or a substitute for consent before sharing someone else’s contact information.
For a deeper look, see vCard Generator With No Sign-Up Required.