NFC Tag Not Detected: Diagnosis Guide

NFC Tag Not Detected: Step-by-Step Diagnosis

A tag that fails to read can stem from six completely different root causes — RF physics, chip damage, NDEF formatting, OS-level permissions, reader firmware, or environmental interference. This guide walks through each layer systematically so you fix the actual cause rather than guess.

Layer 1: Physical and RF Check

Start at the antenna. Coupling between the reader coil and the tag antenna depends on alignment, distance, and conductor proximity.

Symptom	Likely Cause	Test
Reads at one orientation, not another	Antenna axis mismatch	Rotate tag 45° increments
Reads close, not at expected read-range	Detuned tag antenna or metal proximity	Test on non-metal surface
Intermittent reads (≥50% success)	Marginal coupling, thin adhesive gap	Use a spacer or on-metal-tag
Never reads on any reader	Chip damaged, antenna broken, OTP permanently locked	Test with a known-good blank

The operating-frequency is 13.56 MHz. Metal within 3 mm of a standard inlay detunes the resonant circuit drastically. If your tag is near metal, switch to a ferrite-backed on-metal-tag designed for that environment.

Layer 2: Verify the Chip is Alive

Use a dedicated NFC readerNFC readerActive device generating RF field to initiate communication with tagsView full → app (NFC TagInfo by NXP on Android) or a development reader such as the PN532. A chip that returns a valid uid during anti-collisionanti-collisionProtocol for selecting individual tags from multiple in RF fieldView full → is electrically functional even if the NDEF data is corrupt.

PN532 scan output — healthy tag:
  Found 1 ISO14443A card:  UID: 04 A3 B7 21 C4 56 80
  ATQA: 0x4400  SAK: 0x00  (NTAG215)

PN532 scan output — no tag / dead chip:
  No card detected within timeout

If no UID appears, the chip is either dead, delaminated from the antenna, or facing a anti-collision collision from a nearby second tag.

Layer 3: NDEF Formatting Issues

A physically healthy chip may still fail to trigger OS-level tag dispatch if its capability-container is corrupt or the NDEF tlv is malformed.

Common NDEF faults:

Fault	Symptom on Android/iOS	Fix
Capability Container not written	Tag detected, no Intent fired	Format tag with NFC Tools app
TLV length field mismatch	App opens but data garbled	Re-encode with NDEF Encoder
Terminator TLV `0xFE` missing	Partial read, some readers fail	Re-write full NDEF payload
ndef message exceeds total-memory	Write succeeds, read fails	Use Memory Calculator
OTP area written incorrectly	Tag permanently unresponsive	Tag is bricked; discard

Paste the raw hex dump from NFC TagInfo into the NDEF Decoder to identify exactly where the parse fails.

Layer 4: OS and App Permissions

Even a perfectly encoded tag is invisible if the OS NFC stack is off or an app lacks permissions.

Android checklist: - Settings → Connected devices → NFC → enabled - Settings → Connected devices → NFC → Contactless payments → does your app intercept the intent? - android.permission.NFC declared in manifest and granted - android:launchMode — singleTop required to receive onNewIntent() re-reads

iOS checklist: - Background tag reading requires iOS 14+ and entitlement com.apple.developer.nfc.readersession.formats - Core NFC session must be active (user action required to start) - NTAG 424 DNA SDM with SUN message requires iOS 14 or later - Tag type must be NDEF-formatted — ISO 7816 raw APDU sessions require separate NFCTagReaderSession

Layer 5: Reader Firmware and Configuration

Reader-side issues are commonly misdiagnosed as tag faults.

RF field not enabled: Some PN532 configurations keep the field off between transactions to save power; add a SetParameters command to keep the field active.
Protocol mismatch: A Type 5 tag (iso-15693) will not respond to an iso-14443 poll. Ensure your reader polls all target types: Type 1/2/3/4 (ISO 14443ISO 14443Standard for contactless smart cards at 13.56 MHz (Types A and B)View full →) and Type 5 (ISO 15693ISO 15693Standard for vicinity-range smart cards, 1+ meter read rangeView full →).
Timeout too short: NTAG 424 DNA with AES authenticationauthenticationIdentity verification of NFC tags/readers via passwords or cryptographyView full → requires 3–4 round-trips; a 50 ms timeout will always fail.
Baud rate selection: NFC-F operates at 212 or 424 kbit/s; not all readers default to polling both speeds.

Layer 6: Environmental Interference

Interference Source	Effect	Mitigation
Nearby second NFC tagNFC tagPassive unpowered device storing data, powered by reader's RF fieldView full →	anti-collision arbitration may select wrong tag	Separate tags by ≥ 5 cm
Strong EM field (motor, inverter)	Corrupted RF waveform	Shield or relocate reader
Multiple readers active	Cross-field modulation	Time-multiplex reader activation
Thick metal enclosure	Total signal absorption	External antenna or on-metal-tag

Diagnostic Decision Tree

Tag not detected
├── UID detected by raw NFC tool?
│   ├── No  → Physical / chip issue (Layer 1-2)
│   └── Yes
│       ├── NDEF parse error in NFC TagInfo?
│       │   ├── Yes → NDEF formatting issue (Layer 3)
│       │   └── No
│       │       ├── OS permission or NFC disabled? (Layer 4)
│       │       └── Reader firmware / config issue (Layer 5)
└── Multiple tags in field? → Anti-collision / spacing (Layer 6)