NFC vs RFID vs Bluetooth: what is the difference?
NFC, RFID and Bluetooth are three different answers to the same problem of moving data without a cable. NFC works over a few centimetres and powers the tag it reads. RFID covers a family of frequencies, some of which read from several metres. Bluetooth needs power and a connection at both ends.
Is NFC a kind of RFID?
Yes, and this is where most of the confusion starts. RFID is not a single technology but a family of them, spread across three frequency bands that behave nothing alike. Low frequency systems work around 125 to 134 kHz. High frequency systems work at 13.56 MHz. Ultra high frequency systems work in the 860 to 960 MHz band, with the exact allocation depending on the country. GS1 maintains the standards used by most UHF deployments.
NFC sits inside the 13.56 MHz branch. It adds two things the rest of RFID does not have. The first is NDEF, a data format that every compliant device can read, so a tag written by one phone is understood by another. The second is symmetry: an NFC device can act as a reader or present itself as a tag, which is what makes contactless payment from a phone possible.
So every NFC device is an RFID device. The reverse is false, and the gap is wide. A warehouse scanning pallets at four metres and a phone reading a sticker at two centimetres are both doing RFID, and they share almost nothing else.
Bluetooth is unrelated. It works at 2.4 GHz, in the same band as Wi-Fi and microwave ovens, and it is a networking protocol rather than an identification one. The Bluetooth SIG publishes its specifications.
The three side by side
The table compares NFC against the two technologies it is most often confused with. The RFID column describes UHF RFID, since that is the variant people mean when they say a system is "RFID" rather than NFC.
| Criterion | NFC | UHF RFID | Bluetooth |
|---|---|---|---|
| Frequency | 13.56 MHz | 860 to 960 MHz, allocation varies by country | 2.4 GHz |
| Working distance | Centimetres | Metres | Tens of metres, highly variable |
| Power at the far end | None, the tag draws energy from the reader | None for passive tags, battery for active ones | Battery required on both sides |
| Setup before exchange | None, proximity is the trigger | None, the reader interrogates continuously | Pairing or a connection procedure |
| Payload | A URL, a credential, a contact card | An identifier and a small amount of data | Audio, files, continuous streams |
| Reading many at once | One at a time in practice | Hundreds per second, its main purpose | Several simultaneous connections |
| Works with an ordinary phone | Yes | No, needs a dedicated reader | Yes |
| Cost of the passive item | Cents | Cents | Not applicable, no passive form exists |
Why range is the deciding factor
Every other difference follows from this one. Read the ranges as orders of magnitude rather than as guarantees, because the real figure depends on antenna size, transmitted power and what sits between the two devices.
The short range is usually presented as NFC's weakness. In an access or payment context it is the feature that matters most. A badge that only works when you hold it against the reader cannot be triggered from a queue behind you, and a card that reads at four metres would be a liability rather than a convenience.
Which one needs a battery
An NFC tag has no power source. It draws what it needs from the field the reader generates, which is why a sticker costs a few cents, survives years in a drawer and never needs servicing. A passive UHF RFID tag works the same way at a different frequency.
Bluetooth has no passive form. Both ends transmit, so both ends need power. A Bluetooth beacon is a small battery powered radio, and the battery is the part that will eventually decide the deployment's cost: replacing a thousand coin cells across a building is an operation, not a detail.
This single difference decides most projects before any other criterion is examined. If the thing being read is a card, a label, a poster or a product, it cannot host a battery, and Bluetooth is out.
Where the comparison usually goes wrong
Comparing "NFC and RFID" as if they were two competing options is the most common mistake, and it produces bad decisions. The real question is which frequency band suits the distance you need. Once that is settled, whether the result is called NFC or RFID follows from it.
How to choose between them
The decision is usually made by one constraint, and it is worth finding which one before comparing anything else.
If the object being read cannot carry a battery, Bluetooth is eliminated. If an ordinary phone has to be the reader, UHF RFID is eliminated, because no phone has hardware for that band. Those two questions alone resolve most projects.
Where genuine hesitation remains is between NFC and UHF RFID for inventory work. NFC is cheaper to start with, since the reader is a phone people already own, and it is adequate for tagging equipment that gets scanned deliberately, one item at a time. It becomes the wrong choice the moment somebody has to scan a full pallet: reading a hundred items one by one is not a slower version of reading them at once, it is a different job. If your process involves counting things in bulk, buy UHF hardware and stop trying to make NFC fit.
Bluetooth wins whenever the exchange has to continue over time or over distance: streaming audio, tracking a moving asset across a building, talking to a device the user never physically touches.
Frequently asked questions
Is NFC just short range RFID?
Close, but the sentence hides the part that matters. NFC is built on the 13.56 MHz branch of RFID and adds a layer the rest of RFID does not have: a data format that every compliant device understands, and the ability for one device to act as a reader or as a tag. A UHF RFID system reads an identifier. An NFC device reads structured content and can also write it.
Can a phone read a UHF RFID tag?
No. Phones have a 13.56 MHz antenna and no hardware for the 860 to 960 MHz band that UHF RFID uses. This is not a software limitation and no application can work around it. Reading UHF tags requires a dedicated reader, either a handheld unit or a sled that attaches to the phone.
Why does Bluetooth need pairing when NFC does not?
Because Bluetooth has to work across a room, it cannot assume that the device it is talking to is the one you meant. Pairing is how it establishes that. NFC solves the same problem physically: at a few centimetres, holding the phone against the tag is itself the act of selection, so no negotiation is needed.
Which one should you use for a business card?
NFC, without hesitation. A card has no room for a battery, which rules out Bluetooth. It must be read by an ordinary phone, which rules out UHF RFID. The deliberate gesture of tapping two objects together is also exactly the interaction you want when handing over contact details.