# Programming NFC Tags with iPhone — Core NFC Guide

URL: https://proudtek.com/guides/nfc-tag-programming-iphone/
Source URL: https://proudtek.com/guides/nfc-tag-programming-iphone/
Generated: 2026-03-16T01:42:30.697Z
Kind: article
Publisher: Proud Tek Co., Limited
Author: Nancy Wu (NFC Product Specialist)
Published: 2026-04-19
Last Modified: 2026-06-10T18:00:00Z
Reviewed By: Proud Tek Editorial Team
Last Reviewed: 2026-06-10T18:00:00Z
Credentials: ISO 9001:2015, ISO 14001:2015, RoHS Compliant, CE Marking, REACH Compliant
Image: https://proudtek.com/blog-images/tap-phone-nfc.jpg
Image Alt: iPhone tapping NFC tag — Core NFC NDEF writing and Shortcuts programming reference

## Description
A practical guide to programming NFC tags with iPhone. Covering both consumer workflows (free App Store apps for URL, Wi-Fi, vCard and Shortcut...

## Summary
- A practical guide to programming NFC tags with iPhone.

## Buyer Guidance
- Best for: Programming NFC Tags with iPhone — Core NFC Guide supports RFID and NFC evaluation, comparison, and sourcing decisions.
- Compare first: Compare Programming NFC Tags with iPhone — Core NFC Guide against reader compatibility, chip family, material, and deployment environment.
- What to confirm: Confirm target application, compatibility requirements, customization needs, quantity, and sample expectations before quoting Programming NFC Tags with iPhone — Core NFC Guide.

## FAQ
- Q: Which iPhone models can write to NFC tags?
  A: iPhone XS, iPhone XR, and every subsequent model (iPhone 11, 12, 13, 14, 15, 16 series and beyond) can write to NFC tags when running iOS 13 or later. iPhone 7, 8, and X can read NFC tags (via apps and background NDEF URL detection) but cannot write to them. iPhone 6 and earlier have no NFC capability. For a new NFC programme in 2026, you can assume the overwhelming majority of iPhone users are on iPhone XS or later and can both read and write tags.
- Q: Do I need a developer account or coding skills to program NFC tags with iPhone?
  A: No. Free App Store apps (NFC Tools, NXP TagWriter, Simply NFC) let any iPhone user program NFC tags without writing code or having a developer account. These apps handle NDEF encoding, iPhone antenna interaction and tag verification. Coding is only required for custom workflows. Building your own branded NFC app with Core NFC, creating advanced authentication flows (NTAG 424 DNA SUN verification), or integrating NFC reads into a larger enterprise application. Most commercial NFC programmes start with App Store apps and only move to custom development when the use case requires it.
- Q: What's the difference between Core NFC and iOS Shortcuts for NFC interaction?
  A: Core NFC is Apple's low-level framework for iOS apps to read and write NFC tags with user permission. It requires a developer account, an Xcode-built app and user-initiated session activation. iOS Shortcuts is a higher-level automation system that lets end users bind specific NFC tag UIDs to custom automation workflows (open URL, run HomeKit scene, send message, launch app). Shortcuts doesn't require coding or developer account; it's configured entirely within the Shortcuts app. For broad consumer NFC programmes, the NDEF URL record (read by all iPhones in background) is the primary delivery mechanism; Core NFC and Shortcuts are complementary layers for per-app and per-user experiences.
- Q: Can iPhone write to MIFARE Classic tags?
  A: No. Apple Core NFC does not provide access to the MIFARE Classic air-interface protocol (which uses NXP's proprietary Crypto1 authentication). iPhone cannot read or write MIFARE Classic 1K / 4K tags. For NFC programmes that need iPhone compatibility, use NTAG 21x (NFC Forum Type 2), MIFARE Ultralight or Ultralight C (NFC Forum Type 2), MIFARE DESFire EV1/EV2/EV3 (NFC Forum Type 4 via ISO 7816-4 APDUs, readable on iPhone XS+), or NTAG 424 DNA. These chips are universally supported across iOS and Android. Programmes with existing MIFARE Classic infrastructure typically need to migrate to DESFire or NTAG for cross-platform compatibility.
- Q: How does iPhone background NDEF URL detection work?
  A: Background NDEF URL detection was introduced with iOS 13 on iPhone XS, XS Max, XR and every later model (iPhone 11 / 12 / 13 / 14 / 15 / 16 series) — see Apple's 'Adding Support for Background Tag Reading' developer documentation. iPhone 7, 8 and X have NFC hardware but lack the system-level background reading capability. On supported devices, when the phone is awake (screen on) and unlocked, iOS continuously listens for NFC tags carrying NDEF URL records; on detection it displays a notification banner with the URL. Tapping the notification opens the URL in Safari, or triggers a Universal Link to deep-link into the installed app. No app needs to be open. The URL must be a standard https/http web URL; non-URL NDEF records (text, vCard, raw MIME) do not surface a background notification. This is the mechanism behind most consumer NFC experiences on iPhone — restaurant menus, smart posters, product authentication, hotel-room engagement and Apple Wallet pass distribution.
- Q: Can iPhone act as an NFC card and emulate a contactless credential to a reader?
  A: Yes, with caveats. iOS 17.4 introduced the Apple Core NFC `CardSession` and `NFCPresentmentIntentAssertion` APIs that let third-party apps perform ISO 7816 host card emulation (HCE) for in-app contactless transactions. The initial release was restricted to banking and wallet apps operating in the European Economic Area, with developers required to obtain a special HCE entitlement from Apple. iOS 18 / 18.1 expanded availability to additional regions and use cases (loyalty, transit cards, identity, building access). Devices need to be iPhone XS or later. Outside HCE, Apple Wallet passes (PassKit) have long supported NFC interaction at terminals — that path remains the lowest-friction route for transit, loyalty, employee-badge and event-ticket programmes that don't need full custom HCE control.
- Q: Which NFC chip should I pick for my iPhone NFC programme?
  A: For most consumer programmes (URL redirects, business cards, restaurant menus, smart posters, Google Review cards), NTAG 213 is the default. Cheap, iPhone-compatible, and well-suited to short URL and text content. For content longer than roughly 130 URL characters, use NTAG 215 or NTAG 216 (504 and 888 bytes respectively). For luxury authentication, tamper-evident tags or any programme requiring per-tap cryptographic proof, use NTAG 424 DNA which supports SUN messaging natively readable on iPhone Core NFC. For legacy MIFARE Classic programmes needing iPhone support, migrate to NTAG or MIFARE DESFire since Classic is not iPhone-accessible.
- Q: Can Proud Tek pre-encode tags so customers don't need to program them on iPhone?
  A: Yes. Proud Tek's pre-encoding service accepts a URL template or NDEF content specification (URLs, Wi-Fi credentials, vCards, custom NDEF records) and returns tags pre-encoded at production time. Customers receive ready-to-use tags with zero in-house programming required. This is ideal for large-volume consumer programmes (thousands to millions of tags), retailer promotional campaigns, and enterprise deployments where programming by end users is impractical. For programmes that need per-tag unique content (unique URL serialization, per-tag loyalty IDs), we provide tag-serialized encoding with a TID-to-content mapping file suitable for downstream systems to query.

## Machine Routes
- JSON: https://proudtek.com/machine/guides/nfc-tag-programming-iphone.json
- Text: https://proudtek.com/machine/guides/nfc-tag-programming-iphone.txt