NFC engineering

NTAG213, NTAG215 or NTAG216?

Choose memory for the encoded message, then validate the tag in its real application.

NXP ICUser memory
NTAG213144 bytes
NTAG215504 bytes
NTAG216888 bytes

The common platform

NXP specifies NTAG213, NTAG215 and NTAG216 as NFC Forum Type 2 tag ICs using ISO/IEC 14443 Type A at 13.56 MHz. They offer 144, 504 and 888 bytes of user memory respectively. These values describe user memory, not the maximum length of every possible NDEF payload.

Allow for encoding overhead

NDEF record headers and the tag’s data structure consume space. Check the encoded byte count, including any URL, text and additional records. Test the actual message with the intended encoder before settling on a memory size.

Plan how the content will change

For content that changes frequently, encode a stable URL you control and update its destination content. Decide whether the tag will remain writable or be locked after verification. Treat permanent locking as a separate production approval step.

Separate access protection from authenticity

A password option is not the same as a complete product authentication system. A useful authenticity workflow also needs a defined threat model, appropriate chip capability, server verification where applicable, and careful provisioning.

Check the complete construction

Memory capacity does not establish the tag’s read performance. Antenna dimensions, application surface and phone antenna position still matter. For metal packaging, ask about an appropriate construction and test it on the actual material.

Semiconductor reference

NXP NTAG213 / NTAG215 / NTAG216 data sheet

Specification requirements

Include your reader, chip preference and application conditions in the quotation brief. Roxtron can review the requested product configuration with you.

Prepare a quotation