How to Build a Digital Business Card on an NFC Tag — vCard, Smart Poster, or URL

A digital business card on NFC is one NDEF message written to a tag. You've got three real payload choices: a vCard MIME record, a URL record pointing at a hosted contact page, or a Smart Poster that wraps the URL with a title. The right pick depends on whether your audience is on iPhone or Android, how often you'll update your details, and which NTAG chip you bought.

Pick your encoding: vCard, URL, or Smart Poster

vCard MIME record

A vCard is a plain-text contact file defined by RFC 6350 (version 4.0) and its older 3.0 and 2.1 predecessors. On a tag, it lives inside an NDEF record with TNF = 0x02 and a MIME type of text/vcard. The OS opens the contact dialog directly when a reader hands it the record — no website, no detour. The catch: iOS only handles MIME records reliably when an NFC reader app is already open. Android's NDEF dispatch routes text/vcard straight to Contacts, which is exactly what you want. If your audience leans Android, the vCard record is the cleanest path.

URL record

A URL record uses the Well Known URI RTD, which compresses the prefix (https://, tel:, mailto:) to a single byte and stores the rest as a short string. Tap, browser opens, your page presents a "Save contact" button that downloads a vCard. URL records are universally tappable — every iPhone XS or newer running iOS 13+ surfaces them in background tag reading on iPhone without an app open, per Apple's NFCNDEFTag docs. Bonus: you can update the destination page later without ever touching the tag.

Smart Poster

A Smart Poster is the NFC Forum specification that bundles a URI record with optional Title and Action records. The phone can show the title before opening the URL — so the tap dialog says "Add Jane Doe to contacts" instead of a raw domain.

Memory budget

NDEF overhead plus your payload has to fit in the chip's user memory. The common Type-2 chips give you roughly 144 bytes (NTAG213), 504 bytes (NTAG215), or 888 bytes (NTAG216). A trimmed vCard fits NTAG215 comfortably; a URL fits any of them. See the right NTAG chip for the job for the full comparison.

Step-by-step — write the tag

You'll need an NFC-capable phone (iPhone XS or newer on iOS 13+ for writes, or any modern Android), a blank NTAG213/215/216, and NFCore or any NDEF writer.

1. Compose your vCard in any plain editor. The minimum useful payload is BEGIN:VCARD, VERSION:3.0, FN:, N:, TEL;TYPE=cell:, EMAIL:, ORG:, URL:, REV:, END:VCARD. Save as UTF-8.
2. Open NFCore and start a new tag. Pick the record type — vCard, URL, or Smart Poster.
3. Paste your vCard (or your URL), tap Write, and hold the tag steady against the phone's NFC antenna until you feel the success haptic. Antenna placement matters more than people expect — see the full writing an NFC tag with your phone walkthrough.
4. Verify with a second device. The contact dialog should pop for vCards; a URL preview should pop for URL and Smart Poster.

Under the hood on Android, the calls are NdefRecord.createMime("text/vcard", bytes) and NdefRecord.createUri(uri), wrapped in an NdefMessage and written via Ndef.writeNdefMessage() — per Android's NFC basics documentation. NFCore handles this for you, but knowing what's happening underneath the NDEF wrapper every reader understands helps when something goes sideways.

Common problems and fixes

Nothing happens when you tap on iPhone — you probably wrote a MIME vCard. iOS background reading is reliable for URL records and patchy for raw MIME. Open NFCore first, or switch to a URL or Smart Poster.

The contact dialog shows blank fields — usually a vCard 4.0 with a malformed FN or missing N. Drop back to vCard 3.0 with the basic set.

Write fails or only writes once — the tag was locked, or it's a Type-V chip (ICODE SLIX) instead of a Type-2. Stick to NTAG213/215/216. They arrive NDEF-formatted and unlocked.

The card ran out of room — drop PHOTO and LOGO, shorten NOTE, or move up to an NTAG216.

Doing this on NFCore specifically

NFCore ships a Digital Business Card template for each encoding, so you don't have to assemble the vCard text by hand. The Tag Inspector shows the exact NDEF record layout after the write — TNF, type field, payload length — which is the fastest way to confirm text/vcard actually landed on the tag. Nothing leaves your phone; the contact details live on the tag and in the app, not on a server.

Frequently Asked Questions

Can an iPhone read a vCard NFC tag without an app open?

Not reliably. iPhone XS and later on iOS 13+ surface URL records in the background, but a raw vCard MIME record usually needs an NFC reader app open. For one-tap on iOS, write a URL pointing to a hosted contact page that serves the vCard download.

Which NFC tag should I buy for a business card?

An NTAG215 is the safe default — about 504 bytes of user memory, enough for a trimmed vCard. NTAG213 (~144 bytes) works for a URL or a very small vCard. NTAG216 (~888 bytes) is useful if you plan to add a photo or a long NOTE field.

vCard, URL, or Smart Poster — what's the difference on tap?

vCard opens the contact dialog directly on devices that handle text/vcard. URL opens a webpage and is the most universal across iOS and Android. Smart Poster wraps a URL with a title so the dialog can show a label before opening. Pick URL or Smart Poster if iOS background taps matter; pick vCard if your audience is Android-heavy.

Can I update an NFC business-card tag after writing it?

Yes — as long as you don't lock it. NDEF tags stay rewritable until you set the lock bytes. If your details change often, leave the tag unlocked or write a URL pointing to a page you can edit.

Does the vCard need to be version 4.0?

vCard 3.0 reads more reliably across older Android contact apps; 4.0 is the current standard (RFC 6350). For a mixed audience, vCard 3.0 with FN, N, TEL, EMAIL, ORG, and URL is the safest payload.