How to read, edit, and verify an existing NFC tag on iPhone
Use a read-first workflow to inspect public NDEF records, preserve the original value, validate the edit, write only to a compatible tag, and verify the result.
Editing an existing NFC tag should begin with a read, not a blank editor. The first scan establishes what the phone can actually see: protocol details, NDEF status, capacity, records, warnings, and whether a record can be mapped safely into an editable template.
1. Read and preserve the original
Start a scan and hold the iPhone near one tag. Before changing anything, review the decoded records and save or share a tag report when the original value matters. A report creates a practical rollback reference even though it cannot unlock a read-only or protected tag.
2. Distinguish public NDEF from protected systems
Boreal NFC works with public NDEF content. It does not copy payment, transit, access, hotel, secure identity, or protected credentials. A phone detecting an NFC object does not mean that object exposes an editable NDEF record.
3. Edit the value in the matching template
When Boreal NFC can map a record to a supported payload type, open it in the corresponding editor. Check the normalized value, visible destination, estimated encoded size, and any format warning.
For a public URL, open the destination before writing. A syntactically valid link can still point to the wrong page or fail on the network.
4. Confirm the tag can accept the edit
The active write session must connect to the tag, query NDEF status, and compare capacity with the message being written. Stop if the tag reports read-only or unsupported status. If capacity is insufficient, shorten the payload or choose a suitable replacement tag.
5. Write, then scan again
Keep one tag near the antenna throughout the write. After success, start a fresh read and compare the result with the intended value. For links, open the destination. For public sharing, also generate and test a matching QR fallback.
When to replace instead of edit
Replace the physical tag when it is read-only, damaged, unreliable in its installed material, too small for the intended payload, or not exposing compatible public NDEF content. Repeated writes cannot change those underlying constraints.
Sources and review
- Apple: Core NFC overview
- Apple: Building an NFC Tag-Reader App
- Boreal NFC 1.0.5 read, edit, report, validation, and write behavior reviewed August 12, 2026.
Use the pre-write checklist before committing the edit.