Can a phone read two tags at the same time?
No. A phone selects one tag and ignores the rest, and stacking two tags against each other usually means neither works at all. The protocol has a procedure for arbitrating between tags, but two tags in contact prevent each other from powering up before that procedure can run.
The short answer
No, and the reason splits into two very different failures that look identical from the outside.
If the tags are near each other but not touching, the phone picks one. You get one result, arbitrarily chosen, and the other tag might as well not exist.
If the tags are stacked, you usually get nothing at all.
Why stacking breaks both
Two coils placed against each other are not two independent tags in a shared field. They interact.
Each one absorbs energy the other needs, so both may fall below the threshold required to boot. Worse, each detunes the other: an antenna is tuned to resonate at 13.56 MHz, and putting another coil against it shifts that resonance so neither couples efficiently any more.
The result is a complete failure rather than a degraded one, which is what makes it confusing. People expect stacking to be inefficient. It is closer to destructive.
What the protocol could have done
Anticollision exists precisely to handle several tags answering at once, and it works. Dedicated readers use it routinely.
It cannot help here because it operates on answers, and stacked tags never get far enough to answer. There is no collision to arbitrate when neither participant has enough power to speak.
This is the distinction worth carrying away: the standard solved the problem of many tags, and physics still limits how close those tags may be.
What to do instead
If you want two actions from one object, put both in a single tag as separate records rather than using two tags. It costs bytes and works.
If two tags must coexist on one object, separate them by a few centimetres and expect the phone to read whichever it meets. Do not design a flow that depends on which one.
If you genuinely need to read many tags in one gesture, you have left NFC's territory. That is what UHF RFID is for, with dedicated readers, and no arrangement of NFC tags will substitute.
And if a card in your wallet stopped working when you added another, this is the explanation. Wallets are stacks of coils, and contactless cards in contact interfere exactly like tags do.
Frequently asked questions
Why do two cards in my wallet stop working?
They absorb and detune each other, so neither couples well enough to be read. Separating them, or using a wallet that holds cards apart, restores normal behaviour.
Can I put two tags on one object?
Yes, if they are a few centimetres apart. Expect the phone to read whichever it happens to meet, and never design a workflow that depends on which one it picks.
Do dedicated readers manage several tags better?
They handle several tags in a field far better than a phone does, because they produce a stronger field and their software is built for it. They still cannot read tags that are stacked in contact.
Can one tag hold two different actions?
It can hold several records, though what the phone does with more than one depends on the platform. Generally the first actionable record wins, so treat additional records as fallback content rather than as a menu.