Back to guides

Wipe an NFC Tag Before Selling or Giving It Away: What Stays on It

Erasing an NFC tag clears its NDEF message, but the factory UID, the chip type and any lock bits stay. Here is what a new owner can still see and how to check first.

Published

Short answer: the message goes, the chip stays

Erasing a tag overwrites its NDEF message, which is the part you wrote: the URL, the Wi-Fi record, the text. It does not touch the chip's UID, its type or any lock bits. If you locked the tag, the old data stays on it for good.

What an erase overwrites

Everything you can see in a tag-reading app lives in user memory. On an NTAG213 that is 144 bytes in pages 4 to 39, rated for 100,000 write cycles, so rewriting it before a handover costs you nothing.

Android's API shows what the two common operations do. Writing an NDEF message replaces whatever the tag held, and formatting a tag leaves it read-write. A tag that is formatted but empty reads back with no message at all. That's what you want to hand over. If you are wondering how far a tag can be changed after the first write, see changing what a tag does after writing it.

What stays on the tag

The UID

The UID is the chip's serial number. On an NTAG213 it is 7 bytes, factory programmed, and listed as read-only. No erase changes it, so the new owner will see the same UID you saw.

The chip type and memory size

Any reader can tell an NTAG213 from other chips and see that it has 180 bytes of memory. That's how an app knows what it can write. It says nothing about you.

Why the UID rarely matters

The UID identifies a chip, not a person. Apps read it through the platform SDK, and copying it into an NDEF record is discouraged because it is insecure and easy to clone. The one real risk is a system you own that treats a UID alone as proof of identity, such as a door reader set to accept one tag. Remove that tag from the system before it leaves your hands.

Lock bits decide whether a tag can be wiped

NTAG213 has static lock bytes in pages 0 to 2 and dynamic lock bytes on page 40. They can switch memory to read-only irreversibly. Android's makeReadOnly does the same job on the NDEF side: it sets the CC field and, where possible, permanently sets the lock bits. The documentation calls it a one-way process that cannot be reverted.

A locked tag keeps its old message, and any erase attempt fails. You can check whether a tag is really read-only before you decide. If it's locked and the content is sensitive, don't hand it over. The content can't be removed, so bin the tag.

Password-protected tags

NTAG213 can also use a 32-bit password with a 16-bit acknowledgement to restrict writing, or even reading, from a page you choose. Unlike a lock, that protection is reversible. You need the password to remove it, so do that before the handover, or the next owner gets a tag they cannot rewrite. The difference is covered in protected versus locked.

Before you hand it over

  1. Scan the tag and check that it reads as empty, or holds a neutral message you chose.
  2. Confirm it is still writable: try writing a short text record.
  3. Remove any password you set.
  4. If the tag is locked, treat it as a one-time tag and bin it if the data is private.
  5. Remove the tag's UID from any access list or automation you own.

NFCore can read, write, erase and inspect NTAG tags on iPhone and Android without an account, which makes steps 1 to 3 a one-minute job. iOS has fewer low-level options than Android, so a lock or password check may need an Android phone.

Frequently Asked Questions

Can I change the UID of an NFC tag before giving it away?

On a genuine NTAG213, no. The 7-byte UID is factory programmed and read-only, and an erase only rewrites user memory.

Does erasing a locked NFC tag work?

No. Lock bits switch memory to read-only irreversibly, so the old data stays and the tag cannot be reused for new content.

Is it safe to hand over a tag that still shows its UID?

Usually yes. The UID only identifies the chip. It becomes a risk only if something you own accepts the UID alone as proof of identity, since UIDs are easy to clone.