Disclosure: As an Amazon Associate, CardWise earns from qualifying purchases at no additional cost to you. This does not affect our recommendations.
NTAG215 vs NTAG216 — Which NFC Tag Should You Choose?
The NTAG215 and NTAG216 are the two most popular NFC tags from NXP Semiconductors, both NFC Forum Type 2 tags running at 13.56 MHz. They share the same protocol, same read/write speed, same password protection, and same form factor options. The only meaningful difference is memory size. But that single difference determines everything: whether you can make Amiibo, whether you can store a vCard with photo, and how much your project costs at scale. This guide gives you a definitive answer.
Already know the basics? Jump to the decision guide. Or use our NFC Tag Capacity Calculator to test your NDEF message size against both tags.
Specs Side by Side
| Specification | NTAG215 | NTAG216 |
|---|---|---|
| RFC Standard | ISO 14443A | ISO 14443A |
| NFC Forum Type | Type 2 | Type 2 |
| Operating Frequency | 13.56 MHz | 13.56 MHz |
| Communication Speed | 106 kbps | 106 kbps |
| Total Memory | 540 bytes | 924 bytes |
| Usable NDEF Memory | 504 bytes | 888 bytes |
| Memory Pages (4 bytes each) | 135 pages | 231 pages |
| User Data Pages | 126 pages (504 bytes) | 222 pages (888 bytes) |
| Capability Container | 4 bytes | 4 bytes |
| Lock Bytes | 20 bytes | 20 bytes |
| Configuration Pages | 4 pages | 4 pages |
| Password Protection | 42-bit password + PACK | 42-bit password + PACK |
| Write Endurance | 100,000 cycles | 100,000 cycles |
| Data Retention | 10 years | 10 years |
| Price per Tag (bulk, 1k+) | ~$0.20–0.35 | ~$0.35–0.50 |
| Price per Tag (retail) | ~$0.50–1.00 | ~$0.80–1.50 |
The specs that differ are only: total memory (540 vs 924 bytes), usable NDEF (504 vs 888 bytes), number of pages, and price. Everything else is identical. There is no speed, range, or reliability advantage to either chip.
Memory — The Only Real Difference
NTAG215 gives you 504 bytes of usable NDEF storage. NTAG216 gives you 888 bytes — that's 76% more. Here's what that means in practice:
NTAG215 (504 bytes):
NTAG216 (888 bytes):
Scale: 100% = 888 bytes (NTAG216 max)
What Fits in 504 Bytes vs 888 Bytes?
| NDEF Payload | Typical Size | NTAG215 (504 B) | NTAG216 (888 B) |
|---|---|---|---|
| Short URL (https://cupass.com/en/) | ~35 bytes | Yes (up to 14) | Yes (up to 25) |
| WiFi credential (WPA2) | ~60 bytes | Yes | Yes |
| vCard (contact info, no photo) | ~150–300 bytes | Yes | Yes |
| Amiibo data dump | ~540 bytes (215 fit) | Yes (exact fit) | Yes |
| vCard with photo (JPEG thumbnail) | ~500–800 bytes | Tight / may fail | Yes |
| X.509 certificate (DER) | ~600–900 bytes | No | Yes (small certs) |
| Multiple NDEF records (URI + Text + Smart Poster) | ~200–600 bytes | Depends on content | Yes |
| Custom app data / binary blob | Variable | Up to 504 B | Up to 888 B |
The Amiibo Factor
The NTAG215 is the standard chip used in Nintendo Amiibo figures. Every original Amiibo tag contains an NTAG215 with a 540-byte Amiibo data dump that includes character ID, game data, and a read-only UID. This makes NTAG215 tags extremely popular for Amiibo cloning and DIY Amiibo projects.
Can you use NTAG216 for Amiibo? Technically yes — the data fits. But the Amiibo system expects exactly 540 bytes on an NTAG215. Some tools and NFC readers may not correctly write Amiibo data to NTAG216 because they check the tag model. If your goal is making Amiibo, buy NTAG215. No exceptions.
| Amiibo Task | NTAG215 | NTAG216 |
|---|---|---|
| Clone existing Amiibo | Perfect (native fit) | May not work with all tools |
| DIY Amiibo (TagMo, Amiibox) | Recommended | Not recommended |
| Amiibo card collecting | Standard | Overkill + compatibility risk |
| TagMo compatibility | Confirmed | Inconsistent |
When NTAG215 Is the Right Choice
✔ Choose NTAG215 if…
- You're making Amiibo. This is the #1 reason. NTAG215 is the standard Amiibo chip.
- You need a vCard without a photo. A standard vCard 3.0 with name, phone, email, address, and URL fits comfortably in 200–300 bytes.
- You're deploying tags at scale. At 1,000+ tags, the $0.10–0.15 per-tag savings adds up. 1,000 NTAG215 tags vs 1,000 NTAG216 tags = $100–150 saved.
- You need a smart poster (URI + title + icon). Typically 150–400 bytes — fits NTAG215.
- You need a WiFi sharing tag (~60 bytes). Either chip works; NTAG215 is cheaper.
- You're doing a museum/retail deployment where each tag stores one URL. 504 bytes is plenty.
When NTAG216 Is the Right Choice
✔ Choose NTAG216 if…
- You need a vCard with a photo. A JPEG thumbnail (96×96 or 128×128) adds 400–600 bytes, pushing total payload beyond 504 bytes.
- You're storing an X.509 certificate. A minimal DER-encoded certificate is 600–900 bytes. Only NTAG216 can hold it.
- You need multiple NDEF records — e.g., a URI record + a Text record with description + a custom MIME record with app data. Combined payloads often exceed 504 bytes.
- You want future headroom. If your project might grow (add a photo later, add a second URL, store a config blob), the extra 384 bytes of NTAG216 prevents needing to re-tag everything.
- You're storing a Bluetooth pairing payload or a complex Handover Select message with multiple alternative carriers. These can be 400–800 bytes.
- You need to store a small image or icon. A simple 48×48 PNG icon is ~300 bytes; combined with other NDEF data, NTAG216 is required.
Quick Decision Guide
| Your Use Case | Recommended Tag | Why |
|---|---|---|
| Amiibo cloning / DIY | NTAG215 | Standard Amiibo chip, guaranteed compatibility |
| Business card (vCard, no photo) | NTAG215 | 300 bytes max, 504 is enough, cheaper |
| Business card with photo | NTAG216 | Photo pushes payload past 500 bytes |
| URL shortener / link tag | NTAG215 | 35 bytes for a URL, 504 is overkill but cheapest |
| WiFi credential sharing | NTAG215 | ~60 bytes, either works, 215 is cheaper |
| Smart poster (URL + title + icon) | NTAG215 | 150–400 bytes, fits comfortably |
| Smart poster with large image | NTAG216 | Image may push past 504 bytes |
| Digital certificate storage | NTAG216 | 600+ bytes needed |
| Bluetooth pairing / handover | NTAG216 | Multi-carrier handover can exceed 504 bytes |
| Custom binary app data (< 500 B) | NTAG215 | Cheaper if it fits |
| Custom binary app data (> 500 B) | NTAG216 | 504 bytes isn't enough |
| Large-scale deployment (1k+ tags, simple URL each) | NTAG215 | Save $100+ at scale |
| Future-proof / multi-purpose tag | NTAG216 | Extra headroom for growth |
Cost Analysis at Scale
The price difference is small per tag but significant at volume:
| Quantity | NTAG215 (est. $0.25/tag) | NTAG216 (est. $0.40/tag) | Difference |
|---|---|---|---|
| 100 tags | $25 | $40 | +$15 |
| 500 tags | $125 | $200 | +$75 |
| 1,000 tags | $250 | $400 | +$150 |
| 5,000 tags | $1,250 | $2,000 | +$750 |
| 10,000 tags | $2,500 | $4,000 | +$1,500 |
Rule of thumb: If your payload fits in 504 bytes and you're buying more than 500 tags, choose NTAG215. The savings at scale are real. If you only need 10–50 tags, the extra $0.15 per tag for NTAG216 is negligible — buy NTAG216 for the headroom.
Technical Details: Page Structure
Both chips use 4-byte pages. The memory layout differs only in the number of user data pages:
NTAG215 Memory Map (540 bytes = 135 pages):
Page 0-1: Serial Number (UID) [8 bytes, read-only]
Page 2: Internal / Lock bytes [4 bytes]
Page 3: Capability Container [4 bytes: E1 10 1E 00]
Page 4-134: User Data (131 pages) [524 bytes raw]
Page 135-138: Configuration [16 bytes: PWD, PACK, CFG]
NDEF usable = 504 bytes (after TLV + NDEF header overhead)
NTAG216 Memory Map (924 bytes = 231 pages):
Page 0-4: Header + CC
Page 4-230: User Data (227 pages) [908 bytes raw]
Page 231-234: Configuration
NDEF usable = 888 bytes (after TLV + NDEF header overhead)| Memory Region | NTAG215 | NTAG216 |
|---|---|---|
| UID + Header (pages 0–1) | 8 bytes | 8 bytes |
| Internal / Lock (page 2) | 4 bytes | 4 bytes |
| Capability Container (page 3) | 4 bytes (E1 10 1E 00) | 4 bytes (E1 10 3C 00) |
| User Data (pages 4+) | 524 bytes (131 pages) | 908 bytes (227 pages) |
| Configuration (last 4 pages) | 16 bytes | 16 bytes |
| NDEF Usable (after TLV overhead) | 504 bytes | 888 bytes |
The Capability Container (CC) byte 3 differs: NTAG215 =
E1 10 1E 00 (0x1E = 30 × 8 = 240... actually 0x1E = 30, but in NXP's encoding it indicates 504 bytes). NTAG216 = E1 10 3C 00 (0x3C = 60, indicating 888 bytes). The CC tells the reader how much NDEF space is available.Android and iOS Compatibility
Both NTAG215 and NTAG216 are fully supported by Android and iOS:
| Platform | NTAG215 | NTAG216 | Notes |
|---|---|---|---|
| Android (NFC) | Full support | Full support | NfcA + Ndef class, read/write/format |
| iOS 11+ (Core NFC) | Full support | Full support | Read NDEF, write via NFCNDEFReaderSession |
| TagMo (Amiibo) | Confirmed | Inconsistent | TagMo checks tag model; NTAG215 required |
| NTAG I2C Plus | N/A | N/A | Different chip family, not relevant here |
| MifareClassicTool | N/A | N/A | NTAG is not MIFARE Classic; different protocol |
Common Mistakes
Mistake 1: Buying NTAG216 for Amiibo. Many tutorials say "you need NTAG215 for Amiibo" but don't explain why. The reason is that Amiibo data structures and TagMo expect the NTAG215's 540-byte total capacity. NTAG216 tags have a different CC byte and page count, causing some tools to reject them. Save yourself the headache — use NTAG215.
Mistake 2: Forgetting NDEF overhead. The 504/888 byte figure is the usable NDEF space after the TLV (tag-length-value) wrapper and NDEF header. Your actual payload is slightly less. For a single URI record, overhead is ~5 bytes. For complex multi-record messages, overhead can be 20–30 bytes. Use our NDEF Writer Simulator to measure exact consumption.
Mistake 3: Confusing NTAG with NTAG I2C. The NTAG I2C Plus (NT3H2111/NT3H2211) is a different chip with an I2C interface for MCU connectivity. Standard NTAG215/216 tags are passive RF-only tags. They look similar but are not interchangeable.
Mistake 4: Writing data larger than the tag. If you try to write a 600-byte NDEF message to an NTAG215 (504 byte limit), some writers will silently truncate the data or write a corrupted tag. Always verify your payload size before writing. Reformatting a corrupted tag is possible but tedious.
Stocking up on tags? The NTAG215 sticker pack (50 tags for ~$7) is the cheapest way to experiment with both tag types — Check Price on Amazon. For contact sharing, the NTAG215 Business Cards 20-pack comes pre-formatted and looks professional — Check Price on Amazon.
Beyond NTAG: Other NFC Tag Options
Neither NTAG215 nor NTAG216 may be right for you if…
| If you need… | Consider | Why |
|---|---|---|
| Minimal cost, simple URL only | NTAG213 (144 B) | ~$0.10 cheaper per tag than NTAG215 |
| More than 888 bytes | NTAG216F or NTAG I2C | NTAG216 is the max in the standard NTAG line |
| Security / encryption | NTAG 424 DNA | AES-128 authenticated NFC, tamper detection |
| Transit / access control | MIFARE DESFire EV3 | AES-128, file system, application isolation |
| Larger storage (1K+) | MIFARE Classic 1K/4K | 1K or 4K bytes, but older protocol |
For a broader comparison including NTAG213, see our NTAG213 vs NTAG215 vs NTAG216 guide. For choosing the right NFC tag type for your project, see NFC Tag Selection Guide.
Summary
Choose NTAG215 if you need Amiibo, vCard without photo, smart posters, WiFi tags, or large-scale URL deployments where cost matters. 504 bytes handles 90% of NFC projects.
Choose NTAG216 if you need vCard with photo, X.509 certificates, Bluetooth handover, multi-record NDEF beyond 504 bytes, or just want future-proofing for a small deployment.
Choose NTAG216 if you need vCard with photo, X.509 certificates, Bluetooth handover, multi-record NDEF beyond 504 bytes, or just want future-proofing for a small deployment.
Both tags are excellent, reliable, and universally supported. The wrong choice isn't a disaster — but getting it right saves money, time, and frustration. Use our NFC Tag Capacity Calculator or NDEF Writer Simulator to verify your payload size before ordering.