NFC Chips Compared

<\/script>\n
'; }, get iframeSnippet() { const domain = '{ SITE_DOMAIN }'; const type = '{ embed_type }'; const slug = '{ embed_slug }'; return ''; }, get activeSnippet() { return this.method === 'script' ? this.scriptSnippet : this.iframeSnippet; }, copySnippet() { navigator.clipboard.writeText(this.activeSnippet).then(() => { this.copied = true; setTimeout(() => { this.copied = false; }, 2000); }); } }" @keydown.escape.window="open = false" @click.outside="open = false">

Embed This Widget

Theme


      
    

Widget powered by . Free, no account required.

Selection criteria for hardware

Comprehensive comparison of NFC chips helping you choose the right IC for your project. Covers NTAG, MIFARE, ICODE, and ST families with memory, security, pricing, and ecosystem details.

| 3 min read

NFC Chip Comparison Guide

Choosing the right nfc-chip determines your project's memory capacity, security posture, read range, and unit cost. The market is dominated by three families — NTAG, MIFARE Classic, and MIFARE DESFire — each with distinct architectural tradeoffs.

Chip Families Overview

NTAG (NXP Semiconductors) — The consumer workhorse. NTAG chips follow NFC Forum Type 2, use a simple flat eeprom layout, and are certified by the NFC Forum. Memory ranges from 144 bytes (NTAG213) to 888 bytes (NTAG216). Security is limited to a 32-bit password and lock-bits. NTAG DNA and NTAG 424 add aes-encryption and sdm (Secure Dynamic Messaging).

MIFARE Classic (NXP) — The legacy incumbent. Still the most-deployed NFC chip globally (billions shipped), but uses the proprietary crypto-1 cipher which has been publicly broken since 2008. Not NFC Forum certified. Avoid for new secure applications; use for legacy interoperability only.

MIFARE DESFire EV3 (NXP) — The security standard. ISO 14443-4 compliant (NFC Forum Type 4), AES-128/192/256 and des-3des, per-file access-control-bits, mutual-authentication, and originality-signature verification. The chip of choice for physical access control, transport, and government ID.

ICODE (NXP) / ST25 (STMicroelectronics)ISO 15693 (nfc-v) chips for supply chain and item tracking. Longer read range, lower data rates.

NTAG vs MIFARE vs DESFire Comparison

Feature NTAG213 NTAG216 MIFARE Classic 1K DESFire EV3 4K
NFC Forum type Type 2 Type 2 None Type 4
total-memory 180 B 924 B 1024 B 4096 B
user-memory 137 B 868 B ~752 B ~4000 B
Security 32-bit pwd 32-bit pwd Crypto-1 (broken) AES-128/256
data-retention 10 years 10 years 10 years 10 years
write-endurance 100K cycles 100K cycles 100K cycles 500K cycles
Anti-clone No No No Yes (sig)
Unit cost (volume) $0.05 $0.10 $0.08 $0.60
Typical use URLs, Wi-Fi Large payloads Legacy transit Access control

NTAG DNA and Secure Tags

NTAG 424 DNA introduces sun-message (Secure Unique NFC Message) — the tag generates an AES-CMAC over a counter and UID, appended to the URL on every tap. The backend validates the CMAC, making each tap cryptographically unique and defeating replay attacks. This replaces the anti-cloning gap in standard NTAG chips. See NFC Security: Authentication and Anti-Cloning for implementation details.

Selection Criteria

Requirement Recommended Chip
Lowest cost, simple URL NTAG213
Wi-Fi credentials or vCard NTAG215/216
Secure authentication DESFire EV3 or NTAG 424 DNA
Supply chain / long-range ICODE SLIX2 or ST25TV
Legacy system compatibility MIFARE Classic (read-only upgrade)
On-metal mounting on-metal-tag variants (boosted antenna)

Use the NFC Chip Selector to filter across 40+ chips by memory, security, and protocol. Estimate payload fit with the NFC Memory Calculator.

Frequently Asked Questions

NTAG (NFC Tag) chips are NXP's consumer-grade line optimized for simple NFC Forum tag use cases — URL launching, text records, social links — with a straightforward byte-array memory model and optional 32-bit password. MIFARE is NXP's broader smart card platform; MIFARE Classic uses a proprietary 48-bit Crypto-1 cipher, while MIFARE DESFire EV3 uses hardware AES-128 with ISO 7816 APDU commands, suited for transit, access control, and payment applications requiring strong authentication.

NTAG 213/215/216 store a static NDEF URL that is always the same when read. NTAG 424 DNA (Secure Dynamic Messaging) generates a cryptographically unique, AES-128-signed URL on every tap — the counter and CMAC change with each read. This makes NTAG 424 DNA ideal for product authentication and anti-counterfeiting where the backend can verify the tag's cryptographic signature, while NTAG 21x chips are simpler and far cheaper for non-security use cases.

MIFARE DESFire EV3 adds Transaction MAC (TMAC), proximity check (defense against relay attacks), and Secure Dynamic Messaging compared to EV2. EV3 also supports ISO 14443-4 transaction timers and improved power management. Both use hardware AES-128 encryption, but EV3's proximity check is critical for contactless payment and high-security access control where relay attack resistance is required by EMVCo or ICAO standards.

For product authentication at scale, NTAG 424 DNA is the industry standard: it costs slightly more than NTAG213 but provides AES-128 Secure Dynamic Messaging without any backend reader infrastructure. For high-value goods requiring mutual authentication and revocation, MIFARE DESFire EV3 with application-level AES keys offers the strongest security. Avoid MIFARE Classic for new designs — its Crypto-1 cipher has been publicly broken since 2008.

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.