RFC 6350 guide

What is RFC 6350?

RFC 6350 defines the vCard 4.0 format: a standard, text-based way to exchange contact information. Ozama uses the standard format so a card exported here can be opened by address books, email clients, and phones without vendor lock-in.

Quick rule

Every card begins with BEGIN:VCARD, declares VERSION:4.0, and ends with END:VCARD. One property belongs on each line.

Required fields

RFC 6350 requires these two properties in every vCard. Ozama marks them with an asterisk in the editor.

FN · Formatted nameThe display name people see in their address book, such as “Maya Chen”.

N · Structured nameFamily name, given name, additional names, honorific prefixes, and suffixes in that order.

Common properties

Add only the details that are useful for the person receiving the card.

EMAIL — an email address, optionally labeled with a type such as work or home.
TEL — a telephone number. Use the type to describe how it should be used.
URL — a personal or professional website.
ORG and TITLE — workplace and role information.
NOTE — a short piece of context or a reminder.

Keep property values readable and specific. A contact card with one accurate email address is more useful than one filled with outdated details.

A minimal valid example

This is the structure generated by the Studio for a contact with a name, email, and phone number.

BEGIN:VCARD
VERSION:4.0
FN:Maya Chen
N:Chen;Maya;;;
EMAIL;TYPE=work:[email protected]
TEL;TYPE=cell:+1 415 555 0184
END:VCARD

How Ozama validates

Before export, the Studio checks the card envelope, confirms required fields are present, and formats each property for vCard 4.0. Special characters such as commas, semicolons, and line breaks are escaped when needed.

Create a vCard →Browse contacts