Two NFC Tags Close Together? Why Your Phone Reads the Wrong One

Your phone reads the wrong tag because every tag in range powers up and answers, and the reader has to pick one. Keep tags apart and give each its own tap spot, and the wrong reads stop.

If you have stuck two stickers next to each other, or you carry a bank card beside an access badge, you have probably seen it: you tap one and the other opens. Nothing is broken. It's just how HF tags behave when they share a field.

What anti-collision does when multiple NFC tags are close together

NFC tags at 13.56 MHz are passive. They have no battery and draw power from the reader's field, so when you bring a phone near a cluster, every tag in range wakes up at once.

That creates a collision: several tags answering the same reader at the same moment. An ST Microelectronics employee put it plainly in an ST community answer: the tags really do interfere with each other, and the reader "has to detect and solve this collision." The method is called anti-collision, and the standards define it. For ISO 15693 (Type 5) tags it sits in chapter 8 of part 3. For ISO 14443 Type A and B tags, the family behind NTAG and most phone-readable cards, part 3 is literally titled "Initialization and anticollision," as the ISO/IEC 14443 overview lists.

So a reader can, in principle, tell several tags apart. What it can't know is which one you meant.

Why your phone reads the wrong one

Kisi's explainer on cards interfering in a wallet lays it out. The reader activates every card in the field, "irrespective of whether it's the right card or not." All of them send their IDs. If the wrong card's signal arrives first, the reader treats it as the intended one. Their example is a bank card beating an office access card, so the door stays locked.

Tags stuck side by side behave the same way. A phone's antenna covers an area, not a point, so two tags within a few centimeters of each other can both sit inside it. Which one wins depends on timing and coupling, and a small shift in how you hold the phone can flip it.

There is a second step after the read. Once the phone has a tag, the operating system decides what to do with it. On Android, the NFC basics documentation explains that the system reads the first NDEF record to decide how to interpret the whole message, and that if more than one app can handle the result, the Activity Chooser appears. A chooser or a link prompt can look like a wrong read when the tag was fine. Android 16 and 17 also add notifications and open-link prompts for http and https tags, so a tap that asks before opening is working as designed.

Fixes that work

There's no single switch to flip. Kisi says outright that there is "no silver bullet," only ways to cut how often it happens. These are the ones worth trying, in order:

1. Add distance. NFC range usually tops out around 10 cm (about 3 inches), so tags kept further apart than that will not compete. If you are planning a layout, the NFC Forum CR15 range change is worth knowing about, since longer range makes spacing matter more.
2. Give each tag its own tap spot. One tag per surface, clearly marked. Don't stack tags or layer a new sticker over an old one.
3. Tap the right side. With cards in a wallet, presenting the correct side is often enough, even when the cards are closer than 10 cm.
4. Put metal between them. A layer of foil absorbs the signal of the tag furthest from the reader. Test it before you stick anything down, because metal near a tag also hurts that tag's own reads.
5. Remove the tag you no longer use. An old tag left in place is a tag that can answer.

Chip choice helps too. Our guide on which NFC tags work with iPhone covers what to buy so at least the tag type is not a variable.

The takeaway

Two tags close together is a physics problem first and a software problem second. Readers can resolve collisions, but your phone acts on one result, and you don't control which. Design the layout so only one tag is ever in range of a tap.

To check what a tag holds before you place it, scan it with NFCore on the App Store or Google Play and read the NDEF contents one tag at a time.

Frequently Asked Questions

Can a phone read two NFC tags at once?

Readers can detect several tags in the field using anti-collision, but a phone app normally acts on a single result. Treat one tag per tap spot as the dependable design.

How far apart should NFC tags be?

NFC range usually tops out around 10 cm (about 3 inches), so keeping tags further apart than that avoids most interference. Closer than that, test with your own phone and tags.

Does foil between tags help?

A metal layer such as foil can absorb the signal of the tag furthest from the reader. It can also weaken a tag mounted right against metal, so test the result before you stick anything down.