This vCard Generator creates plain vCard 4.0 text, folding large text at no more than 75 UTF-8 octets per physical line without splitting a Unicode code point.

For this workflow, “large text” means long or character-rich values inside a contact record—not oversized lettering in a designed business card. The supported output is a downloadable .vcf file. The vCard Generator lets you enter contact details, inspect the exact generated text, and download it without sending those details to a remote conversion service.

That distinction matters when a note contains punctuation, several lines, emoji, or non-English characters. The file must remain structurally valid, while the contact application ultimately controls how the imported information is displayed.

vcard generator large text
vCard Generator for Large Text: Safe vCard 4.0

Large-text rules inside vCard 4.0

A vCard is plain text, but plain text still follows defined serialization rules. The core content-line requirements in RFC 6350 govern how a long logical value is placed on physical lines. This generator folds a long value across multiple lines, starts every continuation with one space, and limits each physical line to no more than 75 UTF-8 octets.

The octet measurement is important because UTF-8 characters can occupy more than one byte. The generator processes complete Unicode code points, so an emoji or another multibyte character is not divided in the middle of its encoding. This protects both the character and the validity of the UTF-8 output.

Large-text conditionGenerated handlingProblem prevented
A property produces a long physical lineFolds it at no more than 75 UTF-8 octets and places one space at the start of each continuationOverlong content lines
The value contains emoji or multibyte textProcesses complete Unicode code pointsA character split inside its UTF-8 encoding
The value contains commas, semicolons, or backslashesApplies the text escapes required by vCard 4.0Punctuation being interpreted as vCard structure
The value contains a line breakEncodes it inside the property valueAn extra vCard property being injected
The file needs consistent line endingsUses CRLF endings and includes a final CRLFMixed or incomplete record endings

Each generated record starts with BEGIN:VCARD, declares VERSION:4.0, includes the full name as FN, adds the optional properties supplied, and closes with END:VCARD. Empty optional fields are omitted instead of appearing as vague blank properties.

The IANA vCard Elements Registry documents the wider standard vocabulary. This generator intentionally uses a smaller, conservative property set rather than attempting to include every extension that different contact applications may support.

Match each field to a useful contact record

The full name is required because a portable contact file without a formatted name is not useful. Organization, job title, email address, phone number, website, and note are optional, so include only details that belong in the record you intend to share.

Input fieldRequirementWhat to review
Full nameRequiredSpelling, punctuation, and the order in which the name will be stored
OrganizationOptionalExact company or group wording
Job titleOptionalWhether the title belongs with this contact
Email addressOptionalThe full domain and any intended plus addressing
Phone numberOptionalCountry code, punctuation, and the intended format
WebsiteOptionalThe protocol, domain, path, and absence of credentials
NoteOptionalComplete wording, line breaks, punctuation, and practical length

Large text is not unlimited text. The generator rejects unsupported control characters and applies practical length limits to contact fields. Website entries must use public HTTP or HTTPS URLs, and embedded usernames and passwords are rejected. Line breaks inside a note remain part of that property’s value rather than becoming additional vCard records.

Ordinary international text, punctuation, phone formatting, and notes are preserved. The tool does not verify that an email address or phone number belongs to a particular person; it serializes the values you supply.

Create and inspect the vCard

  1. Enter the full name. Use the required name field for the contact’s formatted name. This becomes the explicit FN property in the record.
  2. Add the optional details you need. Include an organization, job title, email address, phone number, website, or note only when it belongs in the card. Leave unused fields empty so they are omitted.
  3. Select Create vCard. The generator serializes the supplied values into a vCard 4.0 record and displays the exact resulting text in the preview.
  4. Review the preview for accuracy. Check the name spelling, phone country code, email domain, website path, and note text. Backslashes and folded lines are expected parts of valid vCard serialization and should not be removed manually.
  5. Download the .vcf file. The download is assembled from the preview through a temporary browser Blob. Save it before closing or reloading the page.
  6. Test-import the file in the destination contact application. Confirm that the contact appears as intended before sending the .vcf to anyone else.

Read the preview without changing its encoding

Consider a name such as “Doe, Jane.” A comma can carry structural meaning in vCard text, so the generator escapes it when needed. The backslash visible in the preview is protective syntax rather than an unwanted addition to the person’s name. Semicolons, backslashes, and line breaks receive the same kind of careful treatment.

Long values are handled in two layers. The logical value remains a single contact value, while its serialized representation is folded across physical lines. Each continuation begins with one space, allowing an importer to identify the continuation and reconstruct the original value. Importers unfold the lines and decode the escaped text during import.

Do not delete apparent backslashes or manually join folded lines in the downloaded file. Those features are part of the standards-aligned output, not display artifacts. Because the result is plain text, you can also inspect it in a text editor when troubleshooting. The file itself carries contact data rather than font size, colors, or other visual styling, so a request for visibly oversized lettering requires a different output format.

Test the .vcf in your target application

Many address-book and contact applications can import a .vcf file, but their import behavior and support for optional properties can differ. A real import is the final compatibility check.

  1. Locate the downloaded .vcf file. Keep the generated file intact and use the copy you downloaded rather than a manually reconstructed version.
  2. Open the destination application’s import command. Use its documented option for importing a vCard or contact file.
  3. Select the .vcf and import it into a test contact where possible. This makes it easier to compare the imported fields without confusing them with an existing record.
  4. Compare the imported details. Check the full name first, followed by the organization, title, email, phone, website, and note that you included.
  5. Investigate optional-field differences in the preview. If a field is missing after import, confirm that it appears in the generated text. Different applications may not expose or retain every optional vCard property.

If an application refuses the record, verify that the downloaded file was not modified and review the preview for accurate input. The generator follows the core vCard 4.0 rules, but an importer can still have its own restrictions. A practical guide to clean vCard imports provides additional checks for common compatibility problems.

Understand privacy, sharing, and output limits

All processing happens in the current browser. 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. Closing or reloading the page discards the entered data and the generated download, so save the .vcf before leaving.

The focused output does not embed a photo, social-profile fields, synchronization extensions, or other vendor-specific properties. It is also not a digital identity, a verified signature, or proof that the supplied details belong to a real person. Share another person’s contact information only with appropriate consent.

For a destination that expects a downloadable contact record, the supported workflow ends with a reviewed .vcf and a test import. A scannable representation for a short public value is better handled by a dedicated QR Code Generator; this tool produces the contact file itself rather than converting it into a QR code.

For a deeper look, see Is Mind Map Maker Safe? Local Processing and Safe SVG.