NTAG213 vs NTAG215 vs NTAG216: What’s the Difference?

If you are choosing an NFC tag, NTAG213, NTAG215, and NTAG216 can look almost interchangeable. They use the same 13.56 MHz NFC interface and belong to NXP’s NTAG21x family, yet their storage capacities are quite different. For a short URL, that difference may not matter at all. Once you need to keep a larger NDEF record on the tag, it does.

NTAG213 vs NTAG215 vs NTAG216: Quick Comparison

The three chips share the same core NFC technology. The main specification that separates them is memory capacity, increasing from 144 bytes of user read/write memory on NTAG213 to 888 bytes on NTAG216.

What Do NTAG213, NTAG215, and NTAG216 Have in Common?

Despite the difference in memory, NTAG213, NTAG215, and NTAG216 use the same NFC air interface. All three are NFC Forum Type 2 Tag ICs based on ISO/IEC 14443 Type A, operate at 13.56 MHz, and communicate at 106 kbit/s. Each chip also has a 7-byte unique identifier (UID).

Their shared functions go beyond basic reading and writing. Fast Read allows a reader to retrieve several memory pages with one command, while the NFC counter can track tag interactions. UID and counter mirroring can insert changing chip data into an NDEF record without rewriting the whole message.

All three chips also support 32-bit password protection with a 16-bit password acknowledgment (PACK). This can restrict access to selected memory areas, but it is intended as basic access protection rather than strong cryptographic authentication.

NXP also provides an originality signature on each chip. This can be used to verify that the IC itself is a genuine NXP product, but it does not authenticate the physical product or item carrying the tag.

What Is NTAG213?

NTAG213 is an NFC tag IC developed by NXP Semiconductors and the smallest-memory option among NTAG213, NTAG215, and NTAG216. It is a passive chip, so it does not need its own battery. Instead, a nearby NFC phone or reader provides the RF field needed to power the chip and communicate with it.

The IC can be built into finished NFC products such as stickers, cards, and labels. It provides 144 bytes of user read/write memory, which can hold NDEF content such as a website address or another compact record.

NTAG213 is commonly found in NFC tags that connect a physical item to online content, including product information, digital profiles, and smart advertising. Its role within the NTAG21x family is straightforward: it provides the same core NFC functions as the larger models with the smallest user-memory area of the three.

What Is NTAG215?

NTAG215 is the middle-capacity option in the same NTAG21x family. It provides 504 bytes of user read/write memory, giving applications substantially more room for information stored directly on the tag while retaining the same basic NFC interface as NTAG213.

The additional space can accommodate larger NDEF messages or more complex record structures. This is useful when the tag needs to carry more than a compact URI and the information cannot be reduced to a simple link.

NTAG215 is also closely associated with Nintendo Amiibo applications. In this case, the specific NTAG215 memory capacity and organization matter, so the requirement is not simply about choosing any NFC chip with enough storage.

What Is NTAG216?

NTAG216 is the largest-memory option among the three chips. It provides 888 bytes of user read/write memory while using the same NTAG21x NFC interface and core functions.

That larger memory area gives NTAG216 more room for NDEF data stored directly on the tag. It can accommodate longer records, multi-record messages, or other applications where the available on-chip space becomes an important part of the design.

User Memory vs NDEF Capacity: What Can You Actually Store?

The familiar 144, 504, and 888-byte figures do not represent the entire memory inside an NTAG21x chip. NTAG213 contains 180 bytes of EEPROM, NTAG215 contains 540 bytes, and NTAG216 contains 924 bytes. Some of this memory is reserved for manufacturer data, locking functions, configuration, and NFC Forum control information.

Why Is NDEF Capacity Different from User Memory?

The full user read/write area is not presented as one unrestricted NDEF data block in the NFC Forum Type 2 Tag structure. A four-byte Capability Container (CC) describes how the tag is organized and indicates the memory available to an NFC Forum-compatible reader.

For NTAG213, the reported NDEF memory size is 144 bytes. NTAG215 and NTAG216 report 496 and 872 bytes respectively, slightly less than their 504 and 888-byte user read/write areas.

This distinction becomes important when checking whether a specific NDEF message fits. The user-memory specification describes the writable memory provided by the chip, while the NDEF figure is the more relevant limit for data stored through the standard NFC Forum Type 2 NDEF structure.

Your Content Does Not Use Memory Byte for Byte

An NDEF message contains more than the visible link or text. Each record includes structural information that identifies its format and payload, while the Type 2 Tag stores the message within a TLV structure so a reader can locate and interpret it correctly.

URLs can use memory efficiently because NDEF supports URI prefix compression. For example, a common prefix such as http://www. can be represented by a URI identifier byte rather than storing every character separately. In NXP’s http://www.nxp.com example, the complete NDEF message occupies 12 bytes, with additional Type 2 TLV bytes marking the message and its end.

Text records use the available memory differently. Their payload includes information such as the language code in addition to the visible text. If one NDEF message contains several records, each record also requires its own record structure.

This is why an NDEF capacity of 144, 496, or 872 bytes should not be read as a simple character limit. The amount of memory used depends on the type of record and how the final NDEF message is encoded.

Does More Memory Mean Better NFC Performance?

More memory does not make NTAG215 or NTAG216 inherently faster than NTAG213. All three communicate at 106 kbit/s, so an NTAG216 storing the same short NDEF message as an NTAG213 does not gain a speed advantage simply because it has more unused memory.

Message size can affect the overall interaction. A larger NDEF message contains more bytes to transfer, so reading or writing it may require more data exchange than a small record. That difference comes from the amount of encoded data rather than the chip model itself.

Memory capacity also does not determine basic smartphone compatibility or RF signal strength. Those are separate from the amount of storage available on the IC.

Which Chip Is Best for Different NFC Applications?

The most useful way to compare the three chips is by looking at what the tag actually needs to store. A short online link and a full contact record may serve a similar user-facing purpose, but they can require very different amounts of NDEF memory.

A digital business card shows why the content format matters. If the tag simply opens an online profile, the encoded data may be only a short URL. If names, phone numbers, email addresses, and other contact information are stored directly on the tag, the NDEF message becomes much larger even though the user sees a similar result.

Amiibo is different from these capacity-based decisions. It depends on NTAG215 specifically, so substituting NTAG213 or NTAG216 is not simply a matter of finding another chip with less or more available memory.

FAQs About NTAG213, NTAG215, and NTAG216

Get the Right NFC Tag for Your Project

Need NTAG213, NTAG215, or NTAG216 tags? We offer custom NFC tags in different sizes, materials, and formats to match your application. Contact us to discuss your requirements and get the right tag for your project.