NFC vs RFID: what is the difference

NFC and RFID are not rivals. NFC is a specific type of RFID — the close-range, two-way kind that runs at 13.56 MHz. The clearest way to understand them is to look at the whole RFID family first, then zoom into the one corner where NFC lives.

01The short answer

RFID (radio-frequency identification) is the umbrella. It covers any system where a reader uses radio to identify a tag, across three very different frequency bands and ranges from a centimetre to several metres. NFC (near-field communication) is one subset of RFID: it works only in the HF band at 13.56 MHz, only at very close range, and it adds a two-way mode so that two powered devices — such as two phones — can talk to each other, not just a reader and a dumb tag.

02RFID: the whole family

RFID is split by the frequency the reader and tag use. The band sets almost everything else: the range, the antenna size, how well it works near metal and water, and the typical use.

The pattern is worth internalising. Lower frequencies (LF) pass through water and work near the body, which is why they suit animal chips, but they need big coils and read only at a few centimetres. Higher frequencies (UHF) read across a room and let a scanner count a whole pallet at once, but they bounce off metal and are absorbed by liquids. HF, in the middle, is the sweet spot for a deliberate tap at close range — and that is where NFC was built.

03NFC: a specific slice of HF

NFC takes the HF band at 13.56 MHz and defines a tighter, standardised way to use it. It is built on the ISO/IEC 14443 contactless-card standards (plus related ones), so phones, readers and tags from different makers interoperate. Its defining traits:

• Very short range. Practical reads happen within about 10 cm, and usually closer. That is a feature: you have to mean it, which makes NFC good for payments and pairing.
• Near-field coupling. The reader and tag exchange energy through their magnetic fields, like a loosely coupled transformer, rather than radiating a signal across a room.
• Two-way communication. Beyond reading a passive tag, two powered NFC devices can exchange data (peer-to-peer), and a phone can act as a tag itself (card emulation) for payments or transit.
• Modest data, instant feel. NFC moves small amounts of data (typically up to a few hundred kilobits per second), which is plenty for an ID, a URL or a payment token.

So NFC is not a different technology from RFID; it is RFID at 13.56 MHz with extra rules and a two-way mode layered on top.

04How tags get power: passive vs active

A second axis cuts across every band: where the tag's energy comes from.

• Passive tags have no battery. The reader's field induces a small current in the tag's antenna coil, which wakes the chip just long enough to reply. Almost every card, sticker and poster tag you meet is passive. They are cheap, thin and effectively last forever, but only work inside a reader's field.
• Active tags carry their own battery and transmit on their own. They reach much farther — tens of metres — and are used in some UHF asset tracking and toll systems. They cost more and the battery eventually dies.
• Semi-passive (battery-assisted) tags sit in between: a battery runs the chip or a sensor, but the tag still uses the reader's field to reply.

All NFC tags you will use in projects are passive. They draw their power from the phone or reader during the brief tap.

05Tag types and standards

Within NFC, the NFC Forum defines several tag types, which differ in memory size and speed. You do not need to memorise them, but it helps to know they exist when you buy blank tags for a project.

Across the wider RFID world, standards are organised by use: ISO 14443 and 15693 for HF contactless, ISO 18000-6C (EPC Gen2) for UHF inventory, and various proprietary LF schemes. The takeaway: when a product says "works with NFC", it means HF 13.56 MHz on the ISO 14443 family, so a phone can read it.

06Everyday uses

Seeing where each band shows up makes the difference concrete.

• Access cards and office badges — usually HF 13.56 MHz; older systems use LF fobs.
• Contactless payment — NFC, with the phone or card emulating a secure element at 13.56 MHz.
• Transit cards — HF contactless, often DESFire-class tags.
• Tap-to-pair a speaker or headphones — NFC hands the phone the Bluetooth details so pairing is one tap.
• Smart posters and product tags — a passive NFC sticker holds a URL that a phone opens on tap.
• Warehouse and retail inventory — UHF, so a handheld can read dozens of tags across a shelf at once.
• Animal microchips — LF, read with a close-range wand.

07Build your own NFC projects

The fun part of NFC is how approachable it is. Blank NTAG stickers cost very little, and a 13.56 MHz reader module lets a microcontroller react when you tap one of your own tags. Think tap-to-start a scene at your desk, a tag by the door that your board logs, or a toy that knows which figure is on it.

The sketch below uses the common Adafruit PN532 library over I2C to detect a tag you present and read its UID, then blinks an LED. It is a starting point for your own tap-to-act ideas — it reads tags you own, nothing more.

#include <Wire.h>
#include <Adafruit_PN532.h>

// PN532 over I2C. IRQ and RESET pins are optional on many boards.
Adafruit_PN532 nfc(-1, -1);
const int LED = 2;

void setup() {
  Serial.begin(115200);
  pinMode(LED, OUTPUT);
  Wire.begin();
  nfc.begin();
  if (!nfc.getFirmwareVersion()) {
    Serial.println("PN532 not found");
    while (1) delay(10);
  }
  nfc.SAMConfig();           // ready to read passive tags
  Serial.println("Tap one of your NFC tags");
}

void loop() {
  uint8_t uid[7];
  uint8_t len = 0;
  // Wait up to 100 ms for a 13.56 MHz tag in the field
  if (nfc.readPassiveTargetID(PN532_MIFARE_ISO14443A, uid, &len, 100)) {
    Serial.print("Tag UID:");
    for (uint8_t i = 0; i < len; i++) Serial.printf(" %02X", uid[i]);
    Serial.println();
    digitalWrite(LED, HIGH); delay(200); digitalWrite(LED, LOW);
  }
}

08FAQ

SGP Lab — written by the team that designs and builds SGP hardware in Europe. We test every example on our own boards before publishing.