NFC vs QR code business cards: which one actually gets scanned

A virtual business card is either a QR code encoding a URL or an NFC chip broadcasting the same data on tap. NFC needs a phone that supports background tag reading and a tap within about 4cm; QR needs enough light and a clean print. Neither format fixes a bad page behind it.

A tap-to-share card works fine against your own phone, because you've tapped it a hundred times and know exactly where the antenna sits. Hand the same card to someone else at a conference and the tap does nothing: no vibration, no popup, nothing to tell either of you whether it even tried. The QR code printed on the back of the same card usually saves the exchange, which is worth knowing before you order NFC hardware assuming it's the more reliable option.

Both formats are trying to move the same handful of bytes: a name, a title, a URL. The difference is entirely in how those bytes get from the card to the phone, and that's also exactly where each one breaks.

What's actually being transmitted

An NFC business card is a small chip, usually embedded in a plastic or metal card, storing an NDEF record, typically a URI pointing at your profile, occasionally a full vCard. Tapping the card against a phone's NFC antenna powers the chip (it has no battery) and the phone's OS reads the record.

A QR-code business card encodes the same URI as a matrix of black-and-white squares. A camera reads it instead of a radio.

Neither one is "the data." Both are just delivery mechanisms for a link, which is why the two most common failure modes have nothing to do with vCard fields or contact-import bugs. They're specific to how radios and cameras behave, and they're worth knowing before you assume a tap failed because of something you did wrong.

Where NFC actually breaks

The phone has to be looking for a tag. On Android, this means NFC is toggled on in Settings and the screen is unlocked, since Android devices only scan for tags under those conditions. On iPhone, background tag reading has existed since the iPhone XS; older models can only read NFC through an app that explicitly invokes the scanner, not by a passive tap.

The tag format has to match what the OS expects. iOS's background reader only picks up NDEF-formatted tags using specific record types, and requires the user to tap through an on-screen confirmation before any data reaches an app (a security measure, not a bug), but it means "tap and done" is never literally true on iPhone.

Range is short and inconsistent across phones. Reliable reads generally happen within about 4cm, and that number moves depending on the phone. Devices with larger, better-placed antennas read more forgivingly than phones where the antenna sits behind a thick case or a PopSocket. A card that works against your Pixel can genuinely fail against someone else's phone for no reason related to the card at all.

Metal defeats it outright. A metal NFC card (the premium option most vendors upsell) needs an antenna cutout or it blocks its own signal. This is a real design tradeoff, not a manufacturing defect, and it's the reason plastic NFC cards read more consistently than metal ones.

Where QR actually breaks

The failure modes here are almost the inverse: physical, not electronic.

Density scales with content. A URL encodes into a sparse, forgiving pattern. A QR code holding an entire vCard (name, phone, title, address) runs several times denser and needs better light, a steadier hand, and a cleaner print to scan. This is also true for QR-based digital business cards generally, not just ours, which is why we point a card's code at a page URL and let the .vcf download live behind a button on that page instead of inside the code itself. If you just need a code for a URL and don't have a page yet, our free QR code generator makes that one without an account.

Light and print quality matter more than the code itself. A code that scans instantly off a bright phone screen can fail against a badge under fluorescent conference lighting, especially if it was printed small or on a low-contrast background.

It needs a camera app that recognizes QR, which every iPhone since iOS 11 and effectively every Android phone since Android 9 does natively, no separate app required. This is the one area where QR has had fewer compatibility surprises than NFC for years.

Cost and who controls the card afterward

An NFC card is a physical object with a per-unit cost: plastic runs roughly $15 to $25, metal $40 and up, before any software subscription for lead capture or CRM sync. Some of the larger vendors in this space don't publish that subscription pricing at all; Popl's team pricing page states plainly that it quotes rates "over a meeting instead of publishing it on our website," which is a real constraint if you're trying to compare options without booking a sales call.

A QR code costs nothing to generate and nothing to reprint. That's also its main limitation as physical hardware: there's no tactile "tap" moment, and a printed code can be photographed and reused by anyone, whereas an NFC chip can't be cloned by a photo.

What we built, and why it's QR and not NFC

Nameplate doesn't sell or support NFC hardware. What we do have is a tracked-link tool in the dashboard: point it at your published page (or any URL) and it creates a /q/ address for that specific link, so scanning it redirects to wherever you set and every scan increments a counter and logs an event with a hashed session identifier rather than a raw IP. You get a scan count, not a name attached to it, and you have to create that tracked link yourself — publishing a profile doesn't generate one automatically. That's a real limitation worth stating plainly if you need attendee-level lead data at a booth: this setup tells you a code got scanned, not who scanned it or whether they saved anything afterward.

If you're choosing hardware to pair with a page like that, the practical split holds up: NFC for repeat one-on-one exchanges where you control both cards and both phones, QR for anything printed at scale or handed to strangers, since it degrades gracefully and costs nothing to reprint when your title changes.

A two-minute test if you already have both

1. Tap the NFC card against your own phone with the screen unlocked (Android only scans for tags in that state). If nothing happens, check whether NFC is toggled on before blaming the card.
2. Hand the same card to someone with a different phone brand than yours and watch what happens with no prompting from you.
3. Print the QR at the size you'll actually use, then scan it from arm's length under normal indoor light, not from six inches under your desk lamp.
4. Compare which one a stranger gets through faster, unprompted. That result matters more than either spec sheet.

What neither format fixes

Whichever one gets the tap or the scan through, it hands over a link. The actual first impression is the page behind it, not the transmission method. And on the data side: our vCard export currently includes name, title, email, and location, but not a phone number, since profiles don't have a dedicated phone field yet. If someone needs to call you from the card alone, right now they'd need it written into the title or bio instead.

Common questions

What is NFC on my phone?

NFC (Near Field Communication) is a short-range radio that lets your phone read a small passive chip when held within a few centimeters, with no battery in the chip and no pairing step. On Android it's a toggle under Connected devices; recent iPhones (XS and later) read compatible tags in the background without opening an app.

What's the difference between NFC and RFID?

RFID is the broader technology family; NFC is a specific, short-range (a few centimeters), two-way variant of it built into phones for exactly this kind of tap-to-read exchange. Most industrial RFID (inventory tags, toll passes) reads from much farther away and isn't something a phone can pick up directly.

How do I scan a QR code without an app?

Point your phone's built-in camera at it. No separate scanner app is needed on iOS 11+ or Android 9+. A viewfinder link or notification appears automatically; tap it to open.

Does an NFC business card work on every phone?

No. It needs NFC enabled, the screen unlocked on Android, and on iPhone a model no older than the XS for background reading. Metal cards can also block their own signal without an antenna cutout.

Is an NFC card better than a QR code for a business card?

Better for a specific case: repeat, one-on-one taps where you know both phones support it. QR remains the more universally compatible option for anything printed at scale or handed to someone whose phone you can't predict.