How the phone resolves the experience
The NFC Forum defines a set of tag types that standardise how chips communicate with phones and readers. When someone refers to an "NFC tag type," they are usually referring to these Forum specifications rather than a particular manufacturer's product name. Understanding the distinction matters because two tags from different suppliers can behave identically if they conform to the same type, even if the silicon inside is different.
Five tag types carry the official Forum designation, with a sixth added more recently:
- Type 1 (Topaz): The smallest and least expensive. Usable memory ranges from 48 bytes up to around 888 bytes, depending on the specific chip. Read and write speeds are modest. Suitable where you only need to store a short URL or a small text string.
- Type 2 (MIFARE Ultralight family): The most widely available type in retail and event deployments. Memory typically sits between 48 and 504 bytes. The ecosystem of stickers, wristbands and cards built on Type 2 is larger than for any other format, which keeps procurement straightforward.
- Type 3 (FeliCa): Designed around a faster communication protocol. Memory can reach several kilobytes. Type 3 tags are common in transport cards in Japan but are rarely the first choice for a UK museum or retail deployment unless a specific integration requires them.
- Type 4 (DESFire-like): Supports larger memory, commonly from 4 KB up to 32 KB or more on some chips. These tags can handle complex data structures and support access control features such as password-protected sectors. Read and write speeds are higher than Types 1 and 2.
- Type 5 (ICODE SLIX): Operates at a slightly different frequency band (ISO 15693) which can give a longer effective range than Types 1–4. Memory sizes start around 256 bytes and go well above 2 KB. Often chosen for asset tracking in warehouses rather than public-facing interactions.
- Type 6 (MIFARE DESFire EV1/EV2): Added to the Forum specifications to formalise support for a widely deployed secure chip. Memory typically ranges from 2 KB to 8 KB, with strong encryption and multi-application support.
A critical point that catches out first-time buyers: the number printed on a chip's datasheet is not all available for your content. NFC Data Exchange Format (NDEF) messaging adds overhead. Each NDEF record carries a header of several bytes, and the tag itself reserves a small area for configuration data. On a 48-byte Type 2 tag, you might have roughly 36 to 40 bytes of usable payload after formatting. That is enough for a concise URL but will not hold a vCard.
Memory in Practice
To judge whether a tag type will serve your needs, work backwards from the content. A plain-text URL of 30 characters occupies 30 bytes, plus NDEF overhead. A basic vCard with a name, phone number and email address can easily exceed 200 bytes. An NDEF record containing a small JSON payload for a museum exhibit might sit between 100 and 300 bytes. Once you have estimated your payload, add a safety margin of around 20 percent and compare that figure against the usable memory of the tag type you are considering.
Design for successful first-time use
For most UK retail, museum and event applications, the decision narrows quickly. If you are placing a tag on a product shelf, an exhibit plinth or a conference badge and the only payload is a URL pointing to a web page, Type 2 tags at 144 bytes or 504 bytes will cover the requirement with room to spare. The cost difference between a 48-byte and a 504-byte Type 2 tag is usually small enough that opting for the larger memory is a sensible default unless you are buying in tens of thousands and every penny matters.
Type 4 or Type 6 tags enter the picture when you need to store data directly on the chip rather than relying on a network link. Examples include offline access control credentials, loyalty point balances that must work without connectivity, or situations where the tag holds multiple NDEF records for different applications. The trade-off is higher unit cost and slightly more complex encoding during production.
Form factor interacts with type selection. Wristbands, stickers and disposable labels almost always use Type 2 because the chips are inexpensive and thin enough to embed in paper or fabric. Hard tags in ABS casings for industrial asset tracking are more likely to use Type 5, where the longer range and larger memory justify the bulkier housing.
Locking and Rewritability
Most tag types support a lock command that prevents further writes to some or all of the memory. For permanent exhibit labels or fixed wayfinding points, locking the tag after encoding prevents accidental overwrites. For reusable assets such as event lanyards that are re-encoded for each event, leave the memory unlocked and choose a tag rated for a high number of write cycles. Check the manufacturer's specification for the endurance figure, which is typically expressed as a number of write operations.
Some Type 4 and Type 6 chips offer granular access control: you can lock individual sectors or require a password to write. This is useful when multiple parties share access to the same tag — for instance, a venue operator and a ticketing provider writing to different memory areas on the same wristband.
Testing, support and incident response
The most frequent error is purchasing tags based solely on the total memory figure without accounting for NDEF overhead. A tag advertised as "144 bytes" does not give you 144 bytes of URL storage. Always confirm the usable NDEF payload with the supplier or calculate it from the chip datasheet.
A second mistake is confusing tag type with brand name. "MIFARE Ultralight" is a family of NXP chips that implement Type 2, but not all Type 2 tags are MIFARE Ultralight. If your integration documentation specifies a particular chip rather than a Forum type, verify that the tags you procure use that exact chip or a confirmed equivalent. Behaviour around locking, authentication and memory mapping can differ between chips within the same type.
Assuming universal phone compatibility is another pitfall. Nearly many current smartphones, with capabilities and default behaviour varying by model and platform can read Types 1, 2 and 4. Support for Type 3 and Type 5 is less consistent across Android and iOS devices. If your deployment relies on visitors using their own phones, stick to Types 1, 2 or 4 unless you have tested Type 3 or 5 thoroughly on the device mix typical of your audience.
Key Checks Before Ordering
- Confirm the NFC Forum type rather than relying on a product name alone. Ask the supplier which Forum specification the chip complies with.
- Request the usable NDEF payload size for the specific chip, not just the total memory.
- Check write endurance if the tags will be re-encoded repeatedly. A low endurance rating will cause failures in reusable workflows.
- Verify locking options. Determine whether you need one-time permanent locking, password-protected writes, or fully rewritable memory.
- Test a small batch on the actual phones and readers your visitors or staff will use. Do not assume that a tag working on a recent Android handset will behave identically on an older device or on iOS.
- Match the form factor to the environment. Paper stickers work for indoor exhibits but will not survive outdoor or industrial conditions. On-metal tags include a ferrite layer to prevent detuning, and forgetting this layer is a common source of field failures.
When the content you need to deliver exceeds what a practical NFC tag can hold, the solution is usually to store a short URL on the tag and serve the full content from a server. That approach keeps tag costs low, allows you to update content without re-encoding physical tags, and removes memory size from the decision entirely. The detailed trade-offs around dynamic URLs and server-managed content are covered separately in the discussion of dynamic QR codes, where the same principle applies.
