What is NFC Tag?
Dec 26, 2025
Leave a message
What is NFC Tag?
You have probably seen those little stickers in restaurants lately. In China they say "Tap to Order." You hold your phone against it, the menu pops up, you order food. No app download. No QR code scanning. That is NFC.
NFC tag is basically a passive RF chip with an antenna. No battery inside. Your phone's electromagnetic field powers it up when you get close enough. The chip wakes up, sends back whatever data it has stored, and the whole thing is done in under 100 milliseconds.
Quick answer: what does an NFC tag actually do?
An NFC tag is a small passive 13.56 MHz tag that contains an NFC chip and a loop antenna. It has no battery. When an NFC-enabled phone or reader comes close, the reader powers the tag through magnetic coupling, reads the stored NDEF data, and opens an action such as a URL, contact card, WiFi setup, authentication page, or access credential.
For most business projects, a phone-readable NFC tag is not used to store a large file. It usually stores a short NDEF record, especially a web link that sends the user to a menu, product page, warranty page, authentication page, review page, membership page, or digital business card. If you are comparing tag forms for a new project, start with custom NFC tags and stickers for phone-readable product labels before choosing the chip and material.
The part most people get wrong
NFC is RFID. Specifically it is high-frequency RFID at 13.56 MHz with some extra features bolted on. When someone asks whether to use NFC or RFID, they are asking the wrong question. The real question is which frequency band fits the use case. For a deeper system-level comparison, see this guide on RFID and NFC technology comparison for system selection.
UHF RFID
UHF RFID at 860-960 MHz can scan many tags from meters away. Great for warehouse inventory, retail stock counting, and logistics gates. But your phone cannot read UHF tags. You need dedicated hardware.
NFC
NFC works with phones and close-range readers. That is the whole point. It is best for consumer-facing applications where you want people to interact using a device they already carry.
NFC tag vs QR code vs UHF RFID
These three technologies often appear in the same project brief, but they solve different problems. A QR code is cheap and visible. An NFC tag feels smoother because the user taps instead of opening a camera. UHF RFID is better when a business needs to read many items automatically without individual taps.
| Option | Best Use | Main Limitation | Practical Buyer Note |
|---|---|---|---|
| NFC tag | Tap-to-open product information, authentication, access, reviews, membership, smart packaging | Short read distance and one-user interaction | Good when the experience should feel intentional and phone-friendly. |
| QR code | Low-cost printed link on packaging, flyers, labels, or menus | Must be visible and scanned by camera | Useful backup even when an NFC tag is embedded in the same label. |
| UHF RFID | Warehouse inventory, apparel counting, logistics, asset tracking | Phone cannot read it directly | Choose it for speed and range, not for customer tap interaction. |
If the project needs both bulk inventory and customer interaction, the answer may be dual technology: UHF for backend operations and NFC for the consumer-facing tap experience.
Let me explain how the power transfer actually works
This is where it gets interesting from an engineering standpoint.
NFC operates at 13.56 MHz which gives you a wavelength around 22 meters. Communication happens at maybe 5 centimeters. That is way shorter than one wavelength so you are firmly in the near-field region. Forget about electromagnetic wave propagation. What matters here is magnetic field coupling between two coils acting like an air-core transformer.
Phone antenna generates an alternating magnetic field. Tag antenna sits in that field. Changing magnetic flux through the tag coil induces a voltage. Rectifier circuit on the chip converts AC to DC. Chip powers up.
Energy Harvest
The reader field provides enough energy for the chip logic, memory access, and short data exchange. The exact harvested power depends on chip, antenna size, reader field strength, alignment, and surrounding material.
Load Modulation
Data goes back through load modulation. Tag varies its antenna impedance which creates ripples in the phone antenna's current waveform. Phone decodes those ripples. Standard rate is 106 kbps. Some chips and modes support higher rates.
NDEF is what makes the tap useful
The chip and antenna only provide the physical connection. The useful action comes from the data format. Most phone-readable NFC tags use NDEF, short for NFC Data Exchange Format. NDEF tells the phone whether the tag contains a URL, text, contact card, WiFi configuration, app link, or another supported record type.
Most NFC tags store a small NDEF message rather than a large file. Common records include a web URL, vCard contact, WiFi configuration, app deep link, plain text, or an authentication URL. For commercial projects, storing a short URL is usually better than storing all product data directly on the chip.
- For menus, reviews and marketing: store a short URL and update the web page when content changes.
- For business cards: use a URL to a live profile if the contact details may change; use vCard only when offline contact transfer matters.
- For product authentication: use a unique URL or a cryptographic response instead of a static plain text code.
- For access control: match the tag chip with the reader, controller and security level, not just the frequency.
Chip selection is where projects succeed or fail
I want to spend some time on this because I have seen too many projects pick the wrong chip.
NFC Forum defines tag types. Type 1 is now rarely chosen for new commercial projects. Type 3 is FeliCa which matters mainly in Japan and some transport/payment ecosystems. Type 5 is based on NFC-V / ISO 15693 and can be useful when a larger antenna and longer read range are needed. For most consumer phone-tap applications you are choosing between Type 2 and Type 4.
Type 2: The Workhorse
NTAG213, NTAG215, NTAG216
Type 2 often means the NTAG series from NXP. NTAG213, NTAG215, NTAG216. Same chip family, different memory sizes. NXP describes NTAG213, NTAG215 and NTAG216 as NFC Forum Type 2 / ISO/IEC 14443 Type A compliant ICs for mass-market uses such as retail, gaming and consumer electronics; the original chip reference is available in the NXP NTAG213, NTAG215 and NTAG216 product specification.
Memory Reality
Here is what nobody tells you until you read the datasheet carefully. Memory is organized in 4-byte pages. NTAG213 has 144 bytes of user memory, which is usually enough for a short URL, a review link, a social media link, or a basic product landing page. NTAG215 and NTAG216 add more memory, but larger memory is not automatically better if the real payload is only a short web address.
Basic Security
Password protection and lock bits can prevent casual overwriting, but they should not be confused with strong authentication. A standard Type 2 tag is fine for simple marketing and identification links. It is not the right chip when every tap must prove that the physical item is genuine.
The NFC counter is useful for simple clone detection. A dynamic URL can mirror a changing value into the link so a backend server can check whether the tap sequence makes sense. That improves basic monitoring, but high-value anti-counterfeiting normally needs stronger cryptographic tags.
One thing that bites many projects: a client asks for NTAG216 for "headroom" while the actual payload is a 60-90 byte short URL. In that case NTAG213 may be enough. Check the real NDEF length first, then choose memory. Do not pay for chip capacity that the application never uses.
Which NFC chip should you choose?
| Chip / Tag Type | Good Fit | Avoid When | Typical Buyer Search Intent |
|---|---|---|---|
| NTAG213 / Type 2 | URL labels, Google review tags, smart posters, basic packaging, simple tap-to-open campaigns | You need a long vCard, large offline payload, or advanced authentication | NTAG213 NFC sticker for URL campaigns |
| NTAG215 / Type 2 | Medium NDEF payloads, game figures, use cases needing more memory than NTAG213 | The data is only a short web link | NTAG215 tag for medium memory NFC projects |
| NTAG216 / Type 2 | Longer contact data, larger NDEF records, business card projects that must store more information offline | You can host the content online and store a short URL instead | NTAG216 NFC business card memory selection |
| NTAG424 DNA / Type 4 | Brand authentication, secure product identity, one-time URL, higher-value goods | The project only needs a simple public URL | secure NFC tag for anti-counterfeiting |
| Type 5 / ISO 15693 based tag | Some library, industrial, or longer-range HF use cases with suitable readers | You only need ordinary smartphone marketing taps | longer range HF NFC compatible tag |
Choose NTAG213 for simple URL campaigns, product labels, and smart posters. Choose NTAG215 or NTAG216 only when the stored NDEF message is larger. Choose a secure Type 4 chip such as NTAG424 DNA when each tap must generate a protected authentication response for anti-counterfeiting or high-value product verification.
Type 4 is different architecture
NTAG424 DNA is a common example here. It uses an ISO 7816-4 style file system structure instead of the flat page memory model used by many Type 2 tags. This changes how data, access rights, and secure features are managed.
The security model is completely different. A secure Type 4 tag can support AES-based authentication, protected file access, and dynamic message authentication. Every tap can be designed to produce a unique response, which is why this class is used for brand protection, high-value product authentication, and secure closed-loop applications.
Luxury Usage
Luxury brands and premium goods use secure NFC tags because the tap can connect a physical item to a controlled digital verification flow. The important point is not just "the tag opens a page"; the important point is whether the backend can verify that the response belongs to a real tag.
Endurance
Endurance and data retention matter when a tag will be rewritten many times, exposed to harsh handling, or used in a long-life product. For single-use marketing stickers, this is rarely the deciding factor. For industrial tags, it can be.
Architecture
Type 4 tags can use a file-based structure, stronger access control, and cryptographic authentication. That is why they cost more but solve problems that a simple NTAG213 sticker cannot solve.
The metal problem
This comes up constantly. Someone wants to put NFC tags on metal products and discovers they do not work.
What happens is the metal acts as a conductor in a changing magnetic field. Eddy currents form inside the metal and create an opposing magnetic field. Your antenna inductance drops, Q-factor changes, and the resonant frequency shifts away from 13.56 MHz. Read distance goes to basically zero.
Standard solution is ferrite sheet between antenna and metal. The ferrite helps redirect magnetic flux. You recover some inductance and the antenna starts working again.
WARNING
Ferrite helps, but you still need to test the final tag size, adhesive layer, product surface, phone model, and read angle. A tag that works on a plastic sample card may fail after it is attached to aluminum, stainless steel, coated metal, or a curved product housing.
If you are designing for metal environments, budget time for iterative matching adjustments. You will need a VNA or at minimum an LCR meter for engineering validation. For production sourcing, compare anti-metal NFC sticker designs for metal surfaces instead of ordinary paper NFC labels.
Form factor matters as much as chip selection
The same chip can behave differently when the antenna diameter, substrate, glue, surface material, and printing layer change. That is why a buyer should not select an NFC tag only by saying "NTAG213" or "13.56 MHz." The finished tag construction matters.
- Paper NFC labels: cost-effective for disposable marketing labels, event stickers, and smart posters.
- PET or PVC NFC stickers: better for handling, moderate durability, product labels, and cards.
- Epoxy NFC tags: useful when the tag needs a raised, glossy, waterproof surface for phone backs, keychains, or branded plates.
- FPC NFC labels: useful for small sizes, flexible surfaces, and compact electronics.
- Anti-metal NFC tags: required when the tag is attached to metal, foil packaging, metal business cards, machines, tools, or electronic housings.
For normal non-metal applications, review adhesive NFC sticker options for posters, packaging, and business cards. For metal packaging or equipment labels, use a ferrite-backed construction and test it on the real object, not just on a desk.
Phone compatibility reality
Android Ecosystem
Android has been friendly to NFC since early days. HCE in Android 4.4 let apps emulate cards without secure element hardware. Read/write works on most Android phones that include NFC hardware.
The Apple Lag
Apple was the problem for years. iPhone 6 had NFC in 2014 but it was locked mainly to Apple Pay. iOS 11 in 2017 allowed reading NDEF data. iOS 13 added more Core NFC capabilities. Older iPhone behavior still matters if your audience uses older devices.
The Turning Point
Apple announced that starting with iOS 18.1, authorized developers can offer in-app NFC contactless transactions using the Secure Element, separate from Apple Pay and Apple Wallet. That matters for payments, corporate badges, hotel keys, loyalty and event tickets, although entitlement and regional limits still apply. See Apple's NFC and Secure Element API announcement.
In practice, you can assume many modern users can tap standard NFC tags, but do not skip phone testing. Test iPhone and Android separately, test with and without a phone case, and test the exact tag placement. For user-side testing steps, this related guide explains how to use NFC on a phone for tag testing.
Quick note on standards
ISO/IEC 14443
ISO/IEC 14443 covers contactless smart cards. Type A and Type B modulation schemes. This is the foundation for many Type 2 and Type 4 NFC tags.
ISO/IEC 18092
ISO/IEC 18092 is NFCIP-1, the device communication protocol behind NFC peer communication.
ISO/IEC 15693
ISO/IEC 15693 is the vicinity card standard that Type 5 NFC tags build on.
NFC Forum
NFC Forum publishes implementation specifications on top of these standards, including tag type definitions and NDEF behavior. See the NFC Forum tag type specifications.
NFC Forum announced Release 15 in June 2025, extending the range of certified compliant NFC contactless connections up to 2 cm, compared with the previous 0.5 cm operating volume. That should make alignment less finicky in future certified devices, but it does not remove the need to test today's tag, phone and surface combination. See the official NFC Forum Release 15 announcement.
Project checklist before ordering NFC tags
Before bulk production, do not stop at "the tag can be read." A production-ready NFC tag project should pass these checks:
- Define the tap action: URL, vCard, WiFi, authentication, access credential, app link, or reader-specific data.
- Calculate the real NDEF length: confirm whether NTAG213 is enough or whether NTAG215/216 is actually needed.
- Choose the physical format: paper, PET, PVC, epoxy, FPC, card, key tag, wristband, or anti-metal construction.
- Test the real surface: plastic, glass, cardboard, liquid packaging, foil, aluminum, stainless steel, curved housing, or phone back.
- Test real phones and readers: at least several iPhone and Android models, plus any dedicated reader used in the project.
- Decide lock strategy: leave rewritable for internal use, lock after encoding for public campaigns, or use stronger authentication for secure projects.
- Verify print and QR backup: make sure the printed design does not confuse users and that a QR code backup exists if the campaign needs maximum accessibility.
- Run pilot sampling: test finished samples from actual production materials before approving mass production.
If you plan to encode tags in-house, use NFC reader and writer hardware for encoding and testing tags instead of relying only on a phone app. Phone apps are convenient for quick checks, but a reader/writer is more stable for batch workflows and production verification.
FAQ about NFC tags
Q: Can NFC Tags Be Rewritten?
A: Many NFC tags can be rewritten before they are locked. NTAG213, NTAG215 and NTAG216 are commonly used as writable tags. Once you permanently lock certain memory areas, normal users cannot rewrite those sections again.
Q: Can An NFC Tag Track A Person?
A: A passive NFC tag cannot track someone by itself because it has no battery, GPS, or long-range transmitter. It only responds when a phone or reader comes very close. A website opened by the tag may collect analytics after the user taps, so privacy depends on the web service behind the tag.
Q: Why Does My NFC Tag Read On One Phone But Not Another?
A: The most common reasons are antenna alignment, phone case thickness, tag size, weak antenna design, metal interference, or unsupported data format. Always test the final tag with the actual phone models your users are likely to carry.
Q: Should An NFC Business Card Store All Contact Details Or Just A URL?
A: A URL is usually better because you can update the landing page later. A vCard stored directly on the tag can work offline, but it consumes more memory and becomes outdated when the contact details change.
Q: Do NFC Tags Work Through Packaging?
A: Usually yes if the packaging is paper, cardboard, plastic, or glass and the tag antenna is large enough. Foil, metalized film, liquid-filled packaging, and metal containers require special testing and often need an anti-metal or custom antenna design.
So what is an NFC tag
Passive RF device. Powered by electromagnetic coupling at 13.56 MHz. Stores a small NDEF message or secure application data. Readable by NFC-enabled smartphones and compatible readers. Memory ranges from small URL payloads to larger NDEF records depending on chip. Security ranges from basic password protection to cryptographic authentication.
Pick Type 2 NTAG21x for cost-sensitive consumer applications. Pick Type 4 secure tags when you need real authentication. Use anti-metal construction when the label sits on metal. Account for material, antenna size, adhesive, phone model and reader behavior before bulk production.
That is the practical summary.
Send Inquiry