What Is NFC: Range, Modes and Two Different Jobs
Home
Yiwu, Zhejiang, China
Mon – Fri 9:00 AM – 6:00 PM · Sat 9:00 AM – 4:00 PM
[email protected]

What Is NFC: Range, Modes and Why Payment Is a Different Job

Alan Xiao, Founder of Sourcing Pioneer
Alan Xiao Founder of Sourcing Pioneer
· Updated November 10, 2026 · 9 min read

NFC is a 13.56 MHz radio that reaches only a few centimetres.

Near field communication sits behind three everyday taps. One pays a bill, one opens a door, one reads a label on a box. All three feel identical to the user. Underneath they are different jobs, built from different pieces of the same standard.

That is where most explanations stop, and where most buyers start guessing. This page gives the numbers your supplier is quoting, tells you which number is which, and then separates the two jobs that get mixed together.

Studio still life of a phone, an NFC tag label and a contactless card on beige
One tap, three very different jobs.

The Short Answer

NFC is a set of short range radio rules. Two devices hold a connection when their antennas are close, usually within a few centimetres. One side can power the other.

The carrier sits at 13.56 MHz, in a band that needs no licence almost everywhere. Data moves at rates the standards state as 106, 212 and 424 kbit/s, and the Forum’s overview takes its upper end to 1.7 Mbit/s.

That is slow next to Wi-Fi. It is fast enough for a card number, a web address, or a pair of keys, which is the whole point. NFC is built for a small payload delivered in an instant.

It is also built so that a dead device still works. A tag with no battery answers because the reader’s field powers it. That single property creates most of the use cases people call NFC.

One Radio, Four Standards Underneath

“NFC” is not one protocol. It is a wrapper that lets one reader talk to several existing contactless families. The Forum lists what a certified device must be able to reach.

The Forum’s own technical overview sets out the families a device must reach. The first group is ISO/IEC 14443 Type A and Type B cards, ISO/IEC 15693 cards and ISO/IEC 18092 devices. The second group is JIS X 6319-4 cards, NFC Forum tags and other NFC Forum devices.

Those five families are why a phone can open a hotel door in one city and ride a bus in another. The card makers never agreed on one protocol. NFC is the layer that reads all of them.

For a buyer this matters at the quoting stage. A tag that is “NFC” may sit on any of those families. The chip you choose decides which phones will read it without a fight.

The package side is its own topic. If the tag lives inside a sealed product, what a sealed housing rating covers decides whether the antenna still works after a wash.

The Range Depends Who You Ask

Ask how far NFC reaches and you get four answers, all defensible, all different. They measure different things.

FigureWhat it describesWhere it comes from
4 cm or lessThe classic working distance of the protocol familyISO/IEC 18092 summaries and platform docs
Up to 2 cmTypical range the Forum quotes for a connectionForum technical overview
20 mmThe operating volume a test is measured insideForum Analog 3.0, as described in its spec list
5 mmThe range the Forum puts on its certificateForum technical overview

Read the table as four different questions, not four opinions. The protocol works at four centimetres. A product is tested inside a twenty millimetre volume. The certificate promises five millimetres.

That last line is the one buyers miss. The Forum states plainly that the certified range of an NFC Forum connection is 5 mm. A supplier who claims certification is claiming a five millimetre promise.

In practice you will see more than five millimetres on a desk. A large antenna, a thin battery and a clean field can push a tag to a couple of centimetres, and some readers reach further. That is margin, not contract.

So write the number you need, not the number you heard. If the user must find the spot on a curved housing, ask for the operating volume in the test report. That figure is what the design was measured against.

Diagram comparing the four published NFC range figures as nested bands
Four numbers, four different questions.

Why One Side Can Be Dead

The two antennas form a loosely coupled transformer. The reader drives its coil, and the field it makes reaches the tag’s coil. A tag with no cell turns that field into its own supply.

The tag then answers by changing how much load it presents. The reader sees that change as a pattern of bits. Engineers call it load modulation, and the Forum’s overview names it as one of the things its rules have to cover.

Power is small and strictly capped. The Forum puts the harvesting ceiling at 1 W. That is enough to run a memory chip and a little more.

It is not enough to run a motor, a screen, or a radio link. This is why a tap can start a connection but cannot carry the conversation. NFC hands the job to Bluetooth or Wi-Fi once the tap has done its part.

Since 2023 the same field can also charge. The Forum defines a wireless charging mode with two settings. One holds a steady field; the other negotiates a higher one in four classes of 250, 500, 750 and 1,000 mW.

Small wearables and styluses are the target. If you are weighing that against a pad, how a charging pad compares puts the two side by side. The short version: a pad moves far more power, an NFC coil fits where a pad cannot.

Three Modes, Four Roles, Two on Your Phone

The usual answer is “three modes”. Open the source documents and the count changes, which is why design reviews go sideways.

SourceWhat it countsThe list
Common shorthand3 modesCard emulation, reader and writer, peer to peer
Forum technical overview6 headingsThe three above, plus wireless charging, host card emulation, and secure element emulation
Digital Protocol spec4 rolesInitiator, target, reader and writer, card emulator
Android platform2 main modesReader and writer, card emulation

None of these is wrong. They answer different questions. The shorthand counts user experiences. The Forum counts how a device can behave. The protocol spec counts which end starts the exchange.

The Android line is the one that bites. Android’s two operating modes are reader and writer, and card emulation. A team that planned a peer to peer feature finds less support than the word “mode” suggested.

What this means for a purchase order is simple. Name the behaviour you are paying for, not the mode. “Reads a tag and opens a URL” is a behaviour. “Reader mode” is a label that three suppliers will implement three ways.

Diagram of NFC operating modes showing which side powers the field and where the data goes
Who powers the field decides who can be dead.

Payment Is Not Tag Reading

A tap to pay and a tap to read a label look the same and share nothing above the radio. Mixing them up is the most expensive mistake in this category, because the two need different parts.

Payment runs in card emulation. Your phone behaves like a contactless card, and the terminal runs its normal card dialogue. The Forum puts it plainly. The service provider does not need to know it is talking to a phone. It only needs the device to look like a card.

Inside the phone the card can live in two places. A secure element, either an embedded chip or a SIM, holds the keys and runs the commands. Or a host app emulates the card, and the controller forwards every command up to it.

Tag reading runs in reader and writer mode, and it carries a file format called NDEF. The tag stores an NDEF message. The phone parses it and acts: open a link, dial a number, join a network.

Those two paths never meet. A payment card holds no NDEF message, and a tag cannot move money. If a supplier offers you one chip that “does payments and labels”, ask which secure element holds the keys.

Ask a second question while you are there. Who is the payment scheme’s counterparty? Card emulation only pays if a bank or a wallet stands behind the credential. A tag with a URL behind it needs nobody’s approval.

This is why a “smart label” project can ship in one quarter and a payment project takes a year of certification. Same tap, different amount of other people’s rules.

What a Tag Actually Carries

A tag is a small memory chip with an antenna. What makes it readable by a phone is the format of the data, not the silicon. That format is NDEF, the NFC Data Exchange Format.

An NDEF message is a stack of records. Each record declares its type, so the phone knows what to do without being told in advance. A URI record opens a page. A text record shows words. A Smart Poster record bundles a link, a phone number or a message.

The Forum also defines a signature record. It signs the message so a phone can tell whether the data came from you and stayed unchanged. The spec is careful about what it does not do: it names no certificate authority and mandates no keys.

Under the data format sit five tag types. They are grouped by the radio family they use, which decides which phones read them easily.

Tag typeRadio familyWhat it is tied to
Type 1NFC-AOlder simple memory parts; its features were dropped from the 2021 release
Type 2NFC-AThe common cheap label chip
Type 3NFC-FJIS X 6319-4, the Japanese transit family
Type 4ISO-DEPISO/IEC 14443, on either NFC-A or NFC-B
Type 5NFC-VISO/IEC 15693

Memory is the line buyers haggle over, and it is the line that matters least. A single URI record fits in a few dozen bytes. Paying for a larger chip to store a link is paying for nothing.

Two other properties deserve a line in the drawing. One is whether the message can be locked read-only after writing. The other is whether the chip can be told apart from a copy.

NFC, RFID and Bluetooth

The three get mentioned together because they all move data through the air. They are built for different distances and different habits.

NFC is the short one. Its job is to start something: identify a thing, open a page, hand a pairing to a bigger radio. The Forum describes it as ultra short range with a fast start, where only one side needs power.

Bluetooth and Wi-Fi take over once the payload grows. That handover is a defined part of NFC, not a workaround. It is why a tap can pair a speaker and then let the audio run over Bluetooth.

A product that ships into Europe carries both questions. The radio side is one, and the CE and RoHS route for a wireless product is the other. A tag alone does not change the product’s duties.

Six Lines for the Order

Here is the version that survives a factory visit. Six lines, each one answerable, each one checkable against a sample.

One. State the behaviour, not the mode. “Tap opens this URL” or “tap pairs the speaker” leaves nothing to interpret.

Two. Name the tag type and the chip family, with the memory you actually need for the message.

Three. Say which range figure you are buying: the certified range, the operating volume in the test report, or a distance measured on your own housing.

Four. Give the antenna size and the place it will sit. Metal behind an antenna costs more range than any chip choice.

Five. Name the record types in the message, and whether the tag is locked after writing.

Six. Say what security you need, if any. A signed message is one answer; it is not the same as a payment credential.

Put those six on the sheet a factory quotes from, and the quotes you get back will be comparable. Without them, three suppliers will quote three different products and all call them NFC.

Checklist panel showing six lines to put on an NFC tag order
Six lines that make three quotes comparable.
TAP CHECK

Send me the tag page from your drawing, or the sample label you were given. I will check which family the chip sits on, which range figure is actually promised, and whether the message is locked. You get a one-page answer you can forward to the factory.

Check My Tag

Questions Buyers Ask

How far does NFC actually work?

Between 5 mm and about 4 cm, depending on which figure you mean. The protocol family is quoted at 4 cm, the Forum calls 2 cm typical, and its certified range is 5 mm.

Does an NFC tag need a battery?

No. The reader’s field powers it, and the Forum caps that harvested power at 1 W. The same field can now charge a small device in the wireless charging mode.

Can one chip do payments and labels?

Not in one role. Payment runs in card emulation with keys in a secure element or a host app. A label is a tag carrying an NDEF message. The radio is shared; the layers above it are not.

Why does my tag only work at one exact spot?

Usually antenna size and what sits behind it. Metal or a battery close to the coil eats the field. A larger coil and a gap of a few millimetres usually fix it.

Is NFC the same as RFID?

It grew out of it. NFC reuses the high frequency contactless families, 13.56 MHz, and wraps them in one set of rules. Long range inventory tags use other bands and other rules.

How much memory does a label need?

Very little. One web address fits in a few dozen bytes, which the smallest common label chip holds many times over. Buy memory only when you plan to store text on the tag.

Questions & Comments

We read every one and reply within 24 hours

If your tag only works when it is held at one exact spot, tell me where that spot is. That detail usually explains the whole problem.

Subscribe
Notify of
guest
0 Comments
Most Voted
Newest Oldest
0
Would love your thoughts, please comment.x
()
x