Why Your iPhone Won't Write to an NFC Tag: Common Fixes

Quick answer

Four things usually explain a failed NFC write on iPhone: the tag was never formatted to NDEF, it's locked or password-protected, the data is bigger than the tag can hold, or something — a case, metal, moving the phone mid-tap — is interfering with the field. Scan the tag with NFCore's Tag Inspector first. It tells you which of the four you're facing before you burn ten minutes retrying the same write.

Step-by-step: diagnose before you assume the tag is broken

Scan before you retry

A tag-inspector tool — NFCore's Tag Inspector included — reports format status, lock-bit state, password-protection state, and remaining capacity in one pass. That single scan tells you whether you're chasing a formatting problem, a lock problem, a capacity problem, or nothing at all.

Rule out a known iOS issue

A subset of iPhones on iOS 15.4 through 16.1 reported NFC tags failing to read or write entirely. Apple never issued an official fix. Two things helped some users anyway: toggling AirDrop from "Contacts Only" to "Everyone" and back, or resetting network settings (Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings). If every tag fails the same way on one of these versions, try that before blaming the tags themselves.

Common problems and fixes

Unformatted or previously-used tag

Tags fresh from the manufacturer are often not pre-formatted to NDEF — just raw memory with no capability container written. Core NFC can only write to tags already in NDEF format, so writing to an unformatted one throws an error instead of formatting it automatically. The fix: format it once with an NDEF-capable app, then write normally from there. Starting over with a tag you've already used for something else? See how to erase and reformat a tag to reuse it.

Locked or password-protected tag

A tag locked — permanently, or behind a password — by a prior app or owner rejects every write, in every app, NFCore included. There's no reliable Core NFC path to force an unlock. Developers have reported writes still failing with a "Stack Error" even after a password handshake succeeds. Your realistic options are the app that locked it, or a new tag. See password protection vs. permanent locking for what's actually recoverable and what isn't.

Capacity exceeded

Consumer tags run on small, fixed memory budgets: NTAG213 holds 144 usable bytes, NTAG215 holds 504, and NTAG216 holds 888. The real writable space shrinks a bit further once the capability container and lock bytes are subtracted. A tracking-heavy URL or a full vCard can blow past a 213 without much warning. Full breakdown by chip: how much data fits on an NFC tag.

Case, metal, and movement interference

Cases with metal plates, kickstands, or magnetic wallet attachments can weaken the field enough to cause intermittent or total write failures — even on a tag that's perfectly healthy and unlocked. Metal directly under the tag does the same thing. Writes failing on and off? Pull the case and try again before you troubleshoot anything else.

A write got interrupted mid-tap

Pull the phone away before a write finishes and you can corrupt the capability container or lock bits. The tag looks fine, but it fails every write after that. It's a hard one to diagnose for exactly that reason. If a tag that used to work suddenly refuses every write right after an interrupted tap, reformatting is usually the only fix.

Doing this on NFCore specifically

NFCore's Tag Inspector reports format, lock, password, and capacity state in a single scan, so you're not guessing at which cause applies. Worth saying plainly: like any app built on Core NFC, NFCore can't force-unlock a tag that another app password-protected. That's a platform limit, not an NFCore gap. Setting up tags for the first time? Download NFCore and scan before you write.

Frequently Asked Questions

Why does my iPhone say the tag isn't writable, or just fail silently?

One of four causes: unformatted tag, locked or password-protected tag, a message bigger than the tag's memory, or field interference from a case, metal, or movement. Work through them in that order.

Can I unlock a password-protected NFC tag from my iPhone?

Not reliably — Core NFC has no consistent way to authenticate and unlock one. Try the app that locked it first, or plan on replacing the tag.

How much data can I actually write to an NFC tag?

NTAG213 holds 144 usable bytes, NTAG215 holds 504, and NTAG216 holds 888 — slightly less once the capability container and lock bytes are subtracted. A long URL or vCard can exceed a 213 easily.

Does my phone case affect writing to NFC tags?

Yes. Metal plates, kickstands, and magnetic wallet attachments can weaken the field enough to cause intermittent or total write failures, even on a healthy tag.

Conclusion

Four causes cover nearly every "won't write" case on iPhone: an unformatted tag, a locked or password-protected tag, a message too big for the chip, or field interference. Scan first, don't guess — it turns a frustrating retry loop into a two-minute fix. For more, see password protection vs. permanent locking and NFC tag capacity by chip.