HF / NFC 
MIFARE Ultralight EV1
For single-use tickets, stickers and simple NFC applications.
Security PWD 32-bit
Memory 48 / 128 B
NTAG® 213 / 215 / 216: Technical Data, Security and Use
NTAG 213, NTAG 215 and NTAG 216 from NXP Semiconductors are passive HF/NFC tag ICs for 13.56 MHz. They operate according to ISO/IEC 14443 Type A and comply with the NFC Forum Type 2 Tag. The three variants offer 144, 504 and 888 bytes of freely usable user memory respectively. Typical applications are NDEF content for smartphone interactions, NFC marketing, digital business cards, product information and pairing.
NXP still lists the NTAG 21x series as Active. We recommend the series for NFC marketing, business cards and smartphone applications. It is particularly suitable for standardized NFC/NDEF applications that do not require strong cryptographic authentication on the chip.
| Feature | Value |
|---|---|
| Manufacturer | NXP Semiconductors |
| Product family | NTAG 21x |
| Type designation | NTAG 213 / NTAG 215 / NTAG 216 |
| RFID class | HF / NFC |
| Frequency | 13.56 MHz |
| Standard | ISO/IEC 14443 Type A |
| NFC standard | NFC Forum Type 2 Tag |
| Data rate | 106 kbit/s |
| Total EEPROM | 180 B / 540 B / 924 B |
| User Memory | 144 B / 504 B / 888 B |
| NDEF memory according to capability container | 144 B / 496 B / 872 B |
| Memory structure | 45 / 135 / 231 pages of 4 bytes each |
| Authentication | 32-bit password check via PWD_AUTH with 16-bit PACK; deactivated on delivery |
| Encryption | No integrated data encryption; password protection for memory access |
| UID | 7 bytes, programmed by the manufacturer |
| Anti-collision | Yes |
| Read range | Up to 100 mm according to NXP, depending on field strength, antenna geometry and application |
| Write cycles | At least 100,000 |
| Data retention | At least 10 years |
| NFC Counter | 24-bit one-way counter, configurable and optionally password-protected |
| UID/counter mirror | Yes, ASCII mirroring of UID and/or NFC counter into the memory area being read |
| Originality Signature | 32-byte ECC signature, ECDSA secp128r1, for verifying the NXP IC origin |
| Read-only lock | Programmable, irreversible lock bits |
| Fast Read | Yes |
| Smartphone NFC | Yes, especially for NDEF on NFC-enabled Android and iOS devices |
| Product status at NXP | Active |
| Typical media | NFC label, sticker, card, ticket, key fob and wristband |
| Security rating | Low – 32-bit password protection |
| Recommendation | Recommended for simple NFC/NDEF and smartphone applications without high cryptographic security requirements |
Technically, NTAG 213, 215 and 216 differ mainly in memory. The total EEPROM is 180, 540 and 924 bytes respectively. Of this, 144, 504 and 888 bytes respectively are available as user memory. The NDEF memory size specified in the capability container is 144, 496 and 872 bytes respectively. All three variants operate at 106 kbit/s, have a 7-byte UID and support Fast Read, a 24-bit NFC counter and an ECC-based originality signature, among other things.
Typical Applications
NXP positions NTAG 213, 215 and 216 for NFC applications in which information or actions are retrieved via an NFC-enabled device. These include in particular:
- NFC marketing and smart advertising
- digital business cards
- product information and mobile companion tags
- vouchers and coupons
- Bluetooth or Wi-Fi pairing and connection handover
- electronic price tags and comparable NFC shelf label applications
Suitable media formats include in particular NFC tags and stickers, RFID/NFC cards, tickets and, depending on the design, key fobs and wristbands as well.
Security
Security level: Low
NTAG 213, 215 and 216 offer 32-bit password protection for defined memory areas. This protects against simple unauthorized access, but is no substitute for cryptographic authentication or encryption.
In addition, an ECC originality signature makes it possible to check whether the IC originates from NXP. For public NFC content, this is usually sufficient. For access control or secure ID cards, more strongly protected chips such as MIFARE® DESFire® EV3 are better suited.
Advantages and Disadvantages of NTAG 213 / 215 / 216
| Advantages | Disadvantages |
|---|---|
| NFC Forum Type 2 and ISO/IEC 14443 Type A for standardized NDEF applications | Only 32-bit password protection instead of strong cryptographic authentication |
| Three memory sizes with 144, 504 or 888 bytes of user memory | No integrated data encryption for the application memory |
| Broad NDEF support on NFC-enabled Android and iOS devices | NDEF memory on NTAG 215 and 216 smaller than the total user memory |
| ECC originality signature for verifying the NXP IC origin | Originality signature does not automatically authenticate the stored content or the tagged product |
| NFC counter, UID/counter mirror and Fast Read for advanced NFC applications | Permanently set lock bits cannot be reset |
Alternatives to NTAG 213 / 215 / 216
Depending on memory requirements, security needs and application, other NFC chip types may be better suited.
HF / NFC Legacy 
MIFARE Ultralight C
For ticketing and loyalty applications with 3DES authentication.
Security 3DES
Memory 192 B
HF / NFC Recommendation 
MIFARE DESFire EV3
For applications with cryptographic authentication and higher security requirements.
Security AES-128
Memory 2 / 4 / 8 / 16 KB
Frequently Asked Questions about NTAG 213 / 215 / 216
How much memory do NTAG 213, NTAG 215 and NTAG 216 have?
NTAG 213 has a total of 180 bytes of EEPROM, NTAG 215 540 bytes and NTAG 216 924 bytes. Of this, 144, 504 and 888 bytes respectively are available as freely programmable user memory. For NDEF, the capability container specifies 144 bytes for NTAG 213, 496 bytes for NTAG 215 and 872 bytes for NTAG 216. These values should not be confused with one another: total EEPROM, user memory and NDEF memory refer to different memory sizes.
What is the difference between NTAG 213, NTAG 215 and NTAG 216?
The most important difference is the memory size. NTAG 213 offers 144 bytes of user memory and is therefore often sufficient for short NDEF content such as a URL or a digital business card. NTAG 215 increases the user memory to 504 bytes, NTAG 216 to 888 bytes. The basic RF interface, 106 kbit/s data rate, 7-byte UID, password protection, NFC counter, UID mirroring and originality signature are available in all three variants.
Can NTAG 213, 215 and 216 be read and written with smartphones?
Yes. The chips comply with the NFC Forum Type 2 Tag and support NDEF. Android requires support for NFC Forum Tag Types 1 to 4 for NFC devices and recommends these formats for new NDEF applications. Apple's Core NFC supports NDEF tags of types 1 to 5 and can also program writable tags. Whether specific content can be opened or written automatically also depends on the smartphone, operating system, NDEF content and the configuration of the tag.
Which readers support NTAG 213, 215 and 216?
For normal reading and NDEF applications, a reader or NFC device for 13.56 MHz and ISO/IEC 14443 Type A or NFC Forum Type 2 is required. If special NTAG functions such as PWD_AUTH, READ_CNT, READ_SIG or FAST_READ are used, the reader software used must also support these commands or enable corresponding low-level communication. The mere specification “13.56 MHz” is therefore not sufficient for selecting a reader.
How secure are NTAG 213, 215 and 216?
The chips have 32-bit password protection, but no strong cryptographic authentication for normal memory access. NXP describes the password mechanism as simple protection against unauthorized memory access and recommends cryptographic methods at application level for higher security requirements. The ECC originality signature serves separately to verify that the IC originates from NXP. For security-critical credentials or access control applications, the NTAG 21x series is therefore not the first choice.
Can the memory be permanently locked against changes?
Yes. NTAG 213, 215 and 216 have programmable lock bits. For the first 16 pages, write protection can be set page by page. Above this area, locking is done in groups of two pages for NTAG 213 and 16 pages for NTAG 215 and NTAG 216. Certain bits in the capability container and the lock bits cannot be reset once set. A permanent lock should therefore only be applied after personalization has been completed.
What can the NFC counter and UID mirror be used for?
The NTAG 21x series has a configurable 24-bit NFC counter. It can be incremented on the first valid READ or FAST_READ command after the tag is powered up. UID and counter can also be mirrored as ASCII characters into a memory area being read. This allows an NDEF URL, for example, to automatically contain a UID or counter value when read, without this value having to be stored statically in the user data beforehand.
What is the read range of NTAG 213, 215 and 216?
NXP specifies an operating distance of up to 100 mm. This value explicitly depends on factors such as field strength and antenna geometry. The actual read distance is therefore determined not only by the IC, but also by the inlay, the reader antenna, the end device, the installation situation and the materials in the immediate vicinity.
Are NTAG 213, NTAG 215 and NTAG 216 still being produced?
Yes. NXP currently lists the product family with the status Active. The current NXP product page also still contains orderable variants and the associated technical documentation. For new simple NFC/NDEF applications, the family therefore remains available and is one of our recommendations.
Technical sources
Data as of: September 2026
The technical information is based on the NXP data sheet “NTAG213/215/216 – NFC Forum Type 2 Tag compliant IC with 144/504/888 bytes user memory”, Rev. 3.2 dated 2 June 2015, and the current NXP product page for the NTAG 21x series. In addition, the NXP Application Notes AN13089 “NTAG 21x features and hints”, Rev. 1.0 dated 5 May 2021, and AN12653 “End to end system security risk considerations for implementing contactless cards and tags”, Rev. 1.1 dated 5 May 2021, were taken into account. Statements on smartphone use are based on the current Android NDEF documentation and Apple's Core NFC documentation.
Trademark notice
NTAG is a trademark of NXP B.V.
The spelling on this page follows NXP's trademark notices in the official NTAG product documentation and the NXP Terms of Use.