Short answer
NFC needs an NFC-capable phone held within a couple of centimetres: Apple lists the iPhone XR, XS and later as reading tags automatically and the iPhone 7 to X as needing the NFC Tag Reader control[1]; Android phones scan tags when unlocked[3]; the NFC Forum describes the historical operating range as about 5 mm, extended to up to 2 cm in NFC Release 15[4]. QR needs a camera and enough light: the iPhone Camera app reads codes natively[2]. A short card link fits a 29-module QR code at level M; a full vCard needs an 81-module code — 2.8× the width (NexaLink measurement).
Key takeaways
- iPhone background tag reading starts with the XR/XS generation; the 7, 7 Plus, 8, 8 Plus and X read tags only after turning on NFC Tag Reader in Control Center[1]. Older iPhones cannot read NFC business cards at all.
- On Android, tag scanning is on whenever the screen is unlocked and NFC is enabled; from Android 16 a web-link tag opens through the standard link handler, and from Android 17 the user must tap an "open link" notification first[3].
- NFC is a proximity technology by design: the NFC Forum gives about 0.5 cm as the historical range and up to 2 cm with Release 15[4]. There is no "across the table" NFC.
- A QR code's size is set by its payload: 28 bytes (a short link) needs version 3 at error-correction level M, 438 bytes (a full vCard) needs version 16 — 29 versus 81 modules a side (measured with qrcode 1.5.4)[5].
- Neither method needs the recipient to install an app; both end at a web page or a contact card, which is where NexaLink Card does its work.
What each method needs
| Requirement | NFC business card | QR code business card |
|---|---|---|
| Hardware on the recipient's phone | NFC reader. iPhone 7 and later have one; automatic (background) reading from iPhone XR/XS onward[1]. Android: device must have NFC hardware[3] | Any camera; the iPhone Camera app and Control Center Code Scanner read QR codes[2] |
| User action | iPhone XR/XS and later: hold near the top of the phone, no app[1]. iPhone 7–X: open Control Center, tap NFC Tag Reader[1]. Android: screen unlocked, NFC on[3]; Android 17 adds an explicit "open link" tap[3] | Point the camera at the code and tap the link that appears[2] |
| Distance | About 0.5 cm historically; up to 2 cm with NFC Release 15 hardware[4] | Any distance at which the camera resolves the modules; depends on code size (calculator on the QR size page) |
| Light | Not needed | Needed; a phone torch helps in the dark |
| Where the data lives | On the tag, usually a URL record (NDEF) that opens a web page[3] | In the printed code: a URL, a vCard or a MECARD (format reference) |
| Updating the details | If the tag holds a link, change the page; if it holds a vCard, rewrite the tag | If the code holds a link, change the page; if it holds a vCard, reprint |
| Cost per card | Physical NFC card or sticker; prices vary by vendor — see the digital business card apps guide | Printing only, or none if shown on screen |
| Failure modes | Phone without NFC; NFC switched off; phone case or metal; wrong spot on the phone; Android app allow-list prompt[3] | Poor light; too small a code for the distance; damaged print; glare |
iPhone support, model by model
Apple's support note is the authoritative list. It says the iPhone SE (2nd generation and later), XR, XS, XS Max, 11, 11 Pro, 11 Pro Max, 12 mini, 12, 12 Pro, 12 Pro Max, 13 mini, 13, 13 Pro and 13 Pro Max automatically support NFC Tag Reader, and that on the iPhone 7, 7 Plus, 8, 8 Plus and X the user must turn on NFC Tag Reader in Control Center[1]. The note was written for iOS 15 and later models follow the automatic behaviour; models before the iPhone 7 have no tag-reading capability. For QR, Apple's instructions are simply to open the Camera from the Home Screen, Lock Screen or Control Center, hold the phone so the code appears and tap the link[2].
| iPhone | Reads an NFC card | How |
|---|---|---|
| 6s and earlier | No | No tag reading[1] |
| 7, 7 Plus, 8, 8 Plus, X | Yes, manually | Turn on NFC Tag Reader in Control Center, then hold the card to the top of the phone[1] |
| XR, XS, XS Max, 11 family, SE (2nd gen and later), 12 family, 13 family and later | Yes, automatically | Hold the card near the top of the phone with the screen on; a notification opens the link[1] |
| Any iPhone with a camera and a recent iOS | QR: yes | Camera app or Control Center Code Scanner[2] |
Android: always listening, with new guard rails
Android's NFC documentation states that Android-powered devices are usually looking for NFC tags when the screen is unlocked, unless NFC is disabled in Settings, and that because devices scan tags at a very short range the system dispatches the tag to the most appropriate app without asking[3]. Two recent changes matter for business cards. Starting in Android 16, a tag that stores a web link (http or https) triggers the ordinary view-a-link intent rather than the NFC-specific one; beginning with Android 17, scanning such a tag surfaces an "open link" notification and requires the user to tap it[3]. Android 16 also introduced a per-app allow-list: users are notified the first time an app receives a tag and can stop it scanning[3]. In practice an NFC business card that holds a URL still works on every Android version with NFC hardware; what changed is that the page no longer opens silently.
QR: how much the payload decides (NexaLink measurement)
A QR code's physical size at a given print resolution is fixed by its version, and the version is fixed by how many bytes go in and the error-correction level. We encoded six representative payloads with the qrcode 1.5.4 encoder[5] (byte mode, auto-selecting the smallest version) on 15 November 2026. The result is the practical case for putting a link, not a whole contact, in a card's QR code.
| Payload | Bytes | Version at L / M / Q / H | Modules per side at M | Side at 0.5 mm modules incl. quiet zone |
|---|---|---|---|---|
| Short card link (https://nexalink.co/c/a1b2c3) | 28 | 2 / 3 / 3 / 4 | 29 | 18.5 mm |
| Readable card link | 42 | 3 / 3 / 4 / 5 | 29 | 18.5 mm |
| MECARD: name, phone, email, URL | 88 | 5 / 5 / 7 / 8 | 37 | 22.5 mm |
| vCard 3.0: name, one phone, one email | 124 | 6 / 7 / 9 / 11 | 45 | 26.5 mm |
| vCard 3.0: organisation, title, two phones, email, URL, address | 280 | 11 / 12 / 15 / 17 | 65 | 36.5 mm |
| vCard 3.0: as above plus second email, second URL, note | 438 | 14 / 16 / 19 / 22 | 81 | 44.5 mm |
Read across: the full vCard needs a code 2.8 times as wide as the short link at the same error-correction level, and at a 0.5 mm module it nearly fills the short side of a business card. The error-correction levels L, M, Q and H restore roughly 7%, 15%, 25% and 30% of codewords respectively[8]; the QR standard defines 40 versions from 21 × 21 to 177 × 177 modules[7][6]. NexaLink Card's in-app QR encodes a vCard at level M for scan-to-save when the other person has no app, and the card's print and NFC surfaces carry the link. The QR size calculator lets you test your own payload.
Which to use
- Both, on the same card. NFC for the fast tap with iPhone XR/XS-and-later and NFC Android phones; a printed QR for everyone else and for screens, slides and email signatures. That is how NexaLink Card is built; the recipient needs no app for either[1][2].
- Put a link in both. A URL record updates when you change jobs; a vCard baked into a tag or a print does not, and a vCard QR is 2–3× the size of a link QR.
- Test on the oldest phone you expect to meet. An iPhone 8 needs the Control Center reader[1]; an Android 17 phone shows a notification before opening the link[3].
- Mind the distance. NFC works at centimetres, not across a table[4]; a QR code must be large enough for the distance it will be scanned from.
Frequently asked questions
Which iPhones can read an NFC business card?
Apple lists the iPhone XR, XS, XS Max, the 11, 12 and 13 families and the SE (2nd generation and later) as reading NFC tags automatically, and later models follow suit. The iPhone 7, 7 Plus, 8, 8 Plus and X read tags after you turn on NFC Tag Reader in Control Center. Earlier iPhones cannot.
Do Android phones read NFC business cards without an app?
Yes, if the phone has NFC hardware and NFC is on: Android scans tags whenever the screen is unlocked. From Android 16 a web-link tag opens through the normal link handler, and from Android 17 you tap an "open link" notification first.
How close does the phone have to be for NFC?
Very close: the NFC Forum describes the historical operating range as about 5 mm, extended to up to 2 cm with NFC Release 15. Cases and metal reduce it further.
Is a QR code better than NFC for a business card?
They fail in different places. QR works on any phone with a camera but needs light and size; NFC works in the dark and in a second but needs an NFC phone held at the right spot. A card with both covers the most people.
How big should the QR code on a business card be?
It depends on what is in it. Our measurement: a short link fits a 29-module code (18.5 mm a side at 0.5 mm modules with the quiet zone); a full vCard needs 81 modules (44.5 mm). Put a link in the code and keep the contact details on the page it opens.
Should the NFC tag hold a vCard or a link?
A link. Both Apple's background reading and Android's dispatch are built around URL records, the page can be updated without rewriting the tag, and the same link works in the QR code.
Does NexaLink Card support both?
Yes. The card shares by NFC tap, QR code, Apple or Google Wallet pass and link, and the recipient needs no app. The in-app QR carries a vCard at error-correction level M for direct scan-to-save.
Sources
- Apple Support — iPhone models that support NFC Tag Reader — checked on 2026-11-15
- Apple Support — Scan a QR code with your iPhone or iPad — checked on 2026-11-15
- Android Developers — NFC basics (tag dispatch, Android 16 and 17 changes) — checked on 2026-11-15
- NFC Forum — NFC Release 15 (operating range) — checked on 2026-11-15
- npm — qrcode 1.5.4 (QR code encoder used for the measurements) — checked on 2026-11-15
- ISO/IEC 18004:2024 — QR code bar code symbology specification (edition 4, August 2024) — checked on 2026-11-15
- DENSO WAVE qrcode.com — Information capacity and versions of the QR Code — checked on 2026-11-15
- DENSO WAVE qrcode.com — Error correction feature — checked on 2026-11-15