NFC Type 2 vs Type 4

NFC Forum Type 2 vs Type 4: NDEF Simplicity vs Application Complexity

The NFC Forum defines five NFC tagNFC tagPassive unpowered device storing data, powered by reader's RF fieldView full → types based on the underlying communication protocol and memory architecture. Type 2 and Type 4 are the two most widely deployed in consumer and enterprise NFC applications. Type 2 covers the NTAG 213/215/216 and MIFARE Ultralight EV1 family — flat, simple, NDEF-first tags at the lowest price point. Type 4 covers NTAG 424 DNA and MIFARE DESFire — multi- file, APDU-capable tags with advanced security. Choosing between them requires understanding the full stack from memory architecture to security model to cost.

Overview

NFC ForumNFC ForumIndustry body developing NFC standards, specifications, and certifications since 2004View full → Type 2 is defined in the NFC Forum Type 2 Tag Technical Specification (T2T). It is based on ISO 14443 Type A, operating at 106 kbps. The memory structure is a flat 4-byte block array — a simple, uniform address space. Blocks 0–3 are reserved for the UID, internal data, and lock bitslock bitsControl bits making memory blocks permanently read-onlyView full →. The NDEF capability container is in block 3. User data starts at block 4. The entire memory is a single contiguous address space — no applications, no files, no key hierarchy. Type 2 supports a static lock byte mechanism for making tags read-only.

NFC Forum Type 4 is defined in the NFC Forum Type 4 Tag Technical Specification (T4T). It is also based on ISO 14443ISO 14443Standard for contactless smart cards at 13.56 MHz (Types A and B)View full → Type A or Type B, but uses ISO 7816-4 APDU command structure for file selection and read/write operations. A Type 4 tag contains a Capability Container (CC) file, an NDEF file, and optionally proprietary additional files. The APDU architecture enables multiple files, per-file access rights, and — in chips like NTAG 424 DNA — full AES-128 cryptographic session establishment before data access.

Key Differences

• Memory architecture: Type 2 is a flat block array — one contiguous address space. Type 4 uses ISO 7816-4 file system — Capability Container file + NDEF file + optional proprietary files, each selectable by File ID.
• NDEF capacity: Type 2 practical limits: NTAG 213 = 137 bytes, NTAG 215 = 492 bytes, NTAG 216 = 872 bytes of NDEF payload. Type 4: NTAG 424 DNA = 256 bytes of user NDEF. DESFire supports NDEF file up to memory limit (2–32 KB depending on variant).
• Security: Type 2 offers only a 32-bit password (4 bytes). Type 4 tags (NTAG 424 DNA) support AES-128 authenticationauthenticationIdentity verification of NFC tags/readers via passwords or cryptographyView full →/" class="text-cyan-600 dark:text-cyan-400 underline decoration-dotted decoration-cyan-300 dark:decoration-cyan-700 underline-offset-2 hover:decoration-solid transition-colors">mutual authenticationmutual authenticationTwo-way identity verification between reader and tagView full →, Secure Dynamic Messaging (SDM), and per-session encrypted communication. MIFARE DESFire (also Type 4 via APDU wrapper) adds ECC (EV3) and TransactionMAC.
• Data rate: Both operate at 106 kbps base rate on ISO 14443.
• Read speed (practical): A Type 2 tag with a short NDEF recordNDEF recordSingle data element with TNF, type, ID, and payloadView full → is readable in under 50 ms — fewer command exchanges. Type 4 requires more APDU round-trips (SELECT, READ BINARY commands) adding 50–200 ms depending on the chip and security level.
• Cost: Type 2 (NTAG 213): $0.03–$0.10 at volume. Type 4 (NTAG 424 DNA): $0.20–$0.50. MIFARE DESFire (Type 4 via APDU): $0.80–$3.00+.
• NFC Forum certificationNFC Forum certificationInteroperabilityInteroperabilityCross-manufacturer device/tag compatibility guaranteeView full → testing program for NFC products and devicesView full →: Both Type 2 and Type 4 carry NFC Forum compliance certification — meaning all NFC Forum-compliant devices read both.

Technical Comparison

Use Cases

Type 2 Optimal Scenarios

• Mass-market consumer labels: URL tags on product packaging, promotional QR-code replacement campaigns, and smart postersmart posterCompound NDEF record combining URI with title and action metadataView full → applications. NTAG 213 at $0.03–$0.10 is the cost-effective choice when no cryptographic authentication is needed.
• NFC business cards: vCard or URL in 144–872 bytes (NTAG 213 to 216) — readable by any NFC phone in under 50 ms.
• Nintendo amiibo: NTAG 215 with 504 bytes is the exact fit for amiibo data. A global deployment of hundreds of millions of NTAG 215-based toys.
• Marketing and smart packaging at scale: FMCG brands use Type 2 for consumer engagement campaigns where authentication is not required and cost per tag is critical.
• IoT sensor tags (basic): NTAG I2C (Type 2 variant) enables NFC read of sensor data from a tag with I2C interface — readable by any NFC phone without an app.

Type 4 Optimal Scenarios

• Anti-counterfeiting with per-tap AES authentication: NTAG 424 DNA (Type 4) with SDM generates a server-verifiable AES-encrypted URL on every tap. The same smartphone that reads a Type 2 URL also reads NTAG 424 DNA natively — but now the URL carries a cryptographic proof of the specific physical tag.
• Transit and access control: MIFARE DESFire (Type 4 via APDU) is the standard for global transit and building access. Multi-file architecture, high write endurancewrite enduranceMaximum write/erase cycles before memory degradation (typically 100K)View full →, and AES key hierarchy are required.
• Pharmaceutical serialization and track-and-trace: NTAG 424 DNA on unit packs provides per-tap authentication for anti-diversion and anti-counterfeiting — tracing individual pharmaceutical units across a supply chain.
• Luxury goods authentication: High-value brands (watches, spirits, fashion) use NTAG 424 DNA to authenticate per-item provenance with a consumer smartphone tap — no app required.
• Government identity and secure access credentials: DESFire EV3 with APDU multi-application support hosts eID + access + payment on a single card.

When to Choose Each

Choose Type 2 when:

• NDEF delivery (URL, vCard, app launch) is the sole function
• Maximum NDEF capacity (up to 872 bytes) outweighs security requirements
• Cost per tag must be minimized (volume > 100,000 units)
• Sub-50 ms read latency is prioritized
• No cryptographic authentication is needed

Choose Type 4 when:

• AES-128 per-tap authentication is required (NTAG 424 DNA)
• Multi-file capability or ISO 7816-4 APDU integration is needed (DESFire)
• Transit, access, or government identity deployment
• SDM SUN message server-side URL validation
• Tamper detection (NTAG 424 DNA TagTamper variant)

Conclusion

Type 2 and Type 4 represent the two tiers of NFC Forum tag architecture: simple and cheap versus secure and capable. Type 2's flat memory model, lowest cost, and fastest reads make it the default choice for consumer NDEF delivery at scale. Type 4's APDU file system and AES security unlock per-tap cryptographic authentication, transit-grade write endurance, and multi-application cards. The sweet spot in 2024–2025 is NTAG 424 DNA — a Type 4 tag that combines AES-128 SDM authentication with native smartphone readability at $0.20–$0.50, closing the gap between Type 2 simplicity and Type 4 security for consumer applications.