What can you configure on a tag besides its content?
Depending on the chip, a tag exposes settings that sit outside the content area entirely: password protection, access conditions, a read counter, and mirroring of the identifier or counter into the content. Several of these are one way, so a mistaken setting can be permanent.
Beyond the content area
Most people meet a tag as a place to put a URL. Chips of any sophistication also carry configuration pages that control how the tag behaves, and those pages are not part of the content at all.
Formatting does not touch them. Writing does not touch them. Erasing does not touch them. They are changed only by tools that deliberately address them, which is why most users never encounter them.
What is commonly available
| Setting | What it does | Reversible |
|---|---|---|
| Password | Requires a key before writing, sometimes before reading | Yes, with the password |
| Access conditions | Chooses what the password protects and from which page | Yes, with the password |
| Read counter | Increments each time the tag is read | No, increments only |
| Mirroring | Injects the identifier or counter into the content | Yes, on most chips |
| Lock bits | Makes memory permanently read only | No, ever |
| Failed attempt limit | Blocks writing after repeated wrong passwords | Depends on the chip |
Availability differs by chip family, and the specific names and page numbers differ too. The manufacturer datasheet is the only authority for a given reference.
Mirroring, the useful one
Mirroring is the setting most worth knowing about because it solves a problem that otherwise needs a server.
The chip injects its own identifier, or its read counter, into the content as it is read. A tag holding a URL can therefore deliver a different URL to every reader, with the tag's identifier appended, without anything having written that identifier.
The consequence is that a thousand identical tags can be written with one identical message and still be distinguishable when tapped. For deployments needing per tag identification, that removes the entire per tag encoding step.
Where to be careful
Lock bits are the obvious one and they are covered elsewhere. The less obvious hazards are the settings that are one way without being called locking.
Some chips allow a configuration area to be frozen independently of the content, so a password can be made permanent. Some counters, once enabled, cannot be disabled. Some access conditions restrict future changes to themselves.
The rule that keeps you safe: read the datasheet for the specific chip before changing anything outside the content area, and test on one tag you are prepared to throw away. Configuration mistakes do not announce themselves, and a tag that still reads perfectly may have become unwritable forever.
Frequently asked questions
Do all tags have configuration pages?
No. The simplest chips expose little beyond content and lock bits, while more capable families offer passwords, counters and mirroring. What exists depends entirely on the chip reference.
Can I see the configuration with an ordinary tool?
Tools that offer raw memory access can read the pages, and interpreting them requires the datasheet since the layout differs between families. Some tools present the common settings by name.
Does mirroring work on every phone?
It happens inside the chip as the content is read, so nothing on the phone needs to support it. Every reader sees the modified content without knowing anything special happened.
Is a password the same as locking?
No, and the difference matters. A password is reversible if you know it, while locking is permanent for everyone including you.