NTAG213 vs NTAG215 vs NTAG216 for iPhone NFC tags
Choose among common NTAG21x tags by payload size and deployment needs, then verify the actual writable NDEF capacity before buying or writing in bulk.
NTAG213, NTAG215, and NTAG216 are NFC Forum Type 2 tag ICs from the same NXP family. The practical difference most buyers notice is memory: NXP lists 144, 504, and 888 bytes of user memory respectively.
Those figures help compare products, but they are not permission to fill every byte with an NDEF message. Formatting and tag configuration consume space, and a finished sticker or card can behave differently from a bare IC. Query the actual tag and test a sample before committing to a bulk order.
Quick choice
| Tag | NXP user memory | Practical starting point |
|---|---|---|
| NTAG213 | 144 bytes | Short HTTPS URLs, review links, and simple labels |
| NTAG215 | 504 bytes | Longer URLs, additional margin, and repeated business-card work |
| NTAG216 | 888 bytes | Long payloads where the extra capacity is genuinely required |
The table describes selection intent, not a guarantee that every retail tag has the advertised IC or that the full user-memory figure is available to your encoded message.
Measure the payload before buying
Build the exact payload first. URL length, non-ASCII characters, the NDEF record type, and encoding overhead all affect the final message size. Boreal NFC displays an estimate before writing so you can reject an obviously undersized option early.
If the tag only needs to open a public page, shorten the data model rather than buying capacity for a large embedded contact record. A durable URL can point to richer content and can be updated later without rewriting the physical tag.
Verify the tag presented to the phone
During an active Core NFC session, iOS can query an NDEF tag for its status and maximum NDEF message size. Treat that result as stronger evidence than packaging, marketplace copy, or the family name alone.
Before a bulk deployment:
- Buy a small sample from the intended supplier.
- Scan and record the reported status and capacity.
- Write the production payload.
- Read the result back on iPhone.
- Test the installed item, including material and placement.
- Keep a matching QR fallback for public links.
Sources and review
- NXP NTAG213/215/216 product data sheet
- Apple:
queryNDEFStatusreturns NDEF status and capacity - Boreal NFC 1.0.5 tag-selection guidance reviewed August 12, 2026.
Continue with the pre-write checklist.