NFC in Museums and Art Exhibits: Tap a Label to Learn More

Stick a small NFC tag behind an exhibit label, point it at a web page you host, and any visitor can tap a phone to it to hear an audio description, read the wall text in their own language, or watch a sign-language clip — no app, no Wi-Fi pairing, no account. The tag costs cents; the experience it unlocks is the point.

Quick answer: a tap that opens a page

A museum NFC tag is a passive 13.56 MHz sticker — an NFC Forum Type 2 tag following ISO 14443-A — with a single URL written to it as an NDEF record. When a phone comes within about four centimetres, the tag wakes up on the phone's field and hands over the URL, and the browser opens your exhibit page.

iPhone XS and later read that URL in the background, so a tap on the top edge is enough. Older iPhones (7 through X) need an NFC reader app open first. Every NFC-capable Android opens the link on an unlocked screen. One important detail: write a plain URL record, not a Smart Poster record — iOS does not surface Smart Poster records during background reading, so a tap would do nothing on most iPhones.

Why museums reach for NFC

The strongest case is accessibility. One tap can route a visitor to an audio description for low vision, a sign-language video for deaf and hard-of-hearing guests, large-print text, or the same label in their preferred language — all from one tag, because the page you host decides what to show. It also updates cleanly: the tag only stores a URL, so you can rewrite the page behind it — new loan info, a corrected date, a fresh translation — without touching the physical label.

Be honest about the tradeoff. A QR code is free to print and visually discoverable: people see it and know to scan it. An NFC tag runs roughly $0.10 to $0.50 each, and the real cost is mounting and maintaining one at every stop. NFC is faster and tidier for a tap; QR wins on cost and on signalling it's there. Most museums pair both — a visible QR for discovery and an NFC tag behind it for the tap, pointing at the same URL.

Deploy it, step by step

1. Build one page per object. Each exhibit gets its own URL with the content and accessibility options you want to offer.
2. Pick a chip. A 144-byte NTAG213 holds a short URL with room to spare; use a URL shortener if your links run long.
3. Write a URL record. Encode the page address as a single URI NDEF record. Our write guide covers the steps and the common snags.
4. Mount it and add a QR. Place the tag where a phone naturally rests against the label, and print a matching QR code beside it for discoverability.
5. Test on both platforms. Tap with a recent iPhone and an Android before opening day — placement that works on one antenna can miss on another.
6. Lock the tags. Once the URLs are right, make them read-only so a curious tap can't overwrite them.

Common problems and fixes

If a tap does nothing, the phone is usually off-target — move the tag to where the antenna sits, the top edge on iPhone and the upper back on most Android handsets. A tag that won't accept new data is already locked, which is read-only by design. Mounted on a metal frame or plate, the metal detunes the antenna and kills the read; an on-metal tag with a ferrite backing fixes it. And if iPhones ignore a tag that Androids read fine, you almost certainly wrote a Smart Poster record instead of a plain URL — rewrite it as a URI record.

Doing this on NFCore

In NFCore, choose Write Data, pick the URL template, paste the exhibit page address, and tap the tag to write it. For a full gallery, write each tag in turn and lock it from the same screen. The memory dump view shows the raw NDEF bytes, so you can verify the URL landed before the tag goes on the wall. NFCore runs on iOS and Android, stores nothing in the cloud, and needs no account — get it on the App Store or Google Play and program a whole exhibit from one phone.

FAQ

Do visitors need an app? No. The tag stores a normal web link, so the phone's browser opens it. Only older iPhones (7 through X) need an NFC reader app; iPhone XS and later and all NFC Android phones read it natively.

Should we use NFC or QR codes? Use both. QR is free and visually discoverable; NFC is a faster tap. Point them at the same exhibit page and let visitors choose.

Which tag should we buy? An NTAG213 is plenty for a URL. Step up to an NTAG215 only if you plan to store more than a short link.