How NFC Tags Store and Share Data

Let’s be honest — we’ve all tapped our phone against a sticker on a coffee shop table to see the Wi-Fi password, or used our smartwatch to pay for groceries. That magic comes from NFC, which stands for Near Field Communication. But here’s the part that usually gets buried in technical jargon: how does a tiny plastic tag actually store data and then share it with your phone in a split second.

At PythonSkillset, we break down real tech into things you can actually use and understand. So today, we’re peeling back the sticker (literally) and looking at how NFC tags work under the hood.

The Tiny Chip Inside

An NFC tag looks like a sticker or a key fob, but inside it's a simple, passive microchip connected to a coil of wire — an antenna. That’s it. No battery. No power source. It’s so simple it feels almost like a cheat.

When your phone (or any NFC reader) gets within about 4 centimeters, it generates a magnetic field. That field induces a tiny electric current in the tag’s antenna, which powers up the chip. Think of it like charging a wireless toothbrush — but instead of charging a battery, it wakes up the chip just long enough to send back a short burst of data.

That’s why your phone has to be close. No power means no long range.

How Data Is Actually Stored

NFC tags don’t have a hard drive. They have something called EEPROM (Electrically Erasable Programmable Read-Only Memory). It’s a small, cheap chunk of memory that holds data even after the tag loses power. Most tags store between 48 bytes and about 1 kilobyte. That’s enough for a URL, a small text message, or a serial number.

Here’s the interesting part: you can write data to these tags yourself. Using a smartphone app (many are free), you can encode a tag with a link to your website, a phone number, or even a short command like “open this app.” Once written, the data stays put until you overwrite it. Some tags are read-only after writing, which makes them tamper-proof for security.

For example, at PythonSkillset, we often show readers how to write a tag that launches a specific Python script on their phone — just tap and go.

The Handshake: How Your Phone Reads It

So the tag has power and it has data. How does the data actually get into your phone? Through a protocol designed to be incredibly fast and secure.

When the tag powers up, it transmits its unique identifier (UID) — a serial number burned into the chip at the factory. Then, if the reader requests it, the tag sends back the stored data. The whole process takes about a tenth of a second.

Your phone’s NFC controller translates this into something the OS can understand. On Android, it triggers an “NFC intent” — a system event that your apps can react to. On iOS, Core NFC handles it. This is where you, as a developer, hook in. You write a listener that says, “When a tag is tapped, read this URL and open it in the browser.”

Security and the “Read Only” Trick

Because NFC tags are passive and short-range, they’re actually quite secure by design. A malicious reader would need to get within a few inches, which is hard to do without being noticed. But there’s an extra layer: you can lock a tag after writing.

You may have seen tags that are “NTAG” or “MIFARE” — different chip families. MIFARE tags, used in transit cards, have encryption built in. That means even if someone read the data floating through the air, they couldn’t decode it without the key stored in your phone.

That’s why NFC is used for payments. Your credit card data isn’t sitting on the tag in plain text. It’s encrypted and tied to a session token.

Real-World Example: A Simple Business Card

Let’s bring this home with something you can test yourself this afternoon. Buy a pack of writable NTAG215 stickers (about $10 for 10 online). Use an app like “NFC Tools” on your phone.

Write your LinkedIn profile URL to one tag. Write your phone number to another. Now tape the phone number tag to the back of your office badge and tap it against a colleague’s phone. In half a second, they see your number. No app. No typing.

That’s the entire lifecycle: your phone generates a field → tag powers up → tag sends back the number → your phone shows it. The tag itself never runs any code. It just holds a few bytes of memory.

The Limits You Should Know

NFC isn’t for streaming video or transferring large files. The speed is in the range of 106 to 424 kbps — fine for a URL, not for a photo. Also, the read range is intentionally short. That’s a security feature, not a bug.

But for quick, touch-to-connect interactions? There’s nothing more practical. And because tags are dirt cheap and last for years without a battery, they’re showing up everywhere — from museum exhibits that give you audio tours to inventory tags that let warehouse workers instantly know what’s in a box.

At PythonSkillset, we’ve been playing with these for automating small office workflows — like tapping a tag on your desk to start your daily VPN session. It’s not magic. It’s just a tiny chip, a coiled wire, and about a hundredth of a second of power.