NFC Tag Types Explained
Type 1 through Type 5 classifications
Guide to all five NFC Forum tag types with memory specs, speeds, and compatible chips. Learn the differences between each classification and when to choose one over another for your project.
NFC Tag Types Explained
The NFC Forum defines five standardized nfc-tag types, each based on a different underlying RF protocol. Understanding these types is essential for selecting hardware that matches your application's memory, speed, and security requirements.
Why Tag Types Exist
NFC emerged from the convergence of multiple RFID standards. Rather than mandate a single physical layer, the NFC Forum created an abstraction: a common NDEF data model that sits on top of each protocol. Tag types differ in their underlying RF standard, memory capacity, and access control features, but all support NDEF storage when formatted correctly.
Tag Type Comparison
| Feature | Type 1 | Type 2 | Type 3 | Type 4 | Type 5 |
|---|---|---|---|---|---|
| RF Standard | ISO 14443-3A | iso-14443 Type A | nfc-f (JIS X6319-4) | ISO 14443-4 A/B | iso-15693 |
| Air interface | nfc-a | nfc-a | NFC-F | NFC-A / nfc-b | nfc-v |
| Memory (typical) | 96 B | 64–888 B | 2 KB | 2–64 KB | 8–64 KB |
| Data rate | 106 kbit/s | 106 kbit/s | 212/424 kbit/s | 106 kbit/s | 26.5 kbit/s |
| Example chips | Topaz 512 | NTAG213/215/216 | Sony FeliCa | MIFARE DESFire | ICODE SLI |
| Typical use | Simple URLs | General-purpose | Transit, loyalty | Secure access | Item-level RFID |
Type 2 Tags: The Consumer Default
Type 2 tags — particularly the NTAG2xx family — dominate consumer NFC deployments. They are cheap ($0.05–$0.20), widely supported, and offer enough memory (144–888 bytes of user-memory) for URLs, vCards, and Wi-Fi credentials. The uid is 7 bytes, guaranteed unique from the factory.
Type 4 Tags: Security-First
Type 4 tags implement the full ISO 14443-4 command set, enabling T=CL transport. They support password-protection and optionally aes-encryption, making them suitable for access control and authentication applications where Type 2's simple lock bits are insufficient.
Type 5 Tags: Long Range
Type 5 (nfc-v) operates under ISO 15693, which supports read ranges up to 1 m with suitable readers — far beyond the 4 cm limit of Types 1–4. This makes Type 5 useful for supply chain item tracking where the tag is embedded in packaging and readers must work without precise alignment.
Choosing a Tag Type
- Consumer interaction (tap-to-open URL, social): Type 2 (NTAG213)
- High-memory payloads (vCard, config data): Type 2 (NTAG216) or Type 4
- Secure authentication / access control: Type 4 (DESFire EV3)
- Transit / loyalty with fast read: Type 3 (FeliCa)
- Supply chain, item-level, long range: Type 5 (ICODE SLIX2)
Use the NFC Chip Selector to filter by tag type, memory, and security features. The NFC Memory Calculator helps size your NDEF payload against available user-memory.
See also: NFC Chip Comparison Guide for a deeper look at specific silicon families.
Frequently Asked Questions
The NFC Forum defines five interoperability profiles — Type 1 through Type 5 — that specify how data is stored and accessed on passive NFC tags. These types map to physical chip families: Type 1 covers Topaz/Jewel, Type 2 covers NTAG/Ultralight, Type 3 covers Sony FeliCa, Type 4 covers MIFARE DESFire and MIFARE Plus, and Type 5 covers ISO 15693 tags like ICODE. Choosing the right type ensures compatibility with all NFC Forum-compliant reader devices.
NFC Forum Type 2 tags — particularly NXP's NTAG213, NTAG215, and NTAG216 — are the most widely deployed for consumer applications such as smart posters, product authentication, and social media links. They offer an excellent balance of low cost (under $0.30 per tag at volume), broad smartphone compatibility, and sufficient memory (144–888 bytes of user NDEF storage) for typical URL or vCard payloads.
Type 2 tags (NTAG21x, Ultralight) use a simple byte-array memory model with optional 32-bit password protection, making them fast and inexpensive. Type 4 tags (DESFire, MIFARE Plus) use an ISO 7816 APDU command structure with hardware-backed AES-128 mutual authentication, making them far more secure and suitable for payments, public transit, and access control — but at higher cost and slightly longer transaction times.
iPhones running iOS 13 and later support background reading of Type 1, 2, 3, 4, and 5 tags with no app required. However, writing to tags and performing advanced APDU operations on Type 4 tags requires a third-party app using Core NFC. Type 3 (FeliCa) is only available on the iPhone 8 and later with regional FeliCa support (primarily in Japan).
Our guides cover a range of experience levels. Getting Started guides are written for beginners with no prior NFC knowledge. Programming guides target developers integrating NFC into mobile apps or embedded systems. Security guides are for engineers designing secure NFC deployments for payments, access control, or authentication.
Most guides require only an NFC-enabled smartphone (iPhone 7+ or any modern Android device) and a few NFC tags (NTAG213 or NTAG215 recommended for beginners, available for under $1 each). Advanced guides may reference USB NFC readers like the ACR122U or Proxmark3 for development and testing.
Yes. Programming guides include code examples for Android (Kotlin/Java with the Android NFC API), iOS (Swift with Core NFC), and web-based tools (Web NFC API for Chrome on Android). All code samples are tested and include inline comments explaining each step.