Why Your Phone Says "Tag Not Supported" — The Five Most Common Causes

"Tag Not Supported" on an iPhone, or "No supported app for this NFC tag" on Android, almost never means the tag is broken. The chip is usually fine — your phone just can't make sense of what's on it, or can't talk to it at all. Five things cause this most of the time: the wrong frequency, no NDEF data, a locked tag, a payload too big for the chip, or simple interference. Here's how to tell which one you're looking at, and the fix for each.

1. It's not actually an NFC tag

NFC runs at 13.56 MHz. A lot of cards and fobs that look identical run at 125 kHz instead — old building-access fobs, some pet ID tags, certain hotel cards. They're low-frequency RFID, a different technology, and no phone can power or read them. There's no fix here beyond using a real 13.56 MHz tag.

The same message shows up for chip types your phone's NFC controller doesn't handle. MIFARE Classic is the classic example: some Android phones read it, many don't, and iPhones treat most of it as off-limits. The tag is real, but your specific hardware has nothing to open it with.

2. There's no NDEF data on it

Phones expect a tidy NDEF message — a URL, a contact card, a Wi-Fi record. A tag that ships blank, or one that was written in a raw format the OS doesn't recognize, gives the phone nothing it can act on, so it shrugs and shows the error.

Android will often format a blank tag the moment you write an NDEF message to it. iOS is stricter: a standard NDEF reader session may not even see an unformatted tag. The fix is to write a proper NDEF record to the tag once, after which any phone can read it.

3. The tag is locked or read-only

NFC Forum Type 2 tags like the NTAG family have lock bytes and a one-time-programmable (OTP) area. Once those are set, the tag is permanently read-only — by design, and there's no undo. If you locked it on purpose, that's working as intended; see our guide to locking a tag permanently. If a previous write got interrupted, the tag can end up in a half-locked state that reads as unsupported.

Encrypted and proprietary tags fall here too. Transit passes, hotel keys, and corporate badges are locked to their own systems, so your phone genuinely has no app that can open them — and shouldn't.

4. The payload is too big for the chip

Every tag has a fixed amount of user memory. For the common stickers that's 144, 504, or 888 bytes on the NTAG213, NTAG215, and NTAG216 respectively, per the NXP datasheet. Try to write a long URL, a vCard with a photo, or a multi-record message that exceeds that, and the write fails — sometimes leaving the tag in a state the reader then calls unsupported. Trim the payload or move up to a larger chip.

5. Interference or a sloppy tap

If the error fires every time you unlock your phone, the culprit is usually a contactless card sitting in a wallet case behind it. The phone keeps detecting the card, can't open it, and complains. Pull the cards out, or stop stacking them against the phone.

Metal does the same thing from the other side: stick a normal tag flat on a laptop or fridge and the metal detunes its antenna so the phone can't get a clean read. Use an on-metal tag with a ferrite layer for those surfaces. And give the tap a moment — hold the tag steady over the phone's NFC antenna (top edge on most iPhones) for a full second instead of swiping past.

Diagnose it in about 30 seconds

Start by tapping a tag you know works. If that reads fine, the problem is the original tag, not your phone. Next, move away from other cards and off any metal surface and try again. Finally, read the tag's raw bytes: if you can pull a UID or a memory dump, the chip is alive and the issue is the data or the format — not the silicon.

Doing this on NFCore specifically

This is where a raw reader earns its keep. NFCore's memory dump shows whether the chip answers at all, even when there's no NDEF for the OS to display — so you can instantly separate a dead tag from an empty one. The tag inspector reports the chip type, total memory, and lock state, which maps straight onto the five causes above: see 125 kHz silence, an empty NDEF area, a tripped lock byte, or a full memory bank and you know exactly which fix you need.

NFCore is free, has no ads, and never uploads your tags anywhere. Grab it on the App Store or Google Play and run a quick memory dump the next time a tag comes back "not supported."