What decision this work should support
An NFC tag is a small, passive device that stores a small amount of data and transmits it when a compatible reader comes within a few centimetres. The tag contains a microchip and a coiled antenna, but no battery. When a phone or dedicated reader generates a magnetic field, the tag's antenna picks up enough energy to power the chip and broadcast its stored data back to the reader.
This inductive coupling is why the range is so short. Unlike Bluetooth beacons, which actively broadcast a radio signal that a phone can detect from several metres away, an NFC tag sits dormant until something practically touches it. The interaction is deliberate: a visitor taps a label on a museum exhibit, a customer touches a payment terminal, or a staff member places a phone against an asset tag.
Most tags used in retail, museums and venues store a simple URL, a text string or an identifier. When the phone reads the tag, the operating system decides what to do — typically opening a web page, launching an app or displaying the text. The tag itself does not track anyone. It holds no analytics, no logs and no connection to a backend until the phone acts on the data it receives.
NFC Tag Types and Memory Sizes
The NFC Forum defines several tag types, each based on a different underlying chip standard. The ones you will encounter in most deployments are Types 1 through 5, with Type 2 being by far the most common for general use.
| Type | Typical Memory | Practical Use |
|---|---|---|
| Type 1 | 96 bytes to 2 KB | Low-cost smart posters, basic URLs |
| Type 2 | 48 bytes to 2 KB | Widely available, good for URLs and short text |
| Type 3 | Up to around 1 MB | More complex data, less common in basic deployments |
| Type 4 | Up to 32 KB | Faster read/write, suitable for more demanding applications |
| Type 5 | Varies | Based on ISO 15693, used in some library and asset systems |
Memory size matters less than many people assume. A typical URL — even a long one pointing to a specific exhibit page — fits comfortably within 144 bytes. You only need larger memory if you intend to store data directly on the tag rather than linking to a server, or if you want to lock sectors and use the tag for more than one purpose over its life.
Tags also differ in whether they are read-only or read-write. Read-only tags are locked at the factory or can be permanently locked after you write to them once. Read-write tags can be overwritten, which is useful during testing but introduces a risk in public spaces if someone with an NFC writing app changes the URL. For permanent installations in museums or venues, locking the tag after configuration is standard practice.
NFC Read Range and Limitations
Expect a reliable read range of roughly one to four centimetres, depending on the tag's antenna size, the reader's antenna power and the physical environment. Some larger tags with bigger antennas might reach five centimetres under ideal conditions, but planning a deployment around anything beyond close contact will cause problems.
The short range is a consequence of the physics involved. Inductive coupling works well at very close distances but the field strength drops off rapidly. This is not a design flaw — it is the reason NFC is used for payment terminals, where you deliberately want the user to present their card or phone with clear intent.
Several factors reduce read reliability further:
- Metal surfaces: Metal detunes the antenna and can block the signal entirely. Tags intended for metal mounting have a ferrite barrier layer, but standard tags will fail or read unreliably.
- Water and liquids: High water content absorbs the magnetic field, which matters for tags placed on glass or near water features.
- Angle of approach: The reader's antenna and the tag's antenna need reasonable alignment. A glancing tap at a steep angle may not register.
- Phone case thickness: Thick cases, especially those with metal elements, can reduce the effective range enough to cause missed reads.
If your use case requires detecting a visitor as they walk past a point without stopping, NFC is the wrong technology. That is a scenario where Bluetooth beacons or other proximity sensors are more appropriate.
NFC-Compatible Phones and Devices
Nearly all smartphones sold in the UK over the past several years include an NFC reader. On Android devices, NFC has been standard equipment for a long time. Apple added NFC reading capability to iPhones starting with the iPhone 6, but the behaviour has changed across iOS versions, and some features remain restricted compared to Android.
On Android, an NFC tap typically triggers an intent that the browser or a registered app can handle. If the tag contains a URL, the browser opens it. If it contains an NDEF record formatted for a specific app, that app can launch directly. This gives integrators flexibility in how the tap is handled.
On iOS, Apple controls more of the NFC interaction. For basic NDEF tags containing URLs, iOS will generally open them in Safari without requiring an app. More complex interactions — reading specific tag types, writing to tags or using NFC for non-URL purposes — may require an app built with Apple's Core NFC framework, and some capabilities are restricted to certain iPhone models. If you are planning a deployment that relies on specific NFC behaviour on iPhones, check Apple's developer documentation for the current restrictions on the iOS version you are targeting.
For operational deployments, the practical step is to test with the actual phone models your visitors are likely to carry, not just one or two devices in the office. Different antenna placements in phone designs mean that the "sweet spot" for a reliable tap varies between models.
Where NFC Works Well and Where It Struggles
NFC suits situations where the visitor is already standing next to something and a deliberate tap is a natural action. Exhibit labels in museums, information points on retail shelves, access control on doors and asset tags in warehouses all fit this pattern. The user knows what they are tapping, why they are tapping it and what they expect to happen next.
The technology also works well when you want a reliable, app-free experience. A visitor does not need to install anything, grant location permissions or enable Bluetooth. They tap, and a page opens. For venues that cannot justify asking visitors to download an app, NFC removes that barrier entirely.
NFC struggles in several common scenarios:
- Passive detection at a distance: If you want to know when someone enters a zone without them taking any action, NFC cannot do it.
- High-throughput points: Entrance gates or busy corridors where people flow through quickly are poor environments for a technology that requires each person to stop and tap.
- Moving targets: Tags on moving objects, such as stock on a conveyor or items being pushed past a reader on a trolley, may not stay in range long enough for a reliable read.
- Harsh environments: Industrial settings with heavy metal shielding, constant moisture or extreme temperatures need specially rated tags and careful testing.
The decision between NFC and other proximity technologies is not about one being universally better. It depends on whether your scenario needs a deliberate, close-range interaction or an ambient, distance-based trigger. For the comparison itself, the neighbouring article in this series covers those trade-offs directly.
