User Memory

User Memory

User memory is the portion of an NFC tag's EEPROM storage that is available for application data — NDEF messages, custom application payloads, or raw binary data written by the tag owner. User memory is always smaller than total memory because every NFC chip reserves space for manufacturer configuration bytes, the UID, lock bits, the capability container, and internal registers.

Memory Map Examples

The relationship between total memory and user memory varies by chip:

Higher-security chips like the NTAG 424 DNA have proportionally more overhead because they store cryptographic keys, file access control settings, and SDM configuration in addition to the standard NFC metadata.

What Consumes User Memory

When writing NDEF messages to user memory, the actual payload is wrapped in NDEF TLV (Type-Length-Value) structures that consume additional bytes:

• NDEF message header: 2-6 bytes depending on payload length.
• NDEF record header: 3-8 bytes per record (flags, type, ID, payload length fields).
• NDEF terminator TLV: 1 byte marking the end of NDEF data.

For example, storing a URL like https://example.com in an NTAG 213 requires roughly 25 bytes of user memory: 1 byte for the encoding URIs with compact prefix compression" data-category="NDEF">URI record identifier code (HTTPS prefix abbreviation), the domain string, plus the NDEF wrapper overhead.

Maximizing Usable Space

Engineers can optimize user memory utilization through several techniques:

• Use NDEF URI abbreviation codes: The NFC Forum defines prefix codes (0x01 for http://www., 0x02 for https://www., 0x03 for http://, 0x04 for https://) that replace common URL prefixes with a single byte.
• Minimize record count: Each NDEF record adds header overhead. Combine data into fewer records when possible.
• Use short-form records: NDEF supports a Short Record (SR) flag that uses a 1-byte payload length field instead of 4 bytes for payloads under 256 bytes.