Black Friday NFC Tags: How to Spot Bargain Bins to Skip
Buying Black Friday NFC tags? Check the chip name, memory and iPhone and Android support, then test one tag before you trust a cheap bulk pack.
Skip any Black Friday tag pack that does not name its chip, and test one tag from every pack you do buy. Bulk NFC tags are cheapest in sales, and that is also when vague listings and look-alike chips show up most.
Read the chip line first
A good listing names the chip: NTAG213, NTAG215 or NTAG216. "NFC compatible", "universal NFC" and "chip may vary" tell you nothing, so treat them as a skip. If the seller will not say what is inside, you cannot know what your phone will do with it.
A familiar name isn't a guarantee. Retail NTAG21x tags bought online have been reported to fail NXP's originality signature check, and NXP's community forum says it gives no support for those products. Treat the chip name on the box as a starting point, not proof.
Read the memory line carefully
NXP lists user memory of 144 bytes for NTAG213, 504 for NTAG215 and 888 for NTAG216. Usable NDEF space is a little lower: 144, 496 and 872 bytes.
Most jobs fit in the small tag. A link, a Wi-Fi record or a short text is well under 144 bytes. Pay extra for NTAG215 or NTAG216 only if your data needs it, or if a gadget requires that exact chip. If you plan to move one tag's content to another, check whether a copy will fit in 144 bytes first.
Check iPhone and Android support
Android reads NDEF on NFC Forum Types 1 to 4 and recommends them for tags that need to work across devices. MIFARE Classic support is optional on Android, and it depends on the phone.
iPhone is stricter. Core NFC reads NDEF tags, and writes them from iOS 13, but it does not support MIFARE Classic. A cheap bin of "NFC cards" that turn out to be MIFARE Classic can look fine on one phone and be invisible on another. See which NFC tags work with iPhone and why an iPhone can't see a MIFARE Classic card before you buy a stack.
Test every pack before you stick anything
Open the pack and test one tag first, on the phone you actually use:
- Read it. The phone should detect it at once and show the chip type.
- Check the memory. The size shown should match the listing.
- Write a short message, read it back, then overwrite it with something else.
- Run NXP's TagInfo app and look at the originality signature. A fail is a red flag. A pass is good news but not complete proof, because NXP suggests combining it with other checks.
NTAG21x chips are rated for 100,000 write cycles and 10 years of data retention, so a tag that fails after a handful of rewrites is not behaving like the real thing. Don't lock the tag during the test, since locking can't be undone. If a write fails, read-only vs tag lost errors have different causes, so work out which one you have before you blame the tag.
Keep the packaging and buy somewhere with a clear return window. If one tag in a pack fails, test a second before you return it, then return the whole pack if it fails again.
NFCore can read a tag, show what it is, and write and rewrite NDEF records, so it covers steps 1 to 3 on both iPhone and Android. Get it on the App Store or Google Play.
Other bin red flags
- No chip name, no memory size and no photo of the actual tag.
- A price far below the same chip from named sellers.
- No mention of antenna size, even though bigger coils usually read from farther away.
- Stickers sold for use on metal with no mention of a metal-safe backing.
- Mixed bins where each tag may be a different chip.
Bottom line
Buy by chip name, not by the word "NFC". Match the memory to the job, avoid MIFARE Classic for tags meant for phones, and test one tag from every pack before you commit. A pack that passes is a deal. One that skips the checks is a gamble, even at half price.
Frequently Asked Questions
Which chip is the safest bet in a Black Friday pack?
NTAG213, NTAG215 or NTAG216 from NXP, with the chip named in the listing. They hold 144, 504 and 888 bytes of user memory, and they work with both iPhone and Android.
Can a cheap tag be fake even if it reads fine?
Yes. Look-alike tags can read and write normally. A failed originality signature check in NXP's TagInfo app is a red flag, but a pass does not fully rule out cloning, so combine it with the other checks.
Is more memory always better?
No. Most tag jobs, like a link or a Wi-Fi record, fit in 144 bytes. Pay for more memory only if your data needs it.