Test Your Black Friday NFC Tags Before You Use Them
A sale pack of NFC tags is only a bargain if the tags work. Check the chip type, memory size, a write and rewrite, and the lock state on every tag before you use it.
Why test a tag pack before you use it
Scan every tag from a sale pack on your desk first: read the chip type and memory size, write a short test record, rewrite it, and check the lock state. It takes about a minute per tag. Peeling a dud off a wall later takes longer.
Sale packs are cheap and often mixed. The label might say NTAG215 while the chip inside is smaller, or a few tags might arrive locked. If you are still deciding what to buy, our notes on bargain bins to skip cover the warning signs. Here is what to do once the pack is in your hand.
Identify the chip and tag type
Scan each tag with an app that shows tag details. NFCore shows what it finds after a scan. You want two things: the chip family and the tag type.
Most stickers and cards sold in packs are NXP NTAG213, NTAG215 or NTAG216. NXP describes all three as NFC Forum Type 2 tags that follow ISO/IEC 14443 Type A. On Android, the platform reports the NDEF type as a string such as org.nfcforum.ndef.type2, and it lists the tag's technologies, for example NfcA and Ndef.
If the app reports something unexpected, such as a MIFARE Classic chip, treat it as a different product. Android only supports MIFARE Classic on phones whose hardware includes it, and an iPhone can't read it at all. Better to find a tag that behaves differently on your two phones now than after it is taped to a shelf.
Check memory against your payload
The label should match the memory. According to NXP, NTAG213, NTAG215 and NTAG216 offer 144, 504 and 888 bytes of user memory. Total memory is higher (180, 540 and 924 bytes), which is why a store listing and your app may show different numbers.
Android also reports the maximum NDEF message size of a tag. That figure is the space for your message, and it is a little lower than the user memory because the message needs its own header bytes.
Note the size the app reports for the first few tags. If a pack sold as NTAG215 reports about 144 bytes, you have NTAG213 tags and a longer message will not fit. See whether a message will fit in 144 bytes before you plan around the smallest size.
Run a write, read-back and rewrite test
A tag that reads fine can still fail to write, so run the full loop:
- Write a short text record, such as the word "test".
- Scan the tag again and confirm the same text comes back.
- Overwrite it with a different record and read it back.
- Confirm the new content replaced the old one.
Hold the tag steady during each write. A tag pulled away mid-write is the usual cause of a "tag lost" message, and what each write error means is worth a read if you see one.
You won't wear a tag out. NXP lists a write endurance of 100,000 cycles for NTAG213, NTAG215 and NTAG216, so a handful of test writes costs nothing in practice.
Check lock and read-only state
Next, find out whether the tag can still be changed. Android can tell an app whether a tag is currently writable, and whether it can be made read-only. A tag that arrives already locked will refuse your test write, so you will spot it in the previous step as well.
Locking is the one step you can't take back. NXP describes the read-only lock on these chips as field programmable, and once the lock bits are set they stay set. So test first and lock last, and only on tags whose content is final. If you need to check whether a tag is really read-only, do it with a spare from the same pack.
Some NTAG chips also support a 32-bit password and a read counter. If your project needs either, confirm it on a sample tag, since a mixed pack may not have it on every chip.
Test it the way you will use it
Finally, test the tag in place. Tape it where it will live, then tap it with an iPhone and an Android phone, with the case on, at the distance you will actually use. NFC range is short (NFC Forum cites a typical range of up to 2 cm), so a tag that only works when pressed flat against the phone is not ready for a door frame.
Mark the tags that pass, for example with a dot on the back, and set aside any that fail. Then write the real content.
Conclusion
A cheap pack is a good buy once you know what is in it. Spend a minute per tag on chip type, memory, a write and rewrite, and the lock state, and you will find the duds while they are still easy to return. NFCore is free to try: get it on the App Store or Google Play.
Frequently Asked Questions
How many tags from a pack should I test?
Test every tag you plan to use for something that matters. For a large pack, test a handful at the start, then test each one again when you write it for real, since a read-back is quick.
Can testing a tag damage it?
Ordinary test writes will not. NXP lists a write endurance of 100,000 cycles for NTAG213, NTAG215 and NTAG216. The step that cannot be undone is locking, so leave that until the tag has passed everything else.
Why does the app show a smaller memory size than the listing?
Listings often quote total chip memory, while the app shows the space available for your NDEF message. For NTAG213 that is 180 bytes in total but 144 bytes of user memory, and the usable message space is a little less again.