The NFC Tag UID: What It Is and Why It Can't Be Changed

What Is an NFC Tag UID?

Every NFC tag carries a UID — a serial number the chip hands over the instant a reader gets close enough to power it up. On the tags NFCore reads and writes most often — NTAG213, NTAG215, NTAG216, and similar NFC Forum Type 2 chips — that UID is 7 bytes long, addressed at cascade level 2 under ISO/IEC 14443-3. The first byte is fixed: it's the manufacturer ID ISO assigns to the silicon vendor, so NXP-made chips all start with the same byte (04h). The remaining six bytes are unique to that one chip.

Two extra checksum bytes — BCC0 and BCC1 — ride along during the handshake. They let a reader confirm the UID came through clean while it sorts out which tag to talk to, if more than one is sitting in the field. That handshake, called anticollision, is why your phone can pick out a single tag even when you've got a stack of them on your desk.

Why the UID Can't Be Changed

The UID isn't stored the same way your NDEF content is. It's written into a locked section of the chip during manufacturing — before the tag ever ships — and it sits outside the rewritable EEPROM pages that hold URLs, text, or Wi-Fi credentials. There's no documented command on a standard NTAG or MIFARE Ultralight chip that unlocks or rewrites it, which is exactly what NXP's own engineers point to when this comes up: it's fused into the silicon, not a setting you toggle.

One narrow exception is worth knowing: a small category of "UID-changeable" or "magic" tags exists, aimed at lab testing and card emulation rather than everyday use. Buy a standard pack of NFC stickers or cards and you won't run into one — but it's why "the UID can never be changed" isn't quite a blanket rule.

The UID vs. Your Tag's NDEF Memory

This is the part that trips people up in NFCore's Tag Inspector: writing new content to a tag never touches its UID. Overwrite a tag with a new URL, Wi-Fi credential, or contact card, and that write lands in the tag's NDEF user memory — a completely separate set of pages from the locked UID block. Rewrite a tag a hundred times and the UID in the inspector won't move, because the write path never goes near it. For a refresher on how tags organize that writable space by Forum type, that's a good next stop.

What the UID Is (and Isn't) Good For

Because it's stable and unique per tag, the UID makes a solid trigger for automation. A Shortcuts action that only fires for one specific tag, a smart-home routine tied to the tag by your front door, an asset-tracking system that logs which physical item a scan belongs to — all of it depends on the UID staying put. That's where NFCore's Tag Inspector reading the UID directly off the chip earns its keep: you can confirm you're holding the exact tag your automation expects, not just "a tag."

Where it falls short is as a standalone security credential. Standard NFC communication isn't encrypted, and because it rides the same protocols as contactless cards, it's exposed to relay attacks, where an attacker relays a legitimate tag's response to a reader in real time. Add in UID-changeable tags, and access-control systems that matter shouldn't treat a matching UID as proof on its own — it's a good first factor, not the whole lock. See our NFC security basics guide for more.

Frequently Asked Questions

Can I change the UID of an NFC tag?

No, not on standard consumer tags like NTAG213/215/216 or MIFARE Ultralight. The UID is burned into a locked area of the chip during manufacturing, separate from the rewritable memory that holds your NDEF content, and there's no documented command that rewrites it. A small category of "UID-changeable" or "magic" tags exists for lab and emulation use, but they're the exception, not something you'll find in a typical tag pack.

Is the NFC tag UID the same as the data I write to it?

No. The UID lives in a separate, factory-locked block used for anticollision and identification. The data you write with NFCore — URLs, text, Wi-Fi credentials, contact cards — goes into the tag's user memory (EEPROM pages), which you can rewrite as many times as you want without ever touching the UID.

Can I use a tag's UID as a security key?

Only for low-stakes convenience automations, not for anything where being wrong is costly. Standard NFC communication isn't encrypted, and a small number of UID-changeable tags exist that can be provisioned to answer with someone else's UID. Treat the UID as a reliable trigger for a Shortcut or smart-home routine, not as a standalone lock-and-key credential.

Conclusion

The UID is the one part of an NFC tag set the moment it's manufactured, staying fixed for the tag's whole life — a 7-byte serial number, checksummed for anticollision, living in a locked block separate from the NDEF content you write and rewrite. That permanence makes it useful for automations and asset tracking, and limited as a standalone security credential. Building a routine around a specific tag? Open it in NFCore's Tag Inspector first and confirm the UID you're targeting is the one you think it is.