Back to guides

NTAG215 Explained for Gamers: Size, Limits and Phone Support

NTAG215 is an NFC chip with 504 bytes of user memory. Here is what that means for game tags, and what an iPhone or Android phone can do with one.

Published

What NTAG215 actually is

NTAG215 is an NFC chip from NXP with 504 bytes of user memory, and it is the size most game tags are built around. If you hold a card, coin or sticker that a console or an app reads, there is a good chance this chip sits inside it.

On paper it's simple. NXP lists it as an NFC Forum Type 2 tag that follows ISO/IEC 14443 Type A. The total memory is 540 bytes, split into 135 pages of 4 bytes each, and 504 of those bytes are yours to read and write. Each chip also carries a 7-byte UID set at the factory, so no two real chips share one.

A few more numbers from NXP's datasheet are worth knowing:

  • Write endurance: 100,000 write cycles.
  • Data retention: 10 years.
  • Password protection: an optional 32-bit password, with an optional limit on wrong attempts.
  • Intended use: NXP names gaming next to retail and consumer electronics.

NTAG215 next to its siblings

NTAG213 gives you 144 bytes, NTAG215 gives you 504 and NTAG216 gives you 888. They share the same standard, so a phone treats them the same way. Only the room differs. We compare them in detail in NTAG213 vs NTAG215 vs NTAG216, so here's the short version for gamers: the middle size is the one game makers settled on. A tag that's too small or too big for a game's expected layout is a common reason a tool refuses it.

Why games picked this chip

Game figures and cards need a fixed amount of space they can count on. 504 bytes is enough for a small save record and little else, which suits a toy that only needs to remember a few things. Amiibo are widely reported to use this chip, and how amiibo use the NTAG215 chip walks through that.

What the console does with the tag is a separate matter. Per Nintendo's support page, a Switch reads amiibo at the NFC touchpoint: the right stick on a Joy-Con, the area over the Switch logo on a Pro Controller, and the right stick on a Switch Lite. Each figure holds data for one compatible game at a time.

One point to keep straight: a blank NTAG215 is not an amiibo. The chip type matches, but a real figure or card also holds data that a game expects to find. NFCore can read and check amiibo, and it does not make working ones.

If you ever copy a tag, do it only for tags you own, as a personal backup, and respect the game maker's terms.

What your phone can do with one

Here Android and iPhone part ways.

Android treats NDEF as the main format, but it also exposes the raw tag through its tech classes, such as NfcA and MifareUltralight. That raw access is what lets an app read the individual pages of an NTAG215, not just the message on it. One recent change to know: from Android 16, a tag holding a web link opens through a view intent, and Android 17 shows an open-link notification first.

iPhone is more limited. Background tag reading works with NDEF tags that carry a URL record, and it is read-only. That's fine for a tag that opens a page. It's not enough for a game tag that needs its raw pages read or written. For the full breakdown, see the iPhone vs Android chart for game tags.

One related warning: MIFARE Classic cards are a different chip family. Android reads and copies them only on phones with an NXP NFC chip, using the default keys or a key you enter. An iPhone can't read them at all.

Picking a physical tag

The chip is the same whether it is a card, a coin or a sticker, so choose the shape for where it will live. Cards slide into a wallet, stickers stick to a case, and coins fit a display shelf. If the tag will get splashed, read about waterproof tags first. If you want a non-console example of the same tag idea, see how Yoto and Toniebox cards work.

Conclusion

NTAG215 is a Type 2 chip with 504 bytes of user memory, a 7-byte UID and a long write life, and phones handle it very differently: Android can reach the raw pages, while iPhone mostly sticks to NDEF links. To check a tag you already own, you can scan it with NFCore on the App Store or Google Play.

Frequently Asked Questions

How much memory does an NTAG215 have?

504 bytes of user memory, according to NXP. The chip holds 540 bytes in total, arranged as 135 pages of 4 bytes.

Can an iPhone use an NTAG215 game tag?

An iPhone reads NDEF tags with a URL record in the background, but it can't read or write the raw page data a game tag depends on. Android with the right app can.

Is a blank NTAG215 the same as an amiibo?

No. The chip family is the same, but a figure or card also carries data a game expects. NFCore reads and checks amiibo, and it does not make working ones.