What happens when you fill a tag completely?
It works. The tag reads normally and nothing degrades. What disappears is every option you had afterwards, because a message written to the exact limit cannot absorb one added character. The next correction means replacing the tag rather than rewriting it.
A full tag is a working tag
Nothing about a full tag is unstable. It reads at the same distance, at the same speed, with the same reliability as a nearly empty one.
There is no wear penalty either, since reading consumes nothing. A tag written to its limit and deployed for years behaves exactly like any other.
So the concern people have about filling a tag is misdirected. The problem is not the tag, it is the deployment around it.
What you lose
Headroom, and headroom is what makes a deployment repairable.
Every project produces a late correction: a number changes, a path moves, a name is misspelled. On a tag with margin that is a rewrite. On a tag at its limit, the corrected message is one byte too long and the write fails.
At that point the options are to shorten the content, which usually means removing something you wanted, or to replace the tags, which means physical access to every one of them.
The edge cases at the limit
The write itself is the first thing to check. A message that exceeds the free space is rejected rather than truncated, so the tag keeps its previous content and the tool reports a failure.
Locking behaves normally at any fill level, and locking a full tag is a decision to freeze the content permanently rather than merely for now.
And a tag verified as written is worth verifying by reading it back, particularly at the limit, since a write that only just fitted is the one most worth confirming.
How much margin to leave
Enough to absorb a realistic correction rather than a rounded percentage. For an address, room for a longer path and an extra parameter. For a contact card, room for one more field.
If leaving that margin means moving up a capacity step, ask first whether the content belongs on the tag at all. A link never grows, and it makes the margin question disappear entirely.
Where the content is genuinely fixed and offline, filling the tag is a reasonable choice made with open eyes. The mistake is filling it by accident and discovering the constraint during a correction.
Frequently asked questions
Does a full tag fail sooner?
No. Fill level has no effect on lifetime, and tags fail from physical damage rather than from how much of their memory is used.
What happens if the message is one byte too long?
The write is rejected and the tag keeps what it had. Nothing is truncated, which means you get a clear failure rather than a silently corrupted tag.
Can I reclaim space by erasing first?
Erasing gives back what the old message used, and it does not increase the tag's capacity. If the new content did not fit before, it will not fit after.
Is there a recommended fill level?
Leave room for one realistic correction rather than aiming at a percentage. Content that cannot spare that room is content that probably belongs on a server.