NFC tags may look simple from the outside, but the technology inside them is not all the same. NFC operates at 13.56 MHz, and most NFC tags are passive devices with no battery of their own. When a phone or NFC reader comes close, its electromagnetic field supplies the energy the tag needs to communicate.
When people talk about “types of NFC tags,” however, they may be referring to several different things. NFC Forum Tag Type describes the communication architecture of the tag. A name such as NTAG213 identifies the specific IC inside it, while terms such as NFC sticker, card, or wristband describe the physical format. Keeping these categories separate makes the differences between NFC products much easier to understand.
What Are the Different Types of NFC Tags?
The NFC Forum defines five tag types, Type 1 through Type 5. Each type uses a particular NFC communication technology and defines how an NFC-enabled device detects the tag and exchanges data with it.
One term that appears frequently in these specifications is NDEF, short for NFC Data Exchange Format. NDEF provides a standardized way to store application data on NFC tags. A tag might contain an NDEF record for a website URL, text, or another supported data type.
Here is a quick comparison of the five NFC Forum Tag Types:
| NFC Forum Type | NFC Technology | Related Standard | Representative Technology / IC | Common Context |
| Type 1 | NFC-A | ISO/IEC 14443 Type A RF technology | Topaz / Jewel | Legacy simple NFC applications |
| Type 2 | NFC-A | ISO/IEC 14443 Type A | NTAG21x, MIFARE Ultralight | General-purpose NFC tags |
| Type 3 | NFC-F | JIS X 6319-4 | FeliCa | Transit and electronic money |
| Type 4 | ISO-DEP over NFC-A or NFC-B | ISO/IEC 14443 series | MIFARE DESFire | Smart cards and advanced applications |
| Type 5 | NFC-V | ISO/IEC 15693 | ICODE, ST25TV | Identification and industrial applications |
NFC Type 1 Tags
NFC Type 1 uses NFC-A technology and was designed for relatively simple read/write applications. Topaz and Jewel are the names most often associated with this category. Like the other NFC Forum tag specifications, Type 1 defines how a reader detects the tag and accesses an NDEF message rather than defining one particular physical tag product.
Type 1 matters today mainly for historical context. The NFC Forum still lists the Type 1 Tag Specification, but Type 1 support was removed from the Digital Protocol and other device specifications beginning with Technical Specification Release 2021. As a result, it is best treated as a legacy NFC technology rather than a normal choice for a new NFC project.
That leaves Type 2 as the much more relevant starting point for the simple NFC tags people commonly use with phones.
NFC Type 2 Tags
NFC Type 2 also communicates through NFC-A, but it has become a widely used platform for general-purpose NFC tags. The NFC Forum Type 2 specification defines how an NFC device detects the tag and reads or writes its NDEF data, while individual IC manufacturers build different memory sizes and features on top of that framework.
You will commonly find Type 2 ICs inside NFC labels, stickers, cards, and embedded product tags. They work well for applications where the tag needs to hold information that a phone or reader can retrieve with a tap, such as a URL, product data, pairing information, or a digital business card. NXP, for example, positions its NTAG21x family for consumer engagement, product authentication, electronic shelf labels, Bluetooth or Wi-Fi pairing, and similar mass-market uses.
Common Type 2 NFC Chips
Type 2 covers a range of compatible ICs. NTAG213, NTAG215, and NTAG216 are among the most widely used examples, especially in NFC labels, stickers, cards, and other general-purpose tags. They share the same Type 2 communication framework, while their user memory and some chip-level features differ.
| Chip | User Memory | Typical Reason to Use It |
| NTAG213 | 144 bytes | Short NDEF records such as ordinary URLs and basic contact information |
| NTAG215 | 504 bytes | Applications that need more encoded data |
| NTAG216 | 888 bytes | Larger NDEF messages where the smaller chips do not provide enough space |
The three chips share several functions beyond basic data storage. NTAG21x provides a manufacturer-programmed 7-byte UID, an ECC-based originality signature, field-programmable read-only locking, and configurable 32-bit password protection. The password can restrict unauthorized memory operations, but it should not be mistaken for encrypted NFC communication. NXP also rates this family for 100,000 write cycles and 10 years of data retention.
The main reason to move from NTAG213 to NTAG215 or NTAG216 is therefore usually capacity, not a different NFC Forum Tag Type. All three remain Type 2 tags and communicate at 106 kbit/s.
NFC Type 3 Tags
NFC Type 3 uses NFC-F technology and is compatible with the Japanese Industrial Standard JIS X 6319-4. It is closely associated with Sony FeliCa, a contactless technology widely used in public transport ticketing and electronic money systems, especially in Japan and other Asian markets.
NFC-F supports 212 and 424 kbit/s communication, which suits applications that require quick transactions. FeliCa is also used for access control and identification, although Type 3 is less common in general-purpose NFC stickers and labels than Type 2.
NFC Type 4 Tags
NFC Type 4 uses ISO-DEP (ISO Data Exchange Protocol) over NFC-A or NFC-B and is compatible with the ISO/IEC 14443 standard series. It supports the command-based communication used in contactless smart cards and can handle more complex data exchange than the simpler tag architectures.
MIFARE DESFire is one of the best-known IC families associated with Type 4 applications. DESFire chips use ISO/IEC 14443-4 communication, and products such as MIFARE DESFire EV3 are NFC Forum Type 4 Tag compliant. They are widely used in public transport, access control, campus cards, and other credential systems where the card needs to manage protected data or multiple applications.
MIFARE DESFire EV3 supports AES-128 cryptography, mutual authentication, encrypted communication, and application-level access rights. It can also communicate at 106, 212, 424, or 848 kbit/s. These capabilities come from the DESFire EV3 IC itself; other Type 4 ICs can offer different memory, security, and performance specifications.
NFC Type 5 Tags
NFC Type 5 uses NFC-V technology and is based on ISO/IEC 15693, the standard used for vicinity RFID systems. Type 5 tags can support NFC interaction with compatible smartphones while also working with ISO/IEC 15693 HF RFID readers, giving them a useful role in applications that combine mobile access with longer-range identification.
NXP ICODE and STMicroelectronics ST25TV are well-known Type 5 IC families. They are used in areas such as asset tracking, inventory, product identification, and supply-chain applications. Type 5 tags support NDEF, so the same tag can also provide information to an NFC-enabled phone.
With a dedicated HF RFID reader and suitable antenna, ISO/IEC 15693 tags can operate at much greater distances than they do with a phone. NXP specifies operating distances of up to 1.5 meters for ICODE with long-range HF readers, depending on antenna geometry, while mobile NFC communication remains within a few centimeters. Type 5 systems also support anti-collision, allowing a reader to identify multiple tags within its field.
Security is again chip-specific. ICODE SLIX2, for example, provides an 8-byte UID, block-level write locking, 32-bit password-protected read and write access, and a 32-byte originality signature. NXP rates it for 100,000 write cycles and 50 years of data retention. Other Type 5 ICs offer different protection mechanisms.
Common NFC Tag Types by Physical Format
NFC tags are also commonly grouped by their physical construction. The same NFC IC can be built into very different products depending on where the tag will be used, how it will be attached, and how much protection it needs.
NFC Inlays
An NFC inlay is the functional core of many finished NFC tags. It combines the IC and antenna on a thin substrate and can later be converted into a label or embedded inside another product.
A dry inlay contains the chip, antenna, and substrate. A wet inlay adds an adhesive layer, making it easier to laminate into labels or attach during manufacturing.
NFC Stickers and Labels
NFC stickers and labels place an NFC inlay inside a thin adhesive construction. They are widely used on packaging, promotional materials, product labels, and other surfaces where a low-profile tag is useful.
The IC inside can vary according to the application. A simple URL label may use a Type 2 chip such as NTAG213, while another label may use a different IC when more memory or different functions are required.
NFC Cards
NFC cards package the chip and antenna inside a rigid or semi-rigid card body. Common applications include digital business cards, membership cards, identification, and access credentials.
The card format itself does not determine the NFC technology inside. Different cards can use Type 2, Type 4, or other compatible contactless ICs depending on what the system needs.
NFC Key Fobs
NFC key fobs place the tag inside a compact housing that can be carried on a key ring. Their enclosed construction gives the chip and antenna more physical protection than a thin paper or plastic label.
They are commonly used for identification, access control, and other applications where the tag needs to be carried and tapped repeatedly.
NFC Wristbands
NFC wristbands integrate the chip and antenna into a wearable form. They are widely used for events, visitor identification, cashless payments, and access systems.
The construction can vary considerably. Silicone wristbands suit repeated use, while disposable event wristbands may use lighter materials designed for shorter service periods.
NFC Anti-Metal Tags
NFC performance changes when a conventional tag is placed directly on metal because the metal interferes with the tag’s antenna field. Anti-metal NFC tags include a shielding or isolation layer that allows the antenna to operate properly on metallic surfaces.
They are useful for equipment, tools, machinery, and other metal assets where a standard NFC label may have poor or inconsistent performance.
Other physical formats include epoxy tags, textile tags, and embedded NFC components. These follow the same basic idea: the chip and antenna are packaged in a form that suits the environment and intended use.
Does NFC Tag Type Affect Phone and Reader Compatibility?
Phone and reader compatibility depends on the NFC technology and protocol supported by the device. NFC-A, NFC-B, NFC-F, ISO-DEP, and NFC-V are handled differently at the hardware and software level.
For iPhone, Apple’s Core NFC framework supports reading NDEF-formatted NFC Forum Type 1 through Type 5 tags. App-based NFC tag reading was introduced with iPhone 7, and Apple expanded Core NFC in iOS 13 to support NDEF writing and native access to ISO 7816, MIFARE, ISO 15693, and FeliCa tags on supported iPhones.
Apple also introduced background NFC tag reading with the iPhone XS, XS Max, and XR generation. On iPhones that support this feature, an NDEF tag can be detected without first opening an NFC reader app. Background scanning remains read-only and requires NDEF-formatted content.
Native tag access gives apps more control than standard NDEF reading. Core NFC provides interfaces for ISO 15693, FeliCa, ISO 7816, and MIFARE technologies, so an app can communicate with supported tags through their native protocols when needed.
Android also supports several NFC technologies directly, including NFC-A, NFC-B, NFC-F, NFC-V, and ISO-DEP. Support for some proprietary technologies can depend on the phone’s NFC hardware; for example, Android defines MIFARE Classic support as optional.
Dedicated NFC and HF RFID readers vary even more. A reader may support ISO/IEC 15693 Type 5 tags, ISO/IEC 14443 technologies, or several protocols in the same device. For projects that use a particular IC or native command set, compatibility should therefore be checked against the exact phone or reader that will access the tag.
Frequently Asked Questions
Are NFC tags reusable?
Many NFC tags are rewritable and can be programmed with new data multiple times. Whether a tag remains reusable depends on the IC and how its memory has been configured. If the relevant memory area has been permanently locked as read-only, it can no longer be rewritten.
Can one NFC tag work with both iPhone and Android?
Yes. Standard NDEF-formatted NFC tags, especially common Type 2 tags, can generally work with both iPhone and Android devices that support NFC.
Compatibility can differ when an app needs to use a chip’s native protocol or proprietary features. In that case, check support for the specific IC on the target phones.
Can NFC tags work without an internet connection?
Yes. A phone or reader can read data stored directly on an NFC tag without an internet connection.
Internet access is only needed when the tag points to online content. For example, a stored text record can be read offline, while a URL requires a connection to load the webpage.
Can NFC tags be copied or cloned?
Data stored in an ordinary NFC tag can often be read and written to another compatible tag. How much of the original tag can be reproduced depends on the IC and its security features.
Some chips include manufacturer-programmed identifiers, originality signatures, password protection, or cryptographic authentication. These features can make it possible for a system to distinguish an authentic tag from a simple copy of its stored NDEF data.
Can you use NFC tags on metal?
Yes, but tags intended for direct mounting on metal should use an anti-metal construction. These tags include a shielding or isolation layer that helps the NFC antenna operate correctly near the metal surface.
A standard NFC sticker placed directly on metal can have poor read performance or fail to read.
How much data can an NFC tag store?
Storage capacity depends on the IC. For example, NTAG213 provides 144 bytes of user memory, NTAG215 provides 504 bytes, and NTAG216 provides 888 bytes.
A short URL usually needs relatively little space, while longer text or multiple NDEF records require more memory. Check the encoded NDEF size before selecting the chip for applications that store more than a simple link.
Which NFC tag type is best for most smartphone projects?
NFC Forum Type 2 is the most practical choice for many everyday smartphone projects. It is widely used for NFC stickers, labels, cards, and similar products that store URLs, contact information, product data, or other NDEF content.
NTAG213 is often sufficient for short records such as URLs. NTAG215 and NTAG216 provide more user memory when the tag needs to store larger NDEF messages.
Find the Right NFC Tag for Your Application
Need help choosing the right NFC tag type? We supply and customize NFC tags for different products, environments, and reading requirements.
Tell us how the tag will be used, and we can help you select a suitable NFC solution for your project.