Can Your Smartwatch Read NFC Tags? Apple Watch vs Wear OS
Your watch has an NFC chip, but that doesn't mean it can read a tag the way your phone can. Apple Watch locks NFC to Wallet; Wear OS support depends on the model. Here's what actually works — and what to do instead.
What it is (one-paragraph answer)
Short answer: no, not reliably. Apple Watch has an NFC chip, but Apple only lets it talk to Wallet and Apple Pay. There's no Core NFC API on watchOS, so no app can open a tag-reading session on the watch itself. Wear OS looks less locked-down on paper, but most current watches still restrict their NFC controller to the secure element used for Google Wallet tap-to-pay. Whether a given model reads generic tags comes down to the manufacturer, not the operating system. If you want to read an NFC tag today, your phone is still doing the work.
How it actually works
Apple Watch: Wallet-only, no Core NFC
Core NFC is Apple's framework for detecting tags, reading NDEF messages, and writing to writable tags — but it's scoped to iOS and iPadOS only. No watchOS target exists. Third-party developers simply have no API to build a tag reader for Apple Watch. The chip is there, and it's used every day for Apple Pay, but that traffic runs through a closed payment stack that never touches the reader-session APIs iPhone apps rely on for NDEF.
This isn't new. A developer forum thread requesting watchOS NFC tag reading has been open since 2020, with dozens of replies and zero roadmap commitment from Apple. Why the holdout? Developers point to two likely culprits: an active reader session would drain battery fast on a cell much smaller than an iPhone's, and there's not much room inside the case for a reader-capable antenna alongside the one already dedicated to payments.
For contrast, Apple opened the iPhone's NFC chip to third-party apps years ago — exactly the kind of access Apple Watch still doesn't have.
Wear OS: it depends on the watch
Android's NFC and NDEF APIs — the tag dispatch system, NdefMessage, NdefRecord — are documented at the platform level with no explicit carve-out for Wear OS. That's a real difference from Apple's approach, where watchOS is excluded from Core NFC by design. A Wear OS watch could, in principle, expose the same reader APIs a phone does.
In practice, it usually doesn't. Most current Wear OS watches from Samsung, Google, and other manufacturers lock the NFC controller to the secure element handling Google Wallet tap-to-pay rather than opening it to general reader mode. So the honest answer for Wear OS is "check your model" — don't assume it reads a tag the way iOS and Android handle NFC differently on phones.
Where you'll see it
Payments are the one place watch-NFC genuinely works on both platforms. Tapping your wrist to a card reader for Apple Pay or Google Wallet is fast, and it's reliable. Worth saying plainly, because it's easy to assume NFC is broken on watches in general when really it's just tag-reading that's missing.
For home automation, the tap still happens on your phone. An iOS Shortcuts NFC trigger fires when you tap your iPhone to a tag. There's no Apple Watch equivalent — the automation starts on the phone even if the result, a scene change, a log entry, a notification, shows up on your wrist a second later.
Same story for digital business cards, event badges, and asset tags: whoever's reading the tag is tapping a phone, not a watch, even if the person on the other end is wearing one.
Tips, gotchas, and a quick how-to with NFCore
Don't build a workflow around wrist-based tag reading. It isn't there yet on either platform, and nothing suggests that's changing soon. Treat the phone as the reader and the watch as where the outcome shows up.
Building an automation? Open NFCore on your iPhone, read or write the tag, then set up the action you want triggered. If the goal is something you'll notice on your wrist — a workout log, a smart-home scene, a reminder — pair that action with a Shortcuts notification or a watch complication instead of waiting on hardware that doesn't exist yet.
Try the read and write flow yourself in NFCore, free on the App Store.
Frequently Asked Questions
Can Apple Watch read NFC tags on its own?
No. Apple Watch has NFC hardware, but Apple only exposes it to Wallet and Apple Pay — there's no Core NFC API on watchOS, so no app can start a tag-reading session on the watch itself. A read has to happen on the paired iPhone.
Does Wear OS support reading generic NFC tags?
It depends on the watch. Wear OS's NFC APIs aren't platform-restricted the way watchOS is, but most current Wear OS watches from Samsung, Google, and other manufacturers lock the NFC controller to the secure element used for Google Wallet, so generic NDEF reading isn't guaranteed — check the specific model.
Can I trigger an iOS Shortcut by tapping an NFC tag with my Apple Watch?
Not directly. iOS Shortcuts' NFC automation trigger runs on iPhone; there's no Apple Watch equivalent, so the tap still has to happen with the phone even if the resulting automation later notifies or acts on the watch.
Why doesn't Apple just add NFC tag reading to Apple Watch?
Apple hasn't said, but developers have speculated it comes down to battery drain from running an active reader session on a small watch battery, plus limited internal space for a reader-capable antenna alongside the one already used for payments.
What's the practical workaround for wrist-based NFC automation today?
Read the tag with your phone and let the resulting action — a Shortcut, a smart-home trigger, a notification — reach your watch afterward. NFCore's iPhone app handles the read and write side; the watch just receives the outcome.