One entry creates two portable outputs

The tool assembles a vCard 3.0 contact, renders the same text as a QR code, and provides the source contact as a `.vcf` file. Phones and contact applications can often scan the image or open the file to preview fields before saving. All construction and image rendering happen in the current browser.

Names remain structured

Given and family names are stored separately in the `N` property and combined for the required formatted-name property. Organization, title, mobile phone, email, and website are optional, but at least one contact method is required. This prevents generating a card that contains only a name and little practical value.

Values are escaped before encoding

Backslashes, commas, semicolons, and line breaks have special meaning in vCard text. They are escaped according to the format rules before the QR matrix or file is created. Lines use CRLF separators for compatibility. The implementation follows the value-escaping principles documented in the IETF vCard specification while emitting vCard 3.0 for broad contact-app interoperability.

Review what a scanner imports

Contact readers vary. Some may label a mobile number differently, normalize a URL, omit an unsupported field, or ask for confirmation. Scan the final PNG on the devices that matter and open the downloaded VCF before publishing it. A QR symbol does not verify the identity or accuracy of the person represented.

The contact details are readable by anyone who receives the QR code or VCF. Obtain permission before publishing someone else’s information, and avoid including private details that should not be widely distributed.