NFC cards break on range, metal, and iOS confirmation. QR codes break on print density and light. Neither format is the contact data — both just deliver a URL.
A tap-to-share card works against your own phone because you know where the antenna sits. Hand the same card to someone at a conference and the tap does nothing: no vibration, no popup, nothing to tell either of you whether it even tried. The QR printed on the back of that card is usually what saves the exchange.
Both formats 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.
What's actually being transmitted
An NFC business card is a small chip, usually in plastic or metal, storing an NDEF record — typically a URI, occasionally a full vCard. Tapping it against a phone's NFC antenna powers the chip (no battery) and the OS reads the record.
A QR-code card encodes the same URI as a matrix of squares. A camera reads it instead of a radio.
Neither one is "the data." Both are delivery mechanisms for a link. The two common failure modes have nothing to do with vCard fields. They're specific to radios and cameras.
Where NFC actually breaks
The phone has to be looking for a tag. Android only scans when NFC is on and the screen is unlocked. iPhone background tag reading exists since the XS; older models need an app that explicitly opens the scanner.
The tag format has to match what the OS expects. iOS's background reader only picks up specific NDEF record types, then asks the user to confirm before any app sees the data. "Tap and done" is never literally true on iPhone.
Range is short and inconsistent. Reliable reads happen within about 4cm, and that number moves by device. A card that works against your Pixel can fail against someone else's phone for no reason related to the card.
Metal defeats it outright. A metal NFC card needs an antenna cutout or it blocks its own signal. Plastic cards read more consistently. This is a design tradeoff, not a manufacturing defect.
Where QR actually breaks
The failure modes are almost the inverse: physical, not electronic.
Density scales with content. A URL encodes into a sparse, forgiving pattern. A QR holding an entire vCard (name, phone, title, address) is several times denser and needs better light, a steadier hand, and a cleaner print. Point the code at a page URL and put the .vcf behind a button on that page, not inside the code itself.
Light and print quality matter more than the code. A code that scans off a bright phone screen can fail on a badge under fluorescent conference lighting, especially if it was printed small or on a low-contrast background.
It needs a camera that recognizes QR, which every iPhone since iOS 11 and effectively every Android phone since Android 9 does natively. 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 roughly $15–$25, metal $40 and up, before any software subscription. Some vendors in this space don't publish that subscription pricing at all.
A QR code costs nothing to generate and nothing to reprint. That's also its main hardware limitation: there's no tactile "tap" moment, and a printed code can be photographed and reused. An NFC chip can't be cloned by a photo.
A two-minute test if you already have both
- Tap the NFC card against your own phone with the screen unlocked (Android only scans in that state). If nothing happens, check whether NFC is toggled on before blaming the card.
- Hand the same card to someone with a different phone brand and watch what happens with no prompting from you.
- 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.
- 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 first impression is the page behind it, not the transmission method.
NFC is the better fit for repeat, one-on-one taps where you know both phones support it. QR remains the more compatible option for anything printed at scale or handed to someone whose phone you can't predict.
I work on Nameplate, a page builder with tracked QR links and a vCard export. This is adapted from our longer guide. We don't sell NFC hardware.
Top comments (0)