Electronic Business Cards: What They Are and How to Make One
The four formats, the free browser way to make one, and how to share it so your details are never out of date.
An electronic business card is your contact details in a digital form a phone saves in one tap. In practice it's one of two things: a .vcf contact file (the vCard open standard) or a hosted card page you share by link, QR code, or NFC tap. Both drop your name, number, and email straight into someone's Contacts.
"Electronic business card" is the decades-old name for the vCard, a registered file format (Library of Congress) that predates every modern card app. This guide covers the four formats you'll actually use, how to build one free in a browser, how to share it, what a recipient can see, and the tradeoff that decides between a static file and a hosted card.
Key Takeaways - Electronic business cards come in four formats: a .vcf file, a QR code, a hosted card page, and an email-signature card. - The .vcf (vCard) format is an open standard from RFC 6350 (IETF, 2011), so any phone reads it. - A static .vcf freezes at download; a hosted card at a link stays editable after you share it. - You can build a .vcf plus QR free in the browser, no signup.
What is an electronic business card?
A digital contact file that saves to a phone's address book with no app installed, that's an electronic business card. The standard format is the vCard: extension .vcf, MIME type text/vcard, defined in (IETF RFC 6350, 2011). Because it's an open standard, not a proprietary format, an iPhone and an Android read the identical file.
Two different things share the name, and separating them prevents confusion. First is the vCard file itself, a small text file your phone imports. Second is the modern hosted digital card: a web profile with clickable links, a photo, and brand colors that generates a .vcf the moment someone taps "Save contact."
What's inside a .vcf file
Every vCard opens with BEGIN:VCARD, closes with END:VCARD, and carries a VERSION line, with each detail stored as a PROPERTY:VALUE pair in UTF-8 (IETF RFC 6350, 2011). Common properties read plainly: FN (display name), TEL, EMAIL, ORG, TITLE, URL, and PHOTO. The file is human-readable, which is why any contacts app can parse it without a plugin.
The four formats of an electronic business card
Four formats cover almost every use: a .vcf contact file, a QR code, a hosted card page at a link, and an email-signature card. All four ultimately deliver the same vCard payload defined in RFC 6350 (IETF, 2011). The column that matters most is the last one below: can you still edit the card after you've handed it out?
| Format | What it is | Best for | Editable after sharing? |
|---|---|---|---|
| .vcf contact file | The vCard file itself | Saving straight to Contacts | No, frozen at download |
| QR code | A scannable square | Badges, screens, print | Yes, if it points to a link |
| Hosted card page | A web profile at a URL | Link in bio, remote sharing | Yes |
| Email-signature card | A linked block in your sign-off | Every email you send | Yes, if it links to a hosted card |
The formats that stay editable are the ones built on a link. A raw .vcf, or a QR that encodes a raw .vcf, freezes the moment you create it, and that single fact decides most of the choices later in this guide.
How do you make an electronic business card for free?
You build one in a browser, no signup, in about two minutes. Whooshly's free vCard and QR builder creates a .vcf plus a matching QR code and lets you download both without an account. Enter your name, number, email, company, and title, then export.
Three steps and you're done:
- Enter your details (name, phone, email, company, title, website).
- Download the .vcf file and the QR image.
- Add the QR to your phone lock screen, print it, or drop the .vcf into an email.
For the sign-off version, the email-signature generator turns the same details into a signature block you paste into Gmail or Outlook once.
How do you share an electronic business card?
Three channels, all resolving to the same contact: a link, a QR scan, or an NFC tap. The recipient never needs your app; they get a standard vCard their phone already knows how to save, whether they run iOS or Android (IETF RFC 6350, 2011).
Pick the channel that fits the moment:
- Email signature: a link or button under your name on every message.
- QR on a badge or screen: they point a camera, the contact opens.
- Text or AirDrop: send the .vcf directly in a chat.
- Link in bio: one URL on Instagram, LinkedIn, or a digital cards hub.
Why a QR should encode a link, not the whole file
A QR code tops out around 2,953 bytes at its densest (Denso Wave, the format's inventor), and a full vCard with a photo eats into that fast. Denser codes get harder to scan. So the reliable pattern nearly every platform uses is to encode a short URL that resolves to the card, keeping the QR light and letting you edit the destination later.
NFC taps and the iPhone caveat
NFC works only across a few centimeters, roughly 4 cm, a deliberate tap rather than a passive scan. One caveat matters: iPhone background tag reading (a tap with no app open) works only on iPhone XS and newer, needs an NDEF URL record, and still asks the user to tap a banner (Apple Developer; GoToTags). It isn't automatic, and older phones need a reader app. Best practice pairs an NFC chip with a printed QR fallback; our NFC smart-card guide covers the hardware in depth.
What can people see when they open your card?
Whoever holds the link or scans the QR sees exactly the fields you put on the card, name, title, number, email, and any social links, and nothing more. A .vcf exposes the same fields the instant it's saved, so treat a shared card as public. Don't add a personal cell you wouldn't hand to a stranger.
A hosted card at a public URL has no login wall by default, so anyone with the link can open it. That's the point for networking, but the card is only as private as its least careful recipient. A static .vcf, once texted or emailed, sits on that person's device with no recall. In our testing, neither format lets you "unshare" a card someone already saved, so your real control is what you choose to include, plus editing a hosted card to strip a field later.
Electronic vs paper business cards
Electronic cards win on three practical points: you never run out, the details stay current, and the recipient saves them in one tap instead of retyping. Paper keeps a real edge in feel and offline reliability. Plenty of professionals carry both and let the room decide.
| Electronic card | Paper card | |
|---|---|---|
| Runs out | Never | Yes, reprint |
| Update details | Edit once (hosted) | Reprint the batch |
| Saved to phone | One tap | Manual typing |
| Works offline | Needs connectivity (hosted) | Always |
| Feels personal | Less tactile | Tactile |
| Cost per extra card | Zero | Printing cost |
A hosted electronic card is the stronger pick for anyone whose title, number, or company changes. Paper still fits if your details never move and you value the physical handoff.
When does a hosted card beat a static .vcf?
The moment your details change. A static .vcf freezes the instant you download it, so change your number and everyone holding the old file has stale data with no way to know. A hosted card lives at a short link: edit it once and every saved QR and link resolves to the new details.
That's the line between free and pay-once. The free .vcf plus QR from the free vCard and QR builder is perfect for a fixed set of details you control. When you want a card that stays current after you've handed it out, Whooshly's hosted card sits at a short link you own for $49 once, no subscription (an optional $9/mo Pro adds scan analytics). You update it; everyone who saved it gets the current version.
Start free, go hosted when details change
An electronic business card is your contact details in a form a phone saves in one tap, delivered as a .vcf file, a QR code, a hosted page, or an email signature. Start free: build the .vcf and QR in a browser, add the QR to your lock screen, and drop a link in your signature. Move to a hosted card once your details change often enough that reprinting and re-sending gets old. The only real decision is static versus editable; the digital cards hub walks through the hosted setup when you're ready.