Back to guides

January NFC Tag Audit: Find, Rewrite or Retire Old Tags

An NFC tag audit takes about an hour: find every tag, scan it, rewrite the unlocked ones and retire the locked ones, since locking can't be undone.

Published

An NFC tag audit is a one-hour pass where you find every tag you have placed, scan it, and decide what to do with it: leave it, rewrite it, or retire it. Unlocked tags can be rewritten for a very long time. Locked tags cannot be changed, so the audit is mostly about knowing which is which.

If you set up tags during the year, some of them now point at a link that moved, a playlist you dropped, or a Wi-Fi password you changed. This guide walks through a simple audit you can finish before the new year gets busy.

Why January is a good time for an NFC tag audit

January already comes with a reset mood. You are putting away decorations, clearing the desk and writing down what you want to do differently. A tag check fits right in, and it takes less time than most resolutions.

Timing helps too. Tags tend to pile up in autumn and winter: a tag for the holiday hours on a shop door, one for a party playlist, one on a gift. By January some of those have done their job. If you built something for midnight, like a New Year countdown automation, the tag may now be a leftover that still triggers a shortcut you no longer want.

An audit has three steps: list the tags, scan each one, and choose an outcome. That's it. You don't need a spreadsheet unless you have dozens of tags, and even then a plain notes list works.

Find every tag you have placed

Start by walking through the places where tags usually end up. Work room by room, so you do not rely on memory.

Walk the house room by room

Check the front door, the kitchen, the desk, the nightstand and the fridge. Look under the lip of shelves, inside cabinet doors and on the back of picture frames. A small round sticker or a thin card with a faint outline is usually a tag. If you are unsure, a quick tap with your phone will tell you.

Check bags, car, desk and gifts you gave

Tags also live in places you carry with you: the glovebox, a gym bag, a keychain, a laptop sleeve. Write down tags you gave to other people too. You cannot rewrite those from your couch, but you can offer to update them next time you see the person.

Keep a short list as you go. For each tag, write where it is and what you think it does. You will compare that guess with the real contents in the next step, and the mismatches are the most useful part of the audit.

Scan each tag and note what it does

Now scan each tag and read what is on it. Do not change anything yet. You only want facts.

Read the action and whether it still works

Open the tag's contents and note the record type and the value: a URL, plain text, a phone number, a Wi-Fi entry or a Shortcut trigger. Then test the result. Does the link still open? Does the contact still have the right number? Does the automation still do what the label says?

Mark each tag with one of three notes: fine, stale or unknown. A stale tag is one whose action is out of date. An unknown tag is one you cannot explain, and those deserve a closer look before you leave them in place.

Check if the tag is writable

This is the step that decides everything else. NFC Forum tags can be in a read-only state or a read-write state. On Android, the Ndef class reports whether a tag is writable and whether it can be made read-only, and it does this without writing anything to the tag. It can also tell you the tag type and the maximum NDEF message size in bytes.

In practice, scan the tag with NFCore and check its status and details before you plan any edit. If the tag is writable, it goes in the rewrite pile. If it is read-only, it goes in the retire-or-relabel pile. If a write attempt fails on a tag you thought was open, treat it as locked.

Write down the memory size while you are there. NTAG213, NTAG215 and NTAG216 chips offer 144, 504 and 888 bytes of user memory, in that order. A long message that fits on a bigger chip will not fit on a smaller one, and that matters when you rewrite.

Rewrite the tags that are unlocked

Most home tags are unlocked, so this is where most of the audit happens. Pick the stale ones and give each a new action that matches its label, or update the label to match the new action.

A few habits keep rewrites clean:

  • Replace the old record instead of adding a second one, so the tag does one thing.
  • Keep the sticker or label in sync. A tag labeled "guest Wi-Fi" that now opens a playlist is a trap.
  • Test with a tap right after writing, on the same phone and, if you can, on a second one.

Rewriting is safer than most people expect. NXP lists its NTAG213, NTAG215 and NTAG216 chips at 100,000 write cycles and 10 years of data retention. A tag you edit a handful of times a year will not come close to wearing out. The 10 years refers to how long the data stays readable, not a promise about the sticker, the glue or the case, which usually give up first.

If you changed phones during the year, a few of your tags may point at Shortcuts that no longer exist on the new device. Our guide on what happens to your NFC tags and Shortcuts on a new phone covers that case. Usually the fix is to rebuild the shortcut and leave the tag alone. The tag itself is rarely the problem.

Some tags also have a password set. NTAG chips support optional 32-bit password protection, which limits who can write to a tag. That is a different feature from locking. A password-protected tag can still be changed by someone who has the password. A locked tag cannot be changed by anyone.

Locked tags are permanent: retire or relabel

Locking is the one part of tag care that has no undo. On Android, the call that makes a tag read-only is described as a one-way process that cannot be reverted. It sets the capability container to read-only and, where the chip allows, sets the lock bits permanently so the memory cannot be modified again. The documentation says "where possible", which means it does not work on every tag, and the call reports whether it succeeded.

NTAG chips support locking at a fine level: per page for the first 16 pages, and in larger blocks above that. Once those bits are set, no app can reverse them. That includes NFCore.

What do you do with a locked tag that has the wrong content? You have three honest options:

  1. Relabel it. If the tag points to a page or action that still works in some form, change the label on the sticker to match what it really does.
  2. Cover or remove it. Peel it off, or put a plain sticker over it. A removed tag does nothing, which is the safest result.
  3. Leave it, if the action is harmless. A locked tag that opens an old but valid page can stay. Just be sure the target is something you still control.

If the tag points to a link you own, you can often fix a locked tag without touching it. Update the page the link opens, or set up a redirect on your side. The tag keeps pointing at the same address, and the address now leads to the right place. This only works if you chose a link you control when you wrote the tag, so it is a good rule for new tags: lock only after a tag has been in place for a while, and only when the action cannot go stale.

Before you lock any new tag, ask whether you will want to change it next January. If the answer is maybe, leave it unlocked.

Keep a simple tag inventory

The easiest way to make next year's audit shorter is to leave yourself a list. It does not need to be fancy. A note with five columns is enough:

  • Name or label
  • Location
  • What it does
  • Locked or unlocked
  • Date last checked

A tag that is on the list is a tag you can find, and a tag with a date is one you can trust. If you like routines tied to places, the idea pairs well with one tag per room for a home reset checklist, since the same room-by-room walk gives you both the checklist and the inventory.

Add a line every time you place a new tag. It takes ten seconds and saves you the guesswork you just went through.

Your January checklist

Keep the audit small and repeatable. Find the tags, scan each one, write down what it does and whether it is writable, rewrite the stale unlocked ones, relabel or remove the locked ones, and save the list. NFCore can read the tag details and write new content, so the whole audit fits in one app. You can get it from the App Store or Google Play.

Frequently Asked Questions

How many times can I rewrite an NFC tag?

NXP rates its NTAG213, NTAG215 and NTAG216 chips for 100,000 write cycles and 10 years of data retention. A home tag you edit a few times a year will not come close to that limit.

Can I undo a locked NFC tag?

No. On Android, making a tag read-only is described as a one-way process that cannot be reverted, and it sets lock bits permanently where the chip allows. Plan to retire or relabel a locked tag instead of trying to change it.

How do I know if a tag is locked?

NFC Forum tags can be in a read-only or read-write state, and Android can report whether a tag is writable. In NFCore, scan the tag and check its status before you plan to rewrite it. If a write fails on a tag you thought was open, treat it as locked.

Should I throw away a tag I no longer use?

Not necessarily. A tag that is still writable can be rewritten with a new action. A locked tag can stay in place with a sticker over it, or be removed if you do not want it to trigger anything.