What to check before writing an NFC tag on iPhone

Writing an NFC tag is a physical change, so the useful moment to catch a problem is before the phone starts the reader session. A calm workflow separates payload validation from the tag’s actual NDEF status and capacity.

1. Check the payload itself

Decide what the tag should do and use the matching NDEF payload type. Boreal NFC currently supports website, text, phone, email, social, review, Google review, payment-link, contact-page, and Shortcut templates.

Before writing, the app checks for an empty value and validates the expected shape. URL-backed templates require a valid URL scheme; email and phone templates receive their own format checks. These checks reduce obvious mistakes, but they do not prove that a destination page, phone number, email address, payment link, or Shortcut will remain available.

2. Compare estimated size with the physical tag

Boreal NFC shows an estimated NDEF payload size before the write session. Version 1.0.5 estimates the normalized UTF-8 value plus encoding overhead and warns when the estimate exceeds 850 bytes.

That warning is a planning guardrail, not a substitute for the tag’s reported capacity. Apple’s queryNDEFStatus API returns the writable status and the maximum NDEF message size for the tag detected in the active session. The final decision must use that live tag response.

3. Check writable status

An NFC tag may report read/write, read-only, unsupported, or unknown status. Apple’s recommended write flow connects to one detected tag, queries its NDEF status, rejects unsupported or read-only states, and writes only to a writable tag.

Do not treat “the phone detected something” as proof that the tag contains editable public NDEF content. Payment, transit, access, hotel, and other protected credentials are outside Boreal NFC’s scope.

4. Keep one tag in the field

During a write, present one physical tag to the iPhone. Multiple nearby tags can make selection ambiguous. Keep unused tags away from the phone until the current write finishes.

5. Read the result again

A successful write callback is not the final acceptance test. Scan the tag again, inspect the decoded value, and open the destination. For public sharing, test the installed tag and its matching QR fallback on representative devices.

Sources and review

• Apple: Building an NFC Tag-Reader App
• Apple: queryNDEFStatus capacity and status
• Product validation behavior reviewed against Boreal NFC 1.0.5 source on August 12, 2026.

Next, compare NTAG213, NTAG215, and NTAG216 or review common iPhone NFC write failures.