Digital Business Card vs vCard: One Lives Inside the Other

A vCard is a text file from 1996. A digital business card is a web page. Most digital business card vs vCard articles compare them as rivals, which is roughly like arguing whether a JPEG beats a photographer's website. They do different jobs, and the good products use both.

One is a file that holds contact fields. The other is a page that holds a person. The better digital cards hand you a vCard at the end of the visit, because that file is still the one thing practically every phone already knows how to save.

What a vCard actually is

A vCard is plain text with a .vcf extension. Open one in any text editor and you can read the whole thing: BEGIN:VCARD, a name, a phone number, an email address, END:VCARD. No styling and no server.

The Versit Consortium built it and handed the rights to the Internet Mail Consortium in 1996. Version 3.0 was standardised in 1998, and version 4.0 arrived as RFC 6350 in August 2011. Thirty years later it is still what your phone writes when you share a contact.

The format is boring in the best way. The US Library of Congress keeps a preservation description of the vCard format in its registry of file formats worth being able to open in a century. Nothing about a contact file has needed to change much since dial-up.

People also say VCF, and the two words get used interchangeably. The standard is called vCard; .vcf is the extension the file is saved with, and its media type is text/vcard. Nothing practical turns on the difference.

What a digital business card actually is

A digital business card is a page at a URL. Ours look like discard.bg/p/yourname. It carries a photo, a title, links, a save button, and whatever else you decide belongs on it.

Two properties matter, and both come from it living on a server rather than in a file. You can change it after you have handed it out. You can see that somebody opened it.

That is the whole advantage over a file, and it is a large one. A file is frozen at the moment you sent it. A page is whatever it says today. If you want the long version of what belongs on one, what to include on a digital business card goes field by field.

Digital business card vs vCard, side by side

The two things a vCard file cannot do

Change your number and every vCard you have ever sent is wrong. There is no recall. The file settled into a few hundred address books and not one of them will hear about the update.

The second limit is narrower. A vCard is contact data and nothing else. That suits a plumber. It suits a photographer less well, when the work itself is the pitch, or a consultant whose case studies do the convincing. RFC 6350 does define PHOTO and URL properties, but contacts apps do not render them as a portfolio.

The file is honest about its scope. It moves eight or nine fields between two devices, reliably, forever. It was never trying to be a website.

Where a plain vCard still wins

Offline, for a start. A vCard needs no connection and no uptime. Encode one directly into a QR code and the contact saves in a basement conference room with no bars showing, which is exactly where business cards get handed over.

Then there is permanence. If a digital card provider folds, the URL dies with it and every card you handed out points at a 404. A .vcf sitting in somebody's contacts is unaffected by anyone else's business model. Worth thinking about before you sign up to a monthly plan for the privilege of being findable.

And it does not phone home. Nothing logs that the file was opened, because there is nothing to open. It lands in Contacts and that is the end of the transaction.

Why a good digital card ships a vCard inside it

Everything interesting happens in the save button.

On a Discard profile that button builds a vCard 3.0 file on the spot: FN and N for the name, then TITLE, ORG, TEL, EMAIL, a NOTE for the bio, and the profile photo base64-encoded into a PHOTO property. Version 3.0 rather than 4.0, on purpose, because 3.0 is the version Android importers and Outlook handle most predictably.

So the visitor leaves with both. The page they can come back to for the current version, and the file their phone already knows how to file away. If your number changes, the next person to tap gets a vCard with the new one, and so does anyone who reopens the link.

That layering is the whole point of putting a chip in a physical card. The metal carries the URL, the URL serves the digital profile, and the profile hands over the file. How NFC business cards work walks the tap end to end if you want the mechanics.

Which one do you need?

If all you need is to move a phone number, use a vCard. Generate the .vcf, put it behind a QR code, print it on whatever you like. It costs nothing and nobody can switch it off.

If your details move, if you want more than a handful of fields, or if you want to know whether anyone looked, you need a hosted profile. Then insist that it exports a real vCard, because a card that will not save into Contacts has failed at the one job the format solved in 1996.

Delivery is a separate question from format. A tap and a scan can both open the same page, and NFC versus QR code business cards settles that one on its own terms. If you already know what you want on the card, the configurator is where the layout and the profile get decided together.

Digital business card versus vCard is a fight that was never on. The file is a thirty-year-old standard for moving contact fields into an address book, it is very good at exactly that, and it is uninterested in anything more. The hosted profile is a page you can rewrite after the handshake, which is the one thing a file can never do. Take the file on its own only if your details are fixed and you want zero dependencies on anybody staying in business. Everyone else wants a profile, and should check it exports a proper .vcf before paying for it. A profile with no save button is a link somebody will lose by Thursday. A .vcf with no profile behind it is a phone number that will be wrong by spring.