Back to guides

Copy an NFC Tag to a Smaller Tag: Will It Fit in 144 Bytes?

Copying an NFC tag to a smaller tag works only if the whole NDEF message fits. Here is how to check it against an NTAG213's 144 bytes and shrink it if needed.

Published

Short answer: it fits only if the whole message fits

You can copy a tag onto a smaller one when the NDEF message, wrapper included, is under the smaller tag's user memory. For an NTAG213 that is 144 bytes, or roughly 130 characters of URL. A short link usually fits. A vCard or several records usually don't. Below: how to check the size, where the bytes go, and what to cut.

What 144 bytes really means

NXP's NTAG213, NTAG215 and NTAG216 offer 144, 504 and 888 bytes of user memory. The chips hold more than that in total: 180, 540 and 924 bytes. The difference is the serial number, lock bytes, the capability container and configuration pages, none of which you can fill with your own data.

So 144 bytes is the real ceiling for an NTAG213, and the NDEF message shares it with its own wrapper. Wakdev puts the practical result at about 130 characters of URL. The NTAG215 holds about 480 and the NTAG216 about 850. Our capacity by chip guide covers the other chips.

Where the bytes go

On a Type 2 tag such as these, the NDEF message sits inside a TLV: a 0x03 tag byte, a length, the records, and a 0xFE terminator. NXP's community notes describe that layout, and the short record format, where the payload length is a single byte, carries up to 255 bytes. Each record then adds its own header and type.

Two things work in your favor. A URI record stores common prefixes such as https://www. as one byte, so a URL costs fewer bytes than it has characters. And every extra record, such as a text label next to a link, pays its header again.

One caveat: lock or memory control TLVs can shrink the usable area on a given tag. Treat 144 as the upper bound, not a promise.

Check the message size before you copy

  1. Read the source tag and look at the NDEF size in bytes. Most readers show it next to the records.
  2. Compare it with 144. Leave a few bytes of margin.
  3. If the source is an NTAG215 or NTAG216, don't judge by the chip name. A 504-byte tag holding a 60-byte link copies to an NTAG213 without trouble.

In NFCore you can read a tag, see its records and sizes, and write the same records to another tag. Check the number first, so you don't find out halfway through a write.

What actually gets copied

You copy the NDEF message, not the chip. The 7-byte UID is programmed at the factory, so the new tag keeps its own. If something only recognises a particular UID, a copied message will not stand in for it. Our guide on how to copy the NDEF message, not the raw dump explains why that is the safer route. Only copy tags you own or control, such as your own stickers and business cards.

Before you write

Check the destination first. A locked tag cannot be rewritten, and a password-protected one needs its password. Read how to check whether the destination is locked before you spend a tag on it.

If the message is too big, you have three options:

  • Shorten the URL, or use a short link.
  • Drop records you don't need, such as a second text record.
  • Use an NTAG215 instead. It is the usual next step up.

Takeaway

Measure the message, not the chip. If it is under 144 bytes with its wrapper, an NTAG213 will take it. If not, trim it or step up to a bigger tag. You can do the read and the write in NFCore on iPhone or on Android.

Frequently Asked Questions

Can I copy an NTAG215 to an NTAG213?

Only if the NDEF message plus its wrapper fits in the NTAG213's 144 user bytes. A single short URL or a few lines of text usually does. A vCard or several records usually does not.

Does the copy get the same UID?

No. The 7-byte UID is programmed at the factory and the new tag keeps its own. Copying the content does not copy the identity.

Why does my app say the tag is too small?

The size you see includes record headers and the wrapper, not just your text. Shorten the content, remove a record, or move to a bigger chip.