What does locking an NFC tag actually do?
Locking sets bits inside the chip that make its memory permanently read only. The operation is instantaneous, leaves no visible trace, and cannot be undone by any tool, any phone or the chip manufacturer. Everything else about the tag continues to work exactly as before.
What actually happens
The chip contains bits whose only purpose is to disable writing. Setting them is itself a write, and it is the last write the affected memory will ever accept.
These bits are designed to move in one direction. There is no command to clear them, no manufacturer procedure, no service. That is not a policy that could be relaxed, it is how the silicon behaves.
What a locked tag can still do
Everything except change. It powers up normally, answers normally, delivers its content to any reader, and is indistinguishable from an unlocked tag until something tries to write to it.
So a locked tag is not a damaged tag. It is a finished tag, and for a deployment where the content is settled that is exactly what you want.
What it can no longer do: accept new content, be formatted, be erased, or have its structure repaired if something goes wrong.
Why it leaves no trace
Nothing about the tag looks different. There is no marking, no indicator, no change in how it reads.
The only way to know is to try writing to it, or to read the configuration with a tool that reports the lock state. This is why a bag of mixed tags is a genuine hazard on a production line: locked and unlocked tags are physically identical.
How it happens by accident
Most writing tools present locking as a checkbox beside the write button. Tick it once, forget it is ticked, and every subsequent tag in the session is finished.
That is the single most common way people lose a batch of tags, and it produces a specific and recognisable pattern: the first few tags were fine, and everything after a certain point refuses to be rewritten.
Before locking anything
Read the tag back and confirm the content is complete and correct. A write interrupted partway, then locked, is permanent nonsense. Verification costs a second and the alternative costs the tag.
Frequently asked questions
Can I tell whether a tag is locked before writing?
A tool that reports the configuration will show the lock state, and a plain read will not. Attempting a write also tells you, at the cost of finding out the slow way.
Does locking protect the tag from being read?
No. Locking affects writing only. Anyone can still read a locked tag, which is usually the point since the content is meant to be read.
Is a locked tag still detected normally?
Yes, identically. Detection, identification and reading all behave exactly as on an unlocked tag, which is why the state is invisible until you try to write.
Can locking be partial?
On many chips yes, with different bits covering different regions of memory. That allows part of a tag to be frozen while the rest stays writable.