MIFARE vs NTAG
MIFARE and NTAG are both NXP 13.56 MHz families but target different markets. MIFARE (Classic, Ultralight, DESFire) focuses on card-based applications with proprietary commands and multi-application support. NTAG (213/215/216/424 DNA) is purpose-built for NFC Forum tags with NDEF compatibility as the primary design goal.
MIFARE vs NTAG: Two NFC Tag Families, Different Design Philosophies
MIFARE and NTAG are both NFC chip families from NXP Semiconductors that operate at 13.56 MHz and comply with ISO 14443 Type A. Despite sharing the same manufacturer and base standard, they represent different design priorities: MIFARE is the established smart card and access control family with a proprietary memory structure optimized for multi-application cards; NTAG is the NFC Forum-compliant family built specifically for NDEF-first consumer and IoT deployments. The right choice between them depends on whether you are building an NFC ForumNFC ForumIndustry body developing NFC standards, specifications, and certifications since 2004View full →-interoperable product or a MIFARE-ecosystem access and payment system.
Overview
MIFARE is NXP's original 13.56 MHz product family, launched in 1994 with MIFARE Classic. The family spans several generations:
- MIFARE Classic: Proprietary CRYPTO1 stream cipher (deprecated for security), 1 KB or 4 KB EEPROMEEPROMNon-volatile memory technology retaining data without powerView full →, 16 sectors of 4 blocks each.
- MIFARE Ultralight / Ultralight EV1: Simplified, low-cost MIFARE for limited-use transit tickets and disposable applications. Compliant with NFC Forum Type 2.
- MIFARE DESFire EV1/EV2/EV3: Multi-application smart card with AES-128 encryption, ISO 7816-4 APDU compatibility, and advanced access control. The gold standard for transit, access control, and government ID.
- MIFARE Plus: Drop-in MIFARE Classic replacement with AES-128 migration path.
NTAG is NXP's NFC Forum-optimized tag family, introduced in 2012:
- NTAG 213/215/216: Type 2 tags with 144/504/888 bytes user memoryuser memoryTag memory portion available for user data storageView full →, 32-bit password protection, and full NDEF record compatibility.
- NTAG 424 DNA: Type 4 tag with AES-128 encryption, Secure Dynamic Messaging (SDM), and cryptographic per-tap authenticationauthenticationIdentity verification of NFC tags/readers via passwords or cryptographyView full →.
- NTAG 424 DNA TagTamper: Adds physical tamper detection loop to NTAG 424 DNA.
- NTAG I2C: Combines NFC interface with I2C bus for embedded IoT applications.
Key Differences
- NFC Forum compliance: NTAG 213/215/216 are certified NFC Forum Type 2 tags; NTAG 424 DNA is a certified Type 4 tag. MIFARE Classic has no NFC Forum certificationNFC Forum certificationInteroperabilityInteroperabilityCross-manufacturer device/tag compatibility guaranteeView full → testing program for NFC products and devicesView full →. MIFARE DESFire operates as a Type 4 tag via ISO 7816-4 APDU wrapper.
- Memory structure: NTAG uses a flat, block-addressed NDEF memory model. MIFARE Classic uses a sector-key-protected structure with CRYPTO1. MIFARE DESFire uses a file system with per-application, per-file AES key hierarchy.
- Security architecture: NTAG 21x uses a 32-bit password. NTAG 424 DNA uses AES-128 with SUN authentication generating a per-tap cryptographic SUN message. MIFARE DESFire EV3 uses AES-128 + ECC with TransactionMAC — the strongest NXP tag security available.
- NDEF out-of-the-box: NTAG 21x ships pre-formatted with an NDEF capability container — any NFC-enabled device reads it immediately. MIFARE Classic requires proprietary reader software; MIFARE DESFire requires application selection via APDU before data access.
- Use case orientation: NTAG is designed for consumer product tags, smart packaging, URL launching, and IoT. MIFARE (especially DESFire) is designed for multi-application smart cards, transit fare collection, building access, and government identity documents.
Technical Comparison
| Parameter | NTAG 213/215/216 | NTAG 424 DNA | MIFARE Classic 1K | MIFARE DESFire EV3 |
|---|---|---|---|---|
| NFC Forum type | Type 2 | Type 4 | None (proprietary) | Type 4 (APDU) |
| ISO 14443 | Yes (Type A) | Yes (Type A) | Yes (Type A) | Yes (Type A) |
| User memory | 144/504/888 bytes | 256 bytes | ~752 bytes | Up to 256 KB (hardware) |
| Security | 32-bit password | AES-128 + SUN | CRYPTO1 (broken) | AES-128 + ECC |
| Write endurance | 100,000 cycles | 100,000 cycles | 100,000 cycles | 500,000 cycles |
| Data retention | 10 years | 10 years | 10 years | 25 years |
| NDEF ready | Yes (formatted) | Yes (formatted) | No (requires config) | Via APDU wrapper |
| Multi-application | No | Limited (3 files) | 16 sectors | Yes (up to 28 apps) |
| SDM / SUN | No | Yes (per-tap AES URL) | No | Via TransactionMAC |
| ISO 7816-4 APDU | No | No | No | Yes |
| Typical tag cost | $0.03 – $0.15 | $0.20 – $0.50 | $0.05 – $0.20 | $0.50 – $2.00 |
| Smartphone read | Immediate (native) | Immediate (native) | Requires NFC app | Requires app |
Use Cases
NTAG Optimal Scenarios
- Consumer product authentication: NTAG 424 DNA with SDM generates a server-verifiable AES-encrypted URL on every tap — accessible natively on any NFC-enabled device without an app.
- NFC business cards and smart labels: NTAG 21x ships NDEF-formatted; any NFC phone reads the URL or vCard immediately.
- Smart packaging and brand engagement: Wine, spirits, cosmetics, and electronics labels use NTAG 21x for URL-based consumer engagement at mass-market price points.
- IoT sensor nodes with NFC configuration: NTAG I2C enables dual NFC/I2C access — tap a phone to read sensor data without a gateway.
- Toy and game interaction (amiibo): Nintendo amiibo uses NTAG 215 — its 504-byte capacity accommodates the amiibo data structure exactly.
MIFARE Optimal Scenarios
- Transit fare collection: Most global metro and bus rapid transit systems run on MIFARE DESFire EV1/EV2/EV3 or MIFARE Plus. The multi-application architecture, high write endurancewrite enduranceMaximum write/erase cycles before memory degradation (typically 100K)View full →, and AES security match the scale and security requirements.
- Building access control: MIFARE DESFire EV3 with AES-128 + ECC provides the key management and access control hierarchy needed for enterprise building systems.
- Government identity and e-passport: MIFARE DESFire is used in national eID cards in numerous countries. The ISO 7816-4 APDU compatibility enables integration with smart card middleware.
- Multi-application smart cards: A single MIFARE DESFire card can host a transit application, a building access application, and a canteen payment application simultaneously — each with its own AES key.
- Healthcare and insurance cards: Long data retention (25 years), high write endurance, and multi-application support make DESFire the choice for premium identity documents.
When to Choose Each
Choose NTAG 21x when:
- NDEF interoperability with any NFC phone is required without an app
- Mass-market consumer labels, packaging, or business cards at the lowest cost
- Simple URL or vCard delivery is the primary function
- NFC Forum Type 2 certification is specified
Choose NTAG 424 DNA when:
- Cryptographic per-tap authentication is needed without an app
- Anti-counterfeiting for luxury goods, pharmaceuticals, or brand protection
- SDM SUN message server-side validation is part of the system
- A step up from NTAG 21x password protectionpassword protection32-bit access control for memory areas (plaintext transmission)View full → is justified
Choose MIFARE Ultralight EV1 when:
- Limited-use transit tickets or disposable loyalty tokens are needed
- NTAG-level memory is not required (128 bytes sufficient)
Choose MIFARE DESFire EV3 when:
- Multi-application smart card functionality is required
- AES-128 + ECC security with TransactionMAC is mandated
- Transit, access control, or government identity deployment
- ISO 7816-4 APDU compatibility is needed for smart card middleware
Conclusion
MIFARE and NTAG are not interchangeable — they are purpose-built for different deployment architectures. NTAG's flat NDEF model, NFC Forum certification, and consumer-friendly instant readability make it the correct choice for product tags, smart packaging, and IoT. MIFARE DESFire's multi-application file system, ISO 7816-4 compatibility, and proven transit/access deployment record make it the correct choice for infrastructure-scale smart card systems. For most new consumer NFC deployments, NTAG 424 DNA delivers the best balance of AES security and NDEF interoperability at sub-$0.50 price points.
Рекомендация
Choose MIFARE for card-based systems like transit and access control; NTAG for NFC tag applications prioritizing smartphone compatibility.