Interaction model, range and discovery
Near-field communication tags provide a way to attach digital information to a physical object or location. A visitor taps their phone against a tag on an exhibit plinth and receives a webpage, audio clip, or image. A facilities manager taps a handheld reader against a tag on an air-handling unit and pulls up the maintenance schedule. The underlying mechanism is the same in both cases, but the operational requirements differ considerably.
NFC tags for exhibits and assets are passive components. They contain a microchip and an antenna, but no battery. Power comes from the electromagnetic field generated by the reader—usually a smartphone. This means the tag will sit dormant for years without degrading, which suits environments where exhibits or assets remain in place for long periods. However, it also means the tag cannot push notifications or initiate interaction on its own; the user must physically present their device within a few centimetres.
Tags store data in NDEF (NFC Data Exchange Format) records. For most exhibit and asset applications, the record is simply a URI pointing to a web address. The phone reads the URI and opens it in the browser. No app is required for this basic interaction on either Android or iOS, which removes a significant barrier to use. More complex payloads—such as vCard records, plain text, or custom application commands—are possible but add complexity without clear benefit for most information-delivery scenarios.
Tag memory capacity matters when you move beyond a simple URL. NTAG213 chips offer 144 bytes of user memory, sufficient for a short URL. NTAG215 provides 504 bytes, and NTAG216 offers 888 bytes. If the destination URL is long, or if you need to store multiple records on a single tag, the higher-capacity chips become necessary. For most exhibit information pages served through a content management system, a short redirect URL on an NTAG213 is adequate.
The distinction between exhibit-facing and asset-facing use cases is important. Exhibit tags are public-facing, must work reliably with a wide range of consumer phones, and are judged on the quality of the experience they deliver. Asset tags are operational, typically read by staff devices or dedicated scanners, and are judged on data accuracy and integration with back-end systems. Mixing these two purposes on the same tag is rarely sensible.
Design for successful first-time use
Museums, Galleries and Heritage Sites
In a museum context, NFC tags are often placed beside or behind exhibit labels. A visitor who wants more detail than the physical label provides can tap to access extended text, video, or audio description. This works well for exhibits where space for printed text is limited, or where content needs to be updated without reprinting labels. Because the tag simply points to a URL, updating the content means changing what the web page serves, not replacing the physical tag.
Heritage sites with outdoor exhibits present a particular set of conditions. QR codes printed on laminated boards can degrade from UV exposure and weather. An NFC tag embedded in a more robust fixture—such as a metal plaque or a stone marker—can survive longer in exposed conditions, provided the tag itself is specified for outdoor use and the enclosure does not block the radio field. On-metal tags with a ferrite layer are necessary when the tag is mounted directly onto a metallic surface.
Accessibility is a genuine strength of NFC in this setting. A visitor who cannot read small print on a physical label can tap to receive the same information in a larger font or have it read aloud by their phone's screen reader. Multilingual content is straightforward: the tap can lead to a page that detects the phone's language setting or offers a language selector, avoiding the need for multiple printed translations on a single label.
Venue and Operational Asset Tagging
For operational assets—projectors, lighting rigs, fire extinguishers, HVAC components, IT equipment—NFC tags serve as a physical link to a digital record. A technician taps the tag and sees the asset's installation date, service history, manual, and the name of the responsible contractor. This removes the need to search a database by asset number or description, which is slow and error-prone when dealing with hundreds of similar-looking items.
In practice, asset tagging requires coordination between the physical installation and the software platform. Each tag must be written with a unique identifier that corresponds to the correct record in the asset management system. If the mapping between tag and asset breaks down—because a tag was moved, a fixture was replaced, or the register was not updated—the system becomes unreliable. Maintaining an accurate register of which tag ID is attached to which physical asset is an ongoing operational task, not a one-time setup.
Tag Mounting and Physical Placement
Read range for passive NFC tags is typically between one and four centimetres, depending on the tag antenna size, the reader device, and the presence of intervening materials. This short range is an advantage for intentional interaction—a visitor clearly chooses to tap—but it means placement must be precise. If the tag is recessed, behind thick glass, or at an awkward angle, users will struggle to get a successful read.
Mounting methods vary. Adhesive-backed tags work on clean, flat surfaces. For rough or irregular surfaces, a recessed mount or a custom enclosure may be needed. In high-traffic environments, tags must be protected from deliberate or accidental damage. Tamper-evident enclosures make it obvious if a tag has been removed or interfered with, which matters for asset tags where the link between physical object and digital record has security implications.
Phone cases affect readability. A thick case with a metal or magnetic component can reduce or block the NFC field entirely. This is not something the venue can control, but it is a reason to test with a range of common phone cases during pilot stages and to ensure signage makes it clear that the user should tap the phone directly, not wave it vaguely nearby.
Security, fallback and maintenance
Material Interference and Tag Selection
Mounting a standard NFC tag directly onto a metal surface will typically render it unreadable. The metal reflects and absorbs the radio signal. On-metal tags incorporate a ferrite layer that isolates the antenna from the metal, restoring functionality—but at a slightly reduced read range. If your exhibit plinths, display cases, or asset housings are metal, on-metal tags are not optional. Ordering standard tags and discovering this after installation is a common and avoidable error.
Water and thick dielectric materials also attenuate the signal. Tags embedded under thick resin, behind multiple layers of glass, or inside certain types of protective casing may not read reliably. The only reliable way to confirm is to test the specific tag model in the specific enclosure with the target devices before committing to a bulk order.
Static vs Dynamic Content
Writing a fixed URL to a tag and never changing it is simple and robust. The tag becomes a permanent pointer, and all content updates happen on the server. This is the correct approach for most exhibit and asset applications. Where organisations run into difficulty is writing long, complex URLs with query parameters directly onto tags, then needing to change those parameters later. Once a tag is locked—and locking is good practice to prevent tampering—the URL cannot be overwritten. Using a short redirect URL that you control gives you flexibility to change the destination without touching the physical tag.
Tag Security and Locking
Unlocked tags can be overwritten by anyone with an NFC-capable phone and a tag-writing app. In a public environment, this means a visitor could theoretically change the URL a tag points to. Locking the tag after writing prevents this. Most NTAG chips support a one-time lock command that makes the memory read-only. For asset tags in operational use, locking is essential. For exhibit tags, the risk is lower but still worth eliminating, particularly in unsupervised areas.
Locking does not prevent physical removal or replacement of the tag. If an attacker can swap your tag for one pointing to a malicious URL, locking provides no protection. Tamper-evident mounts and regular physical inspections are the countermeasure here. For most museum and venue environments, the practical risk is low, but it should be assessed rather than assumed away.
Platform and Device Compatibility
Both Android and iOS support NDEF URI dispatch without a dedicated app. On Android, this has worked reliably for several years. On iOS, Apple introduced native NFC tag reading in iOS 11, but the behaviour has evolved across versions. Current iOS versions handle NDEF URLs well, but it remains good practice to test with the OS versions your visitors are actually running, rather than assuming universal compatibility.
Some older or budget Android devices have NFC hardware that is slow to wake or has a very small sweet spot for reading. If your pilot testing reveals that a significant proportion of test devices struggle, consider whether the tag antenna size or placement can be improved before expanding the deployment.
Key Checks Before Deployment
- Confirm the surface material at every planned tag location and order on-metal tags where needed.
- Test read performance with the tag in its final mounting position, using a representative range of phones and common case types.
- Verify that the destination URL loads correctly on both Android and iOS browsers, including any redirect chains.
- Lock all tags after writing and record the tag ID, written URL, and physical location in an asset register.
- Establish a process for updating the destination content without needing to replace physical tags.
- Plan for tag replacement when exhibits are moved, rotated, or deinstalled—tags left behind on empty plinths create confusion.
- Ensure a non-NFC fallback exists for visitors whose devices do not support NFC or who cannot tap for physical reasons, such as a short URL printed beside the tag.
NFC for exhibit and asset information is a mature, low-maintenance technology when deployed with attention to physical placement, material compatibility, and content architecture. Its limitations—short range, requirement for deliberate user action, and vulnerability to physical interference—are well understood and manageable. The failures tend to come not from the technology itself but from treating tag deployment as a purely digital task that does not require the same rigour as physical signage or fixture installation.
