NFC Type 4 vs Type 5

NFC Forum Type 4 vs Type 5: Proximity Security vs Vicinity Range

NFC Forum Type 4 and Type 5 represent the two highest capability tiers in the NFC ForumNFC ForumIndustry body developing NFC standards, specifications, and certifications since 2004View full →'s five tag type taxonomy — but they are built on entirely different underlying standards and optimized for entirely different use cases. Type 4 is the security- and application-complexity tier, based on ISO 14443 Type A/B with AES-128 encryption. Type 5 is the long-range vicinity tier, based on ISO 15693 with read ranges up to 1.5 m. Understanding their architecture reveals why you cannot substitute one for the other.

Overview

NFC Forum Type 4 is defined in the NFC Forum T4T Technical Specification. It is built on ISO 14443ISO 14443Standard for contactless smart cards at 13.56 MHz (Types A and B)View full → Type A or B, using the ISO 7816-4 APDU command layer. Key Type 4 implementations:

• NTAG 424 DNA (NXP): AES-128 + Secure Dynamic Messaging (SDM), per-tap cryptographic URL, 256 bytes user memory. NFC Forum Type 4 certified.
• MIFARE DESFire EV1/EV2/EV3 (NXP): Multi-application file system, AES-128 + ECC (EV3), 2–32 KB memory, ISO 7816-4 APDU, NFC Forum Type 4 via NDEF wrapper.
• ST25TA (ST): Dual-interface (NFC + I2C), Type 4 certified.

NFC Forum Type 5 is defined in the NFC Forum T5T Technical Specification. It is built on ISO 15693 — the vicinity coupling standard at 13.56 MHz that achieves read ranges up to 1.5 m. Key Type 5 implementations:

• ICODE SLIX2 (NXP): 2,528 bits (316 bytes) user memoryuser memoryTag memory portion available for user data storageView full →, EAS (Electronic Article Surveillance) functionality, password protectionpassword protection32-bit access control for memory areas (plaintext transmission)View full →, privacy flag.
• ST25TV (ST): 512–2048 bytes user memory, ISO 15693ISO 15693Standard for vicinity-range smart cards, 1+ meter read rangeView full → + NFC Forum Type 5 certified.
• TI Tag-it HF-I (Texas Instruments): Classic ISO 15693 tag, widely used in library and pharmaceutical RFID.

Key Differences

• Underlying standard: Type 4 is ISO 14443 (proximity, ~10 cm). Type 5 is ISO 15693 (vicinity, up to 1.5 m). This single difference drives most other trade-offs.
• Read rangeRead rangeMaximum communication distance between reader and tagView full →: Type 4: 0–10 cm (deliberate tap). Type 5: 0.5–1.5 m (passive read at distance, or bulk reading through a gate).
• Data rate: Type 4 (ISO 14443 Type A at 106 kbps). Type 5 (ISO 15693 at 26.48 kbps high rate). Type 4 is ~4x faster.
• Security: Type 4 offers full AES-128 encryption (NTAG 424 DNA, DESFire EV3). Type 5 chips offer password protection and privacy flags — no AES-128 native to the ISO 15693 standard.
• NDEF support: Both support NDEF — Type 4 uses ISO 7816-4 APDU- based NDEF access; Type 5 uses the T5T memory-mapped NDEF model (flat block array, similar to Type 2 but at ISO 15693 addressing).
• Smartphone support: Type 4 is supported as NFC-A or NFC-B by all NFC smartphones universally. Type 5 is NFC-V — supported in Android (API 16+) and iOS (iPhone 7+, iOS 11+ via Core NFC).
• Anti-collisionAnti-collisionProtocol for selecting individual tags from multiple in RF fieldView full →: Type 4 (ISO 14443) handles a limited number of tags simultaneously. Type 5 (ISO 15693) slot-ALOHA anti-collision enumerates dozens to hundreds of tags in a field — enabling bulk inventory reading without individual positioning.

Technical Comparison

Use Cases

Type 4 Optimal Scenarios

• Product authenticationauthenticationIdentity verification of NFC tags/readers via passwords or cryptographyView full → with cryptographic proof: NTAG 424 DNA (Type 4) with SDM generates a per-tap AES-encrypted URL. Any NFC phone verifies the product's authenticity without an app. Type 5 has no equivalent authentication.
• Contactless payments: MIFARE DESFire (Type 4) is the smart card IC used in transit fare collection systems globally. ISO 15693 (Type 5) is not used in payment applications.
• Access control and government identity: DESFire EV3 multi-application cards for building access, transit, and eID. Type 5's read range makes it unsuitable for tap-based access gates.
• Transit gates at walking speed: Type 4 at 106 kbps (NFC-A) completes a transaction in < 200 ms. Type 5's 26 kbps and wider read range would trigger false reads as commuters pass near the gate.
• Pharmaceutical serialization requiring per-tap authentication: NTAG 424 DNA on unit packs provides secure anti-counterfeiting tap interaction — undeliverable by Type 5.

Type 5 Optimal Scenarios

• Library management: ICODE SLIX2 (Type 5) on book covers read at 30–50 cm in self-service return machines and staff sorting equipment. Type 4's 10 cm range would require individual tag alignment — impractical for bulk book handling.
• Pharmaceutical item-level tracking in logistics gates: Reader portals above pharmaceutical conveyors read Type 5 tags on passing boxes at 1 m+ distance — enabling inventory tracking at line speed.
• Laundry and textile tracking: ICODE SLIX2 tags embedded in garments withstand repeated high-temperature laundering and can be read in loose bundles at 0.5–1 m — NFC Type 4's 10 cm range is operationally impractical for laundry sorting.
• Asset tracking in clean rooms and healthcare facilities: Equipment tagged with Type 5 tags is readable as it passes through doorway-mounted readers — no one-by-one tag scanning needed.
• Retail EAS (Electronic Article Surveillance): ICODE SLIX2 includes a built-in EAS bit that activates/deactivates the EAS alarm function — replacing traditional magnetic security labels while also providing RFID inventory tracking.

When to Choose Each

Choose Type 4 when:

• AES-128 per-tap authentication is required (NTAG 424 DNA, DESFire)
• The interaction must be a deliberate tap at ~10 cm (payments, access, authentication)
• Multi-application file system is needed (DESFire EV3)
• SDM SUN message server-side validation is part of the system
• Data rate of 106 kbps is needed for transaction speed
• Maximum smartphone compatibility (all NFC phones via NFC-A/B)

Choose Type 5 when:

• Read range beyond 10 cm is operationally required
• Bulk inventory reading of many tags simultaneously (library, pharmaceutical, textile)
• Dedicated HF RFID reader infrastructure is deployed (not relying on smartphone reading)
• EAS (Electronic Article Surveillance) integration is needed (ICODE SLIX2)
• Lower IC cost ($0.10–$0.30) at adequate security levels (password + privacy flag)

Conclusion

Type 4 and Type 5 are not competing tiers in the NFC Forum specification — they address orthogonal dimensions of the tag performance space. Type 4 owns the short-range, high- security, authentication-capable niche where AES encryptionAES encryption128-bit symmetric encryption for strong NFC chip securityView full →, payment infrastructure, and deliberate tap interactions are required. Type 5 owns the vicinity-range, high- throughput, infrastructure-scale niche where 1.5 m read range and simultaneous multi- tag reading solve real operational problems that Type 4's proximity constraint cannot. The NFC Forum's inclusion of both in the same certification framework ensures that any NFC-enabled device supporting both NFC-A (for Type 4) and NFC-V (for Type 5) provides a complete interoperabilityinteroperabilityCross-manufacturer device/tag compatibility guaranteeView full → solution across both use cases.