NTAG213 vs NTAG215 vs NTAG216 — Which NFC Tag Should You Use?
All three are NFC Forum Type 2 tags from NXP, all running at 13.56 MHz with the same protocol. The only difference that matters: memory size. But that difference determines which projects each tag is suitable for. Here's the definitive comparison.
Specs at a Glance
| Spec | NTAG213 | NTAG215 | NTAG216 |
|---|---|---|---|
| Total Memory | 180 bytes | 540 bytes | 924 bytes |
| Usable NDEF | 144 bytes | 504 bytes | 888 bytes |
| Capability Container (CC) | 4 bytes | 4 bytes | 4 bytes |
| Lock Bytes | 20 bytes | 20 bytes | 20 bytes |
| Configuration Pages | 4 pages | 4 pages | 4 pages |
| Price per Tag (bulk) | ~$0.12-0.20 | ~$0.20-0.35 | ~$0.35-0.50 |
| URL Length (typical) | ~120 chars | ~480 chars | ~865 chars |
| Best For | Simple URLs, WiFi config | Amiibo, vCard, smart posters | Large payloads, photos, certificates |
NTAG213 — The Budget Workhorse
144 bytes of NDEF memory. That's enough for a WiFi credential (~30 bytes), a short URL (~50 bytes), or a text message (~120 bytes). If you're deploying NFC tags at scale — say, 1,000 tags for a museum audio guide or smart posters in a retail chain — the NTAG213's lower per-tag cost adds up to real savings. The tradeoff: you can't store a vCard or anything beyond a short URI.
Use when: You need many tags, and each tag stores one simple URL or short text string.
Don't use for: Amiibo, contact cards, or any data-heavy payload.
NTAG215 — The Sweet Spot
504 bytes. This is the most popular NTAG chip for good reason. It fits NTAG215 Amiibo data (~540 bytes of the total are needed for Amiibo dumps), a full vCard (~150-300 bytes), a long URL with metadata, or a smart poster with title + icon. The NTAG215 is the default recommendation for most developers.
Use when: You need a versatile tag that handles 90% of NFC projects.
Don't use for: Storing images or large certificates.
NTAG216 — Maximum Storage
888 bytes. When 504 bytes isn't enough. Use the NTAG216 for vCard with photo, long NDEF messages with multiple records, X.509 certificates, or multiple URLs in one tag. The price premium is small per tag, so if you're unsure, go with NTAG216.
Use when: Your NDEF message exceeds 450 bytes, or you want headroom for future growth.
NDEF Capacity Visualization
Use Our Tools to Decide
Not sure which tag your data needs? Use our NDEF Writer Simulator to compose your message and see exactly how much memory it consumes. Our NFC Tag Capacity Calculator compares all tag capacities side by side.
Related
Best NFC Tags for Developers — Where to buy | NDEF Writer Simulator | NFC Tag Capacity Calculator