A week ago I walked through how the NFC Tap Counter works: the chip counts its own scans, the app embeds placeholder bytes, and the tag substitutes the live count and tag ID into whatever it is carrying on every tap. That post stops where the tag does, which is at the moment the values arrive on your phone.

The question I have been getting since is the obvious next one: “great, the tag is handing me 049F50824F1390x000007 - now what?” If you are on iPhone and you want to act on those values inside a Shortcut, you have to parse them. That is a small but fiddly piece of string work, and I would rather you not have to write it yourself.

So I built two Shortcuts and I am sharing them as iCloud links. One is the brain. The other is a demo that uses the brain.

What the Tag Hands You

Before the shortcuts: a quick refresher on what they actually receive, because it matters for how you use them.

In the Tap Counter setup screen you pick a content type for the tag: URL, Email, SMS, or Shortcut. When you turn on the Tap Counter and / or Tag ID toggles, the app embeds placeholder bytes inside that content, and the chip swaps them for the live values on every read. Using 049F50824F1390 as the tag ID and 000007 as the count, the four content types end up looking like this:

• URL: https://nfc.cool/tap-counter/ becomes https://nfc.cool/tap-counter/?nfc=049F50824F1390x000007

• Email body: Hi, here's my card. becomes Hi, here's my card. 049F50824F1390x000007

• SMS body: Order confirmed! becomes Order confirmed! 049F50824F1390x000007

• Shortcut input: log-entry becomes log-entry 049F50824F1390x000007

That URL above is a real one. Our live tap counter test page is set up to read the ?nfc= value straight out of its own address bar, so if you want to see the substitution happen before writing your own automation, write a tag pointing at https://nfc.cool/tap-counter/ with both toggles on, tap it, and the page will show you the tag ID and the count it just received.

When the content type is Shortcut, NFC.cool runs the chosen shortcut through shortcuts://run-shortcut?name=Your%20Shortcut&input=text&text=<payload>, with the appended NFC values already in the text. Your shortcut’s input is a plain text string. Your only job is to pull the tag ID and the count back out of it.

Depending on which toggles were on when you wrote the tag, you may get the full pattern (14 hex characters, an x, then 6 hex characters), or just the 14-hex tag ID, or just the 6-hex count. The parser handles all three.

Parse NFC Tap Counter - the Reusable Parser

Install Parse NFC Tap Counter

This one is the brain. It does no UI, takes a single text input, and returns a Dictionary. That is deliberate: a utility shortcut with no UI composes cleanly inside anything else you build, and a Dictionary is the easiest thing to consume from another shortcut with the Get Dictionary Value action.

Here is what the Dictionary contains:

• tagID - the 14-character hex tag ID, or an empty string if the toggle was off.

• count - the scan count as a decimal number (so 000007 comes out as 7, and 00000A as 10), or empty if the toggle was off.

• countHex - the original 6-character hex count, in case you want to use it verbatim. Empty if absent.

• hasTagID, hasCount - booleans for branching, so you can write If hasCount is true without having to test the string yourself.

• content - the input with the NFC payload cleanly stripped off, so the rest of your shortcut sees the input the way it was before the tag dressed it up. If the input was a URL with ?nfc=..., you get the URL back without it. If it was an email body with the tag ID appended, you get the body back without it.

• raw - the unmodified original input, in case you want to log it or fall back to it.

To call it from your own shortcut, the recipe is three actions:

1. Receive Shortcut Input as text (the NFC payload arrives here).

2. Run Shortcut -> Parse NFC Tap Counter, with that text as input. Turn off “Show When Run” so it stays invisible.

3. Get Dictionary Value -> pick tagID, count, content, or whichever keys you care about.

That is it. From step 3 onwards you can do whatever you want with the values: branch on hasTagID, log count to a Note, fire a webhook with the JSON, anything. The parser does not assume what your shortcut wants to do with the result, which is exactly why it is small and reusable.

A note on the count: it is a real Number in the Dictionary, not a text string, so you can feed it straight into a Calculate or an If comparison without converting it again. The hex-to-decimal step is already done.

NFC Tag Alert - the Demo

Install NFC Tag Alert

This one is a demo I would still install on day one, even if you have no intention of using alerts in production. It takes a text Shortcut Input, runs the parser, and shows a single alert titled NFC Tag Scanned with two lines:

Tag ID: 049F50824F1390
Scans: 7

The reason I would install it first is that it is the fastest possible sanity check for a counter-enabled tag. Write a tag from NFC.cool Tools with content type Shortcut and name NFC Tag Alert, turn on the Tap Counter and Tag ID toggles, write it, tap it. An alert pops up with the real values from your physical tag.

If the alert shows the values you expected, your tag is doing its job and you can move on to building something more elaborate. If the count is wrong or the tag ID is missing, you know it is the tag (or the toggles you picked when writing it) and not your own shortcut. Eliminating one whole class of “is this even the chip’s fault?” debugging is worth installing a five-action shortcut for.

If you ever wonder how to call the parser correctly, this shortcut is also the smallest possible worked example. Open it, look at the five actions, copy the structure into your own shortcut.

Wiring It Into Your Own Shortcut

There are two ways tag content gets routed into your shortcut. The parser is happy with both.

Tag-driven (the Shortcut payload). Write the tag with content type Shortcut, pick your shortcut by name, turn on whichever toggles you want. From now on every tap launches your shortcut with the NFC payload already in the input. Inside your shortcut, call Parse NFC Tap Counter on that input and you have tagID / count ready to use.

URL-driven (the URL payload). This is the more common case. The tag carries a URL, your phone opens that URL on tap, and the count rides along as ?nfc=.... If you want a Shortcut to handle the tap instead of (or alongside) a browser, you can: route the URL through a Shortcut that handles a Safari web page input, then run Parse NFC Tap Counter on the URL. The parser strips the ?nfc= segment cleanly and gives you back the URL without it as content, so you can pass that on to a browser, an API call, or anywhere else that expects a plain URL.

Here is a four-action example for “log every scan to a note in Apple Notes”:

1. Receive Shortcut Input as text.

2. Run Shortcut -> Parse NFC Tap Counter, with the input as text.

3. Get Dictionary Value -> three lookups in a row for tagID, count, and content. Store each in a variable.

4. Append to Note -> a single line like [Current Date] tag=<tagID> count=<count> url=<content>.

You now have a running tap log written by the tag itself. No backend, no third-party analytics, no account anywhere.

A Few Ideas to Build On

A handful of small things the parser unlocks, written down so you do not have to invent them from scratch:

• Branch on the tag ID. One shortcut, many tags. Add an If action per known tag ID: if the office door tag was scanned, mute notifications; if the studio tag was scanned, set a focus mode; if the kitchen tag was scanned, start a timer. The tag ID identifies the physical tag, not the content, so you can give every tag the same URL and still react to each one individually.

• Pick a winner at scan N. Combine hasCount with a comparison. If count equals 100, fire a confirmation message; for every other scan, do the regular handling. The chip enforces order; your shortcut just reads it.

• Send to a webhook. Pair this with the NFC.cool Webhooks feature if you want server-side handling without writing an iOS app: post the parsed values as JSON, let the server take it from there. Two iOS actions and your tag is wired into anything that speaks HTTP.

• Log to a file or Note. The simplest one and surprisingly useful. Append timestamp, tagID, count to a running file in iCloud Drive or a single Note, and you have a tap log you can scroll through or graph from later. Good for engagement tracking on a single tag without standing up infrastructure.

If you build something neat with these, I would genuinely like to see it.

A Quick Thanks

Both of these shortcuts were built with Shortcuts Playground, Federico Viticci’s plugin for generating iOS Shortcuts from natural language. It is a great tool, and I want to thank him for shipping it - without it these two would have taken me a lot longer to put together.

A Quick Note for Android

Shortcuts is an Apple app, so these two only run on iPhone. The Tap Counter feature itself works on both platforms though, because the substitution happens inside the chip and does not care which phone is reading the tag. On Android, the URL, Email, and SMS payload types behave the same way they do on iOS; if you want similar automations there, apps like Tasker or MacroDroid can take a URL with ?nfc=... and pull the values out with their own string-handling actions. The format on the wire is the same.

Try It

If you want the deeper explanation of how the Tap Counter feature actually works under the hood, that is in the previous post. And if you want to see a counter-enabled tag in action without setting up your own automation first, our live tap counter demo page reads the ?nfc= value straight out of its own URL: write a tag that points there, tap it, watch the count and tag ID appear.

The NFC Tap Counter feature itself lives in NFC.cool Tools, on iPhone and Android. For the full set of tools I have built around NFC, take a look at the NFC reader and writer feature.

I build the Business Card app at NFC.cool, and over the last two years I’ve read a lot of emails from the people using it. They almost always open the same way: with their job. “I’m a realtor and…” “I’m a cardiologist and…” “I’m a freelance designer and…” Each person assumes their situation is unusual.

It mostly isn’t. But the reason a paper business card lets them down genuinely is different from one profession to the next. A real estate agent and a hospital physician both outgrow paper - for completely different reasons.

So instead of writing one more “paper cards are dead” article, I organized this the way people actually think about the problem: by profession. There are three sections - real estate, healthcare, and independent consulting - followed by the parts that apply to everyone, including an honest look at where my own app fits and where it doesn’t.

Why Paper Still Fails, Whatever You Do

Three things hold true before we get specific.

The first is waste. Adobe’s research - the most-cited number in this whole industry - found that roughly 88% of paper business cards are thrown out within a week. You pay to print them, you spend a moment of someone’s attention handing one over, and nine times in ten it produces nothing.

The second is staleness. A paper card is frozen the moment it leaves the printer. New title, new number, new address - the card in someone’s drawer still shows the old one.

The third is friction on the receiving end. A paper card has to be typed in to be useful, and most people never get around to it.

A digital business card fixes all three. It updates after you’ve handed it out. The person receiving it saves your details with one tap, no typing. And because it costs nothing per card, you stop rationing them.

That’s the shared story. Now the part that is actually different for you.

For Real Estate Agents

Real estate runs on staying reachable. Every open house, every broker’s open, every chance encounter at the coffee shop is a lead - and whether it becomes a client often comes down to one thing: did they keep your card? With paper, the honest answer is usually no.

The Open House Sign-In Sheet Is Broken

We’ve all seen the clipboard at the door. Visitors scribble half-legible names and emails, some skip it entirely, and on Monday you’re squinting at “jsmith@gmai…” trying to reconstruct a lead. A QR code on the property flyer replaces the clipboard: visitors scan it, get your full card, and you get a clean contact in return. Put an NFC tag on a small stand at the entry table for the same effect with a tap.

You Change Brokerages, Numbers, and Teams

Switched brokerages? New number? Added a team member? Every change means another print run - and weeks of handing out cards you know are already wrong. A digital card updates once, and everyone who saved it sees the new information immediately.

International Buyers Can’t Read an English-Only Card

Miami, Vancouver, London, Dubai - major markets attract international buyers, and an English-only card is useless to a Mandarin-speaking buyer or a Portuguese-speaking investor. A digital card in an app that supports multiple languages makes your information accessible regardless of what language your client reads.

The Follow-Up Window Closes Fast

A paper card creates exactly one touchpoint: the moment you hand it over. Miss the next few days and the lead is gone, because the card is buried or already in the trash. A digital card sits in the prospect’s phone, searchable, and some apps even show you when it was viewed - a natural prompt to reach out.

One note on credibility: the National Association of Realtors’ 2025 Technology Survey found 47% of buyers consider an agent’s technology skills “very important” when choosing who to work with. A card that opens cleanly on a phone, with your listings and virtual tours one tap away, is a small but real signal at a listing presentation. A practical habit: build a dedicated “open house” card with the property address and tour link, then switch back to your general card afterward.

For Healthcare Professionals

A cardiologist at a university hospital once told me she carries three business cards. Not by choice - one has her direct line, one has the cath lab’s scheduling number, one has the department fax for referral letters. She keeps them in separate coat pockets, because handing a patient the wrong one means a missed referral.

She is not unusual. Ask any physician in a hospital or multi-specialty practice: the contact information they need to share is rarely just their own.

You Need More Than One Number

A surgeon doesn’t just share a mobile number. They share the surgical scheduling desk, the ward clerk, the pathology lab, the referral fax. A paper card can’t hold that much information legibly, and when any one number changes, every printed card becomes garbage. A digital card holds all of it and updates in a single edit.

Hygiene Is Not Theoretical

Paper business cards are handled objects - passed hand to hand in waiting rooms, at conference booths, between doctors on rounds. A 2021 study at Hannover Medical School tested how long bacteria survive on hospital surfaces. S. aureus lasted at least seven days; A. baumannii and E. faecium, both on the WHO’s antibiotic-resistance priority lists, persisted for over four weeks. (Katzenberger et al., BMC Research Notes, 2021, DOI: 10.1186/s13104-021-05492-0.) Laminated cardstock is exactly that kind of surface. A tap-to-share card removes the handoff entirely.

Patients Expect Digital, and Expect It Current

A 2021 Redpoint Global survey of more than 1,000 U.S. consumers found that 80% prefer digital communication with healthcare providers, and 66% would choose a provider based on timely, consistent communication alone. (Redpoint Global / Dynata, December 2021, businesswire.com.) Their number-one frustration was outdated information - which a paper card guarantees the moment a practice moves or adds a telehealth line.

Referrals

This is the use case that surprises most doctors. When a GP refers a patient to a specialist, they need to pass on the specific scheduling line, the prep instructions, and the preferred contact method - not just a name. A referral-specific digital card carries all of that, and stays correct forever after a single share.

A word on privacy, because it matters more here: a business card is not a medical record. Put your name, credentials, specialty, department, phone numbers, practice address, and booking link on it. Never patient information, diagnosis codes, or insurance details. A good app lets you choose exactly which fields each card shows.

For Consultants and Freelancers

When you go independent, nobody orders your business cards for you. There’s no marketing department, no receptionist reprinting them when your title changes. You are the brand - and the card budget is your budget.

You Wear More Than One Hat

This is the one corporate employees never deal with. You might be a UX designer who also does brand photography, or a management consultant who also coaches executives. Paper forces one identity per card, or three stacks you fumble through at an event. A platform that supports multiple cards lets you keep one per role and share whichever fits the conversation.

Every Subscription Comes Out of Your Revenue

When a corporate employee gets business cards, the company pays. When you get them, you pay - and that changes the math. A platform charging $8-15/month for enterprise features you’ll never touch is money better spent on your actual business. Premium individual plans should be cheap, or there should be a real free tier.

Conferences and Coworking Run on Bad WiFi

You’ve had a great conversation, you want to swap details, and the conference WiFi is crawling. An NFC tap is near-instant - the tag carries a link, and a lightweight card profile loads quickly even on a spotty connection. In a coworking space, where a paper handoff feels heavy, a QR code on your laptop sticker is casual and non-intrusive.

The Follow-Up Is Where the Money Is

You met someone three weeks ago; they’re finally ready to talk. With paper, they’d have to find your card. With digital, they search your job title in their contacts and your website, portfolio, and booking link are right there. Less friction means more follow-ups, and more follow-ups means more clients.

One more thing, specific to independents: your card is brand collateral. Use your own colors and logo, write a benefit-oriented tagline instead of a bare title (“I help SaaS startups find product-market fit” beats “Strategy Consultant”), and give people a next step - a booking link, a portfolio, a lead magnet.

What to Look For in a Digital Business Card App

The professions differ; the checklist mostly doesn’t. Whatever you do, a digital business card app earns its place only if it gets these right:

• No app required for the recipient. This is the one that matters most. If the person you just met has to install something to see your details, you’ve added friction to the exact moment that should be frictionless.

• NFC and QR, both. NFC is faster and more impressive in person; QR is universal and works on a printed sign, a flyer, a slide. You want both, not one as a paid add-on.

• Multiple cards. Different roles, different events, different audiences. Non-negotiable if you wear more than one hat.

• Multiple languages, if you work across borders - the card content, not just the app’s interface.

• Privacy you can explain. Some platforms email the people who view your card, or record conversations. If your card provider spams your contacts, that reflects on you. Read the privacy policy before you commit.

• No hardware lock-in. Plenty of companies sell proprietary $30-$60 NFC cards. A $2 NFC sticker you program yourself does the same job.

• Honest pricing. Enterprise SSO and team dashboards are irrelevant when it’s just you. Look for a genuine free tier or an affordable individual plan.

How NFC.cool Business Card Fits

Full disclosure: this is my app, so read the next few paragraphs knowing that. I’ll try to be straight about where it’s strong and where it isn’t.

NFC.cool Business Card is a standalone app on iPhone, and the same features are bundled into NFC.cool Tools on Android. Here’s what it does well for the professions above:

• 35 languages in the app interface and the App Clip - more than any other digital business card I’m aware of. Your card displays in your client’s language on iOS. (The Android sharing website is English-only for now.)

• No app for the person receiving your card. On iPhone they get a native App Clip; on Android, a page on the nfc.cool domain. Both have a “Save Contact” button.

• NFC tap and QR code, plus a plain shareable link for chats and email signatures.

• Conference Mode - an iOS Live Activity that puts your card’s QR code on your lock screen. You raise your phone, they scan, done. No unlocking, no hunting through Apple Wallet. Wallet integration is there too, as an alternative.

• Up to 100 cards, so the “one card per role” advice above is actually practical.

• PIN-protected cards for anything sensitive.

• Privacy-first: no data monetization or advertising, no recipient solicitation, no conversation recording, GDPR-compliant data export.

• Any NFC tag works. I don’t sell hardware - write your card to a sticker you already own.

• Pricing: a free tier, then Personal at €20/year (1 card), Small Business at €50/year (10 cards), and Business at €100/year (100 cards).

Where competitors are genuinely ahead:

• CRM integrations. If your day runs on HubSpot or Salesforce, apps like Wave Connect or Blinq sync contacts natively. NFC.cool offers CSV export on iOS - no webhooks yet.

• Cross-platform analytics. Seeing who viewed your card, and when, is iOS-only for now; Android is coming. Some competitors have it on both today.

• Enterprise team management. If you’re a 50-person firm that needs an admin dashboard and directory sync, that isn’t what NFC.cool is built for.

The honest version: for an agent, a physician, or a soloist, what matters day to day is that sharing is fast, the card looks like you, and nothing embarrasses you later. That’s what I built it for. If you need a sales CRM welded to your business card, buy the tool that does that.

You can get NFC.cool Business Card on the App Store or on Android inside NFC.cool Tools.

Frequently Asked Questions

Does the person receiving my card need to install an app?

No. On iPhone they see a native App Clip; on Android, a web page on the nfc.cool domain. Both let them save your contact straight to their phone. This is true of most modern platforms - if one makes recipients download an app, skip it.

Which is better, NFC or QR?

Both, for different moments. NFC is a one-second tap and looks impressive face to face. QR works on any camera phone and on printed things - signs, flyers, slides, a sticker on your laptop. A good app gives you both.

Can I have different cards for different roles?

Yes, and you should. An open-house card with a property address, a referral card with a scheduling desk, a conference card with your talk details - all from one account, each updatable on its own.

Will it work with international clients?

NFC and QR work on phones worldwide. Whether the card itself adapts to another language depends on the app. NFC.cool Business Card supports 35 languages in the app and App Clip on iOS.

Can I see who viewed my card, and is that data safe?

Some apps show you views; some go further and market to the people who saw your card. That second behavior is a problem - your prospects should hear from you, not from your card vendor. NFC.cool offers analytics on iOS (Android coming) and never solicits recipients.

What does it actually cost?

A digital card is free or nearly free on most platforms. A physical NFC sticker is a $2-$30 one-time purchase and is reprogrammable. Compare that to $50-$150 per print run of paper cards that are outdated within months.

The Bottom Line

Paper business cards didn’t fail because they were paper. They failed because they freeze your information in a job that never holds still - and every profession’s information moves in its own way. An agent’s brokerage changes. A physician’s department numbers multiply. A consultant’s title shifts with every contract.

A digital card keeps up. Pick one that needs no app on the other end, supports NFC and QR, and treats your contacts’ data with respect - then stop thinking about business cards entirely. That’s the real win.

If you want to try mine, NFC.cool Business Card is free to start on iPhone and on Android inside NFC.cool Tools.

Say you print the same URL onto fifty NFC stickers and stick them on fifty products, fifty posters, or fifty business cards. A week later, someone asks the obvious question: which one actually got tapped? And how many times?

I’ve built NFC.cool for years now, and the usual answer I hear is a server. You generate fifty unique links, point them all at a backend, and let analytics software count the hits. It works, but now you are running infrastructure, paying for it, and trusting it to stay online for as long as those stickers exist. That always struck me as a lot of moving parts for a question this simple.

There is a simpler way, and it has been sitting inside the NFC chip the whole time. Many tags can count their own scans. With the right setup, a tag will tell you how many times it has been read and which physical tag it is, with no backend involved at all. This is one of my favorite NFC tricks to show people, so here is how it works, and how to set it up.

What an NFC Tap Counter Actually Is

Most NFC stickers you can buy use chips from the NTAG21x family - NTAG213, NTAG215, and NTAG216. Those chips have a small feature that I find most people never knew was there: a built-in counter. Every time the tag is read, the counter ticks up by one. It lives in the chip’s hardware, not in an app, and not on a server. (If you want the deeper breakdown of these chips, I covered them in NFC tag types for iPhone.)

The way I describe it is an odometer for the tag. A car’s odometer counts miles whether or not anyone is watching it; the NFC counter counts reads the same way. The number is always there. The only question is whether anything is set up to show it to you.

That is exactly what the NFC Tap Counter feature in NFC.cool Tools does, and it is the part I’m proudest of. It configures the tag once so that, from then on, the tag reports its own count. You do not need to scan the tag yourself to check the number, and you do not need the app present when other people tap it. The tag does the counting and the reporting on its own.

The same chips also carry a unique tag ID - a serial number burned in at the factory, a bit like a MAC address on a network card. The Tap Counter feature can surface that too, which is what lets you tell fifty identical-looking stickers apart.

How It Works, Without the Jargon

When you write content to a tag with Tap Counter turned on, the app does something I think is genuinely clever. It embeds a row of placeholder characters into whatever you are writing - a stand-in for the count and the ID. That part still feels a little like a magic trick to me, even after building it.

From then on, the chip handles the rest. As the help screen inside the app puts it: “The app embeds placeholder bytes in your content. On every scan, the chip replaces them with the current tap count (and/or tag ID) before the iPhone reads it. No server or internet needed.”

So the sequence on every tap looks like this. Someone holds their phone to the tag. The chip wakes up, bumps its counter, swaps the placeholders for the real numbers, and only then hands the finished content to the phone. The phone that scanned the tag never sees a placeholder - it sees a complete URL with a live count already baked in.

The thing I want you to take away is that you only do the setup once. After that first write, the tag is on its own: it will count and substitute for every tap, by every person, on every phone, for the life of the sticker. Nothing in that chain touches the internet. The counting happens in the chip. The substitution happens in the chip. If you point the finished URL at a website you control, your own server sees the count arrive - but that is your choice, not a requirement of the feature.

What You Can Actually Do With It

A self-counting tag sounds like a neat trick until you match it to a real problem. These are the four uses I keep coming back to when people ask me what it is for.

Tell which physical sticker was scanned. This is the fifty-stickers problem from the start of this post. Put the same URL on every tag, switch on the tag ID, and each tap arrives stamped with the serial number of the exact tag it came from. One URL to manage, fifty tags you can still tell apart.

Limit free access. Because the count travels with every tap, you can act on it. Run a promotion where the first hundred scans get the demo version and later scans get redirected somewhere else. A limited print run can hand out the full reward until the counter passes a threshold you picked. The tag enforces “first come, first served” without a signup system behind it.

Track engagement. Stick a tag on a business card, a poster, a product box, or a shop window, and the counter becomes a quiet engagement metric. You can see whether a card has been tapped twice or two hundred times without building an analytics pipeline for it.

Prove authenticity. The counter only ever goes up - it cannot be wound back. A number that can only increase is hard to fake convincingly, which is why I think it earns its place in limited-edition items and anti-counterfeit checks. A genuine tag has a plausible, climbing history; a cloned one does not. If that side of NFC interests you, I went further into it in how NFC keeps encrypted secrets safe.

Put a few of those together and you get something like this: a craft maker drops a tag into each numbered run of a product, all pointing at the same landing page. The tag ID tells them which item a buyer is holding, the count tells them how often that buyer has come back, and because the count only rises, a reseller cannot quietly pass a copy off as the original. No accounts, no database, no monthly bill - just the chip doing its job. That is the kind of result I built this feature for.

Setting It Up, Step by Step

The feature lives in NFC.cool Tools, on both iPhone and Android. It is part of the Pro (Platinum) subscription, so you will need that to write counter-enabled tags. If you have never written a tag before, my walkthrough on how to write NFC tags on iPhone covers the basics first.

1. Open NFC.cool Tools, go to the NFC Tools section, and tap NFC Tap Counter.

2. Pick what the tag should deliver: a URL, an Email, an SMS, or a Shortcut. (Shortcut is iOS only, since Shortcuts is an Apple app; URL, Email, and SMS work on both platforms.)

3. Compose that content the way you normally would - type the link, write the message, choose the shortcut.

4. Turn on the toggles you want: NFC Tap Counter adds the live count, and NFC Tag ID adds the tag’s serial number. You can use either, or both.

5. If you are programming a batch of tags with the same content, switch on Batch write so the scanner stays open and you can write one tag after another.

6. Check the Preview. It shows example output with stand-in values, so you can see exactly where the count and ID will land before you commit.

7. Tap Write to NFC Tag and hold a tag to the top of your phone.

That is the whole setup, and I deliberately kept it that short. From that point the tag is self-sufficient - it counts and reports on its own, for every person who taps it, with or without the app.

If you ever want to stop it, the app can turn the counter off on an existing tag. The chip stops swapping in live values, but the content stays on the tag exactly as it was last written. One detail worth knowing: the chip keeps counting internally even after you switch the substitution off - the count is never lost, it just stops being shown.

Where the Count and Tag ID Show Up

Where the values land depends on the content type you chose. With both toggles on, the tag ID and the count are inserted together - the ID first, then the count, joined by a small x. Using 049F50824F1390 as the tag ID and 000007 as the count, here is the before and after for each type:

• URL: https://example.com/page becomes https://example.com/page?nfc=049F50824F1390x000007

• Email body: Hi, here's my card. becomes Hi, here's my card. 049F50824F1390x000007

• SMS body: Order confirmed! becomes Order confirmed! 049F50824F1390x000007

• Shortcut input: log-entry becomes log-entry 049F50824F1390x000007

The values are appended cleanly, so the rest of your content keeps working as normal. Switch one toggle off and you simply get the other on its own: just the count (000007) or just the tag ID (049F50824F1390).

Now, the question I always get here: why 000007 and not just 7? The count is written in hexadecimal - the base-16 number system that runs 0 through 9 and then A through F - and padded out to six characters. So 000007 is simply the tag’s seventh scan. Once you pass scan nine you start seeing letters: 00000A is 10. The ceiling is FFFFFF, which is roughly 16 million scans, more headroom than almost any real-world tag will ever need. The tag ID is a longer hex string - the chip’s 7-byte factory serial number - and unlike the count it never changes.

If you are routing the finished URL to your own website, your server reads those values straight out of the address: log the count, compare it to a threshold, or tell one tag from another by its ID.

Which Tags You Need

This feature depends on the chip, so the tag matters. NFC.cool supports NTAG213, NTAG215, and NTAG216 chips for Tap Counter. Those are the most common NFC stickers sold for phones, so they are easy to find, but I would still check the chip type before you buy in bulk. If you try to use a tag the feature does not support, the app warns you rather than writing something that will not work - I made sure of that because I have seen how frustrating a silent failure is.

If you need to stock up, our recommended NFC tags page lists the NTAG216 stickers we use and test against. And if you are new to choosing tags, my guide to the different types of NFC tags for iPhones walks through the trade-offs in plain terms.

A Few Quick Questions

Can I reset the counter? No. It is a one-way counter built into the chip and it can only go up. That is deliberate, and honestly the whole point - a counter you could reset would be useless for limited editions or anti-counterfeit checks. If you need a fresh count, use a new tag.

Can anyone read the count, or just me? Anyone. Every phone that taps the tag gets the finished content with the count already in it, with or without the app installed. That is the point - the tag reports for itself.

Can I turn it off later? Yes. The app can stop the chip from substituting placeholders. The URL or message stays on the tag; only the live updates stop. The chip keeps counting internally.

Is the counter private? The count lives on the tag, not on a server. Anyone who taps the tag sees the count in the content, and if that content points to a server you control, only that server sees it. The tag ID is a factory serial number, not personally identifying information.

Does it need internet? No. The counting and the substitution both happen inside the chip. Internet only enters the picture if the URL you wrote happens to point at a website.

Try It

For most of the years I’ve worked with NFC, counting taps meant unique links and a backend to tally them. The NTAG21x counter quietly removes that requirement: the tag keeps its own tally, and the NFC Tap Counter feature in NFC.cool Tools is what switches it on. It is one of those features I keep wishing more people knew was even possible.

Want to see it work before writing a single tag? Our live tap counter demo is a page that does exactly what this post describes - write a tag that points at it, give it a tap, and the page shows you the scan count and tag ID the chip just handed it. No server in the loop, just the URL.

It is available now in NFC.cool Tools, on iPhone and Android. To see the full NFC toolkit I’ve built, take a look at the NFC reader and writer feature.

Your seed phrase is probably on a piece of paper. Maybe it’s in a safe. Maybe under a floorboard. Maybe split across three locations because someone on Reddit said that’s what “serious” crypto people do. But it’s still paper. Paper burns. Paper floods. Paper gets lost.

I’ve spent years building NFC.cool, an app for reading and writing NFC tags, and at some point I started asking myself a question that has nothing to do with payments or keycards: what if your backup couldn’t rot, couldn’t degrade, and looked like nothing to anyone who found it?

That question is why I built NFC Safe. It encrypts any text - seed phrases, passwords, recovery codes, whatever you need to keep secret - onto an NFC tag with 256-bit AES encryption. The tag is self-contained. No cloud. No server. No account. To read the secret, you need the physical tag and the passphrase. Without both, the tag is just a tiny piece of plastic with some gibberish on it.

One thing I felt strongly about while designing this: I didn’t want your secrets to depend on my app existing. So the encryption format is fully documented and open, including a reference Python decoder. If NFC.cool ever disappears, you can still recover your data with a standard NFC reader and the spec. That’s a promise I can keep because I wrote the spec to outlive the software.

The problem with storing secrets

If you asked me to name the weak point in every secret-storage method I’ve seen, I could do it without thinking: paper burns, USB connectors corrode, cloud services get breached, hardware wallets only handle crypto seed phrases, and your brain forgets. Every option fails in its own way.

So I worked backwards. The ideal backup would be physically durable, encrypted, self-contained, redundant, and long-lasting. NFC tags hit all five, and that surprised me at first too. They have no battery, no moving parts, and the NTAG216 chip is rated for 10+ years of data retention. Epoxy-coated variants survive water, impact, and decades of neglect. If you’re new to how these chips differ, I broke down the trade-offs in NFC tag types for iPhone.

How to use NFC Safe

NFC Safe lives inside NFC.cool Tools under NFC Apps. I kept the whole thing down to one screen with a segmented control at the top - Encrypt or Decrypt. If you’ve ever written a tag before, none of this will feel unfamiliar.

To encrypt:

1. Open Tools → NFC Apps → NFC Safe

2. Select Encrypt

3. Type or paste your secret

4. Set a strong passphrase

5. Tap Encrypt; hold an NFC tag to your phone

To decrypt:

1. Same screen, switch to Decrypt

2. Enter your passphrase

3. Tap a previously-encrypted tag - your secret appears

Under the hood, here’s what I’m actually doing: AES-256-GCM with PBKDF2 (HMAC-SHA-256, 100,000 iterations, 16-byte random salt). The result is stored on the tag as a custom NDEF record (urn:nfc:ext:crypto). If you want to verify any of that yourself rather than take my word for it, the full format spec is on GitHub. If you’re curious what a normal, unencrypted tag write looks like first, I walk through that in how to write NFC tags on iPhone.

The redundancy strategy

Here’s how I’d actually use this myself. An NTAG216 tag costs about as much as a coffee, so there’s no reason to make just one. Buy a handful, encrypt the same secret to each, and distribute them: desk drawer, office, a family member’s house, a safety deposit box, somewhere only you’d think to look. Each tag on its own is meaningless without the passphrase. That’s the part I like most about the design - it’s two-factor by nature: a physical tag plus a passphrase, held in two separate places, with no extra setup from you.

Why NFC instead of USB or SD card

People ask me why I didn’t just point everyone at a USB stick or an SD card. The honest answer is that I’ve watched too many of those fail in boring, preventable ways. NFC sidesteps all of them:

• No connector - nothing to corrode or bend

• No battery - passive, powered by the reader

• No filesystem - nothing to corrupt

• No driver - every smartphone reads NFC natively

• Small and cheap - coin-sized, under a dollar in quantity

• Durable - epoxy variants handle water, impact, UV

The one real limit is capacity: roughly 500-700 bytes after encryption overhead. That’s not much, but it’s plenty for what this is actually for - a 24-word seed phrase, a master password, or a set of recovery codes.

Security notes

I’d rather be upfront about the sharp edges than have you discover them later:

• Your passphrase is everything. 256-bit AES is unbreakable. A weak passphrase isn’t. Use a randomly-generated 20+ character string and don’t compromise here.

• NFC range is short (~4 cm). Nobody scans from across the room - that tiny range is a feature, not a bug.

• No remote wipe. Lost tag? Destroy it physically. Scissors work, and so does the fact that the data is useless without the passphrase anyway.

• No passphrase recovery. Forget it and the data is gone. I made that decision deliberately - a recovery path is also an attack path. Write the passphrase down somewhere separate from the tags.

The bigger picture

Working on NFC every day, I’ve watched these tags quietly become the storage medium for things that matter. The EU Digital Product Passport will require NFC for product authenticity. Philips puts them in toothbrush heads. Hotels use them for room keys. Cheap, durable, and universally readable by the device already in your pocket - that combination is rare, and it’s exactly why I keep finding new uses for them. If you want the broader view, I covered the basics in NFC tags explained: a complete beginner’s guide.

NFC Safe is my attempt to take that durability and add the one thing it was missing - encryption. A backup that outlasts paper, can’t be read by anyone who finds it, and costs less than a cup of coffee. That’s the kind of thing I wanted for myself, so I built it.

Available now on NFC.cool Tools for iPhone and Android.

Your iPhone is the scanner. Your Mac is the browser.

Starting today, the NFC.cool iOS and iPadOS app is compatible with Mac - meaning you can install it directly from the App Store on your Mac, just like any other app designed for iPhone and iPad.

No separate Mac app. No subscription upgrade. Same app, one more screen.

The Sidebar - Built for Bigger Screens

NFC.cool has always been a mobile-first app. You hold your phone, scan a tag, see the result. That works great on iPhone.

But on iPad and Mac, a single-column phone layout wastes a lot of space. So I added a sidebar navigation - designed specifically for the bigger screen.

The sidebar gives you quick access to all your content categories:

• NFC tags you’ve scanned

• QR codes & Barcodes you’ve captured

• Documents you’ve scanned

• 3D models & Rooms you’ve scanned

Everything is one tap (or click) away. The sidebar also adapts to iPad - same experience, same efficiency, whether you’re holding it or it’s on your desk.

iCloud Sync - What You Scan on iPhone, You See on Mac

This is where it gets useful.

Every scan you’ve done on your iPhone - NFC tags, QR codes, barcodes, documents, 3D models, room scans - syncs to your Mac automatically through iCloud.

Open the app on your Mac, and your entire library is already there. No export, no manual transfer, no “send to Mac” button. It just appears.

This means you can:

• Scan on the go with your iPhone

• Review and organize on your Mac with the bigger screen

• Reference a tag or document while working on your Mac - without reaching for your phone

Your data follows you across devices because it lives in your iCloud account. Same privacy approach as always: your scans stay on your devices and in your iCloud. I never see them.

Bonus: Your Mac Camera Is a QR & Barcode Scanner

Here’s a fun one - your Mac’s built-in camera works as a QR code and barcode scanner.

Hold a QR code up to your Mac’s camera, and NFC.cool reads it. Same for barcodes. No iPhone needed for these.

Useful for quickly looking up a product barcode while you’re working, or scanning a QR code from a screen without pulling out your phone.

What Doesn’t Work on Mac (And Why)

I believe in being upfront about limitations, not hiding them.

NFC scanning doesn’t work on Mac - Macs don’t have NFC radio hardware. You need your iPhone for that.

Document scanning doesn’t work either - the Mac camera doesn’t have the auto-focus and edge-detection pipeline that makes document scanning work on iPhone and iPad.

3D scanning and room scans need the LiDAR sensor (iPhone Pro / iPad Pro) - no Mac has one.

These aren’t software limitations I can fix. They’re hardware constraints. The Mac simply doesn’t have the sensors.

But here’s the thing: you probably don’t need them on your Mac. You scan with your iPhone because it’s in your hand. You browse and reference on your Mac because it has the big screen and keyboard. The Mac app is built for that workflow.

Same App, More Screens

The Mac app isn’t a separate product. It’s the same NFC.cool app you already know, now compatible with one more device.

If you already have NFC.cool on your iPhone or iPad, it’s waiting for you in the Mac App Store - same subscription, same account, same library.

Download NFC.cool Tools for iPhone, iPad, and Mac

Android user? NFC.cool for Android has you covered too.

Your electric toothbrush is spying on you.

Not in a creepy surveillance way. In a “we put a tiny NFC chip in your brush head to nag you into buying replacements” way. Every Philips Sonicare replacement head has an NTAG213 embedded in the plastic that tracks how long you’ve been brushing and tells the handle to flash a warning light when it decides your three months are up.

Welcome to the Internet of Shit.

The thing is, three months is a recommendation, not a medical fact. Bristle wear depends on how hard you brush, what toothpaste you use, and how often. The chip doesn’t measure bristle condition. It just counts seconds. A gentle brusher with soft toothpaste might have perfectly fine bristles at three months. The timer doesn’t know or care.

NFC.cool Tools can now read that chip, show you exactly how much life your brush head has used, and reset the timer if you decide your bristles are still good. Here’s how it works.

What’s Actually on the Chip

I didn’t reverse-engineer any of this myself. Cyrill Künzi tore down the protocol and mbirth mapped every byte, and between them they worked out everything below. Here’s what the NTAG213 in your brush head stores:

• Brush head type and color - a single byte at page 0x1F that identifies the model (Premium All-in-One, Gum Care, DiamondClean, etc.) and its color (mbirth’s memory map lists 22 known types)

• Target lifetime - at 0x21, usually 0x5460 = 21,600 seconds, which is 180 two-minute brushing sessions, or three months of twice-daily use

• Manufacturing code - at 0x21-0x23, the production date and line as ASCII, like 241206 31K (manufactured December 6, 2024, on line 31K). Also printed on the stem

• Accumulated brush time - the first two bytes at page 0x24 store the total seconds the head has been in use as a 16-bit value. When it reaches 0xFFFF (65,535 seconds, about 18 hours of continuous brushing), the counter stops. A brand-new head starts at 00:00:02:00 - the first two bytes are zero (no usage), the meaning of the last two bytes is currently unknown

• Last intensity and mode - at 0x24 as well: Low/Med/High and Clean/White+/Gum Health/Deep Clean+

• A URL - pointing to philips.com/nfcbrushheadtap, which opens if you tap the head with a generic NFC reader

When the accumulated time exceeds the target (21,600 seconds), the handle blinks its amber LED. That’s the chip talking, not the bristles.

Why You Might Want to Reset It

The three-month replacement interval is a Philips recommendation, not a scientific measurement of bristle wear. The chip counts seconds, not bristle fraying. If you want to decide for yourself - by looking at your bristles instead of obeying a countdown timer - resetting the counter lets you do that.

You might also reset if you rotate between multiple heads (travel vs. home) and want to track them yourself.

How the Password Works

The NTAG213 is password-protected. Every brush head has a unique 4-byte password. The toothbrush handle authenticates with it every time it writes to the tag.

The password is computed from two inputs: the tag’s 7-byte UID and the manufacturing code stored on the tag (and printed on the stem). Aaron Christophel reverse-engineered the algorithm from the Sonicare firmware after Cyrill Künzi originally sniffed the password transmission using a software-defined radio.

⚠️Important: The NTAG213 permanently locks after three failed password attempts. The chip becomes read-only forever - not even the toothbrush can write to it anymore. Don’t guess.

How to Check and Reset with NFC.cool Tools

Here’s how it looks in the app:

NFC.cool Tools handles the whole process: reading the tag, computing the password, and showing you the stats. No hex commands, no web calculators, no SDR.

1. Open NFC.cool Tools on your iPhone

2. Go to Toothbrush Head Reset

3. Tap Read NFC and hold the brush head against your phone

4. The app shows a percentage gauge of how much life the head has used, with used and remaining time below

5. Tap Reset Timer to set the usage counter back to zero, or scan another head

Available now on iPhone and Android.

What the Reset Actually Does

When you reset, you’re writing 00:00:02:00 to page 0x24 - the same value a brand-new brush head ships with. Only the first two bytes (the usage counter) are changed back to zero. The meaning of the last two bytes is unknown, so the app preserves them.

The toothbrush starts counting from zero again, and the amber light comes back after another three months. At which point you can check your bristles and decide for yourself.

The Bigger Picture: NFC in Everyday Objects

A toothbrush head with an NFC chip that counts down to your next purchase is peak Internet of Shit. I’ve built my work around NFC because I think it’s genuinely useful, but embedding it in disposable plastic specifically to nudge you toward buying more is… a choice.

The same NTAG213 chip is also used for things that actually serve the consumer: product authentication, access control, and soon the EU Digital Product Passport, which will require NFC tags on consumer products so you can verify what you’re buying and where it came from. That’s NFC being used for you, not against you.

NFC.cool Tools reads and writes all of these. The Sonicare feature is one example of understanding what’s on the tags around you, and deciding what to do with that information.

Further Reading

• Cyrill Künzi’s original reverse engineering writeup - SDR sniffing, password extraction, and the first detailed analysis of the Sonicare NFC protocol

• Aaron Christophel’s password generator - the algorithm extracted from the Sonicare firmware

• mbirth’s NTAG213 memory map - detailed documentation of every byte on the chip

Have a Sonicare brush head to check? Download NFC.cool Tools for iPhone or Android and see what your toothbrush has been tracking.

I’ve been building NFC apps for years. And every single week - without fail - someone emails me some version of this:

“Hey, I bought an NFC business card. Programmed my vCard on it. Works great on my friend’s Android. But when I tap it to my iPhone? Nothing happens. Is my card broken?”

Your card isn’t broken.

Your iPhone just doesn’t support vCard on NFC tags. And it probably never will.

Let me explain why - and what actually works instead.

Why vCard NFC Tags Don’t Work on iPhone

Here’s what happens when you tap an NFC tag with vCard data:

On Android: The Contacts app opens. You see the contact info. Tap save. Done. Beautiful.

On iPhone: Nothing. Literally nothing happens. No popup. No error message. Just your iPhone sitting there, silently ignoring you.

The first time I saw this happen at a conference, the person tapping looked at me like I was broken.

Why does this happen?

According to Apple’s developer documentation, background NFC tag reading on iPhone only supports specific data types:

• ✓ Web URLs (http:// and https://)

• ✓ Phone numbers (tel:)

• ✓ SMS links (sms:)

• ✗ vCard contact files - not supported

When your iPhone detects an NFC tag with vCard data, it simply ignores it. No fallback. No helpful error. Just nothing.

Android handles vCards natively because Google decided that made sense. Apple decided URLs were enough.

I don’t make the rules. I just build around them.

But Wait - Can’t an App Read vCards on iPhone?

Technically, yes. If you install an NFC reader app like NFC.cool Tools on iPhone or NFC.cool Tools on Android, it can read the raw tag data - including vCard records - and display the contact info. On Android, NFC.cool Tools does this automatically when it detects a vCard on a tag.

But here’s the problem: the person scanning your card needs to already have the app installed.

At a networking event, that means: “Hey, before you scan my card, can you go to the App Store, search for an NFC app, download it, wait for install, open it, grant NFC permissions, and then scan?”

They’ve already walked away. The magic is gone.

The whole point of NFC is tap and done. The moment you add extra steps, you’ve lost.

NFC.cool Tools is great for reading and writing NFC tags - I built it for exactly that. But for sharing your contact info with strangers, you need something that works without any app on their end.

The Solution: URL-Based NFC Business Cards

Here’s the thing nobody tells you when you buy an NFC business card:

You shouldn’t store contact data on the tag at all.

Instead, store a URL that points to a digital profile.

That’s exactly what NFC.cool Business Card does. Instead of cramming vCard data onto the tag (where iPhones ignore it), we store a smart link to your digital profile.

When someone taps your card:

• iPhone → Link opens → Beautiful profile loads → One-tap save contact

• Android → Same experience → Works perfectly

• Any smartphone → Universal compatibility

No app required for the person receiving your card. No tutorials. No friction.

Tap. Profile. Save. Done.

Why a Digital Profile Is Better Than vCard

When I first built this solution, I thought it was just a workaround for Apple’s limitations.

Then I realized: this approach is genuinely better than vCards ever were.

What a vCard gives you: Name. Phone number. Email. Maybe a job title. That’s it. Static data from 2005.

What a URL-based digital profile gives you:

▸ All Your Links in One Place LinkedIn, Twitter, Instagram, your portfolio, your Calendly booking link - all accessible from one tap.

▸ Smart Networking Features You know how you meet someone, save their contact, and two weeks later you’re staring at “John - Conference” with zero memory of who John is?

NFC.cool lets you capture the context: where you met, what you discussed, follow-up notes. It’s like a CRM that doesn’t cost $50/month.

▸ Apple Wallet Integration Your digital business card lives in Apple Wallet. Left your physical NFC card at home? Just show your phone.

▸ Update Anytime Changed jobs? New phone number? Update your profile once - everyone who has your link sees the new info instantly. No reprinting cards. No reprogramming tags.

vCards can’t do any of this. They’re frozen in time the moment you write them.

▸ Works on Every Phone Unlike vCard, a URL-based profile works on every smartphone - iPhone, Android, even older devices with just a browser. The NFC.cool Business Card app on iOS uses an App Clip so recipients don’t even need to install anything. On Android, NFC.cool Business Card (inside NFC.cool Tools) opens a web profile instantly.

FAQ

Will Apple ever support vCard on NFC tags?

It’s been years and Apple hasn’t changed this behavior. Background NFC reading has remained limited to URLs, phone numbers, and SMS links since the iPhone XS. I wouldn’t count on it changing.

Does this affect all iPhones?

Yes. Every iPhone with background NFC reading (iPhone XS and newer, running iOS 13+) ignores vCard data on NFC tags.

Can I read vCard NFC tags on iPhone at all?

Only with an NFC reader app installed. NFC.cool Tools on iPhone and NFC.cool Tools on Android can both read and display vCard data from NFC tags. Android does this natively without an app; iPhone requires one. But for business card sharing, the better path is NFC.cool Business Card - no app needed on the receiving end.

What NFC tags work best for digital business cards?

Any NTAG213 or NTAG215 tag works great. The data stored is just a URL, so you don’t need much memory.

Can I write NFC tags with my iPhone?

Yes - NFC.cool Tools lets you write URLs and other data to NFC tags directly on iPhone. It supports all common NDEF record types and works with any NTAG tag.

The Bottom Line

If your NFC business card uses vCard data, it’s invisible to half your audience. iPhones won’t read it without an app - and you can’t ask every new contact to install one.

The solution isn’t a workaround - it’s a fundamentally better approach:

1. Store a URL instead of contact data

2. Point that URL to a rich digital profile

3. Let the profile handle contact saving, link sharing, and everything else

That’s what NFC.cool Business Card does. It’s what I use at every conference, meetup, and networking event.

I tap. They save. We both move on with our lives.

That’s how it should work.

NFC.cool Business Card is available on the App Store and Android (inside NFC.cool Tools). NFC.cool Tools (tag reader and writer) is available on the App Store and Google Play.

You tap your NFC card against someone’s phone, or they scan your QR code. What happens next determines whether they actually save your contact or just walk away.

The best digital business card in the world is useless if the person on the other end has a bad experience. And yet, most of the conversation around digital business cards focuses on the sender: how many fields can I add? How do I customize my card? What CRM does it integrate with?

The question that actually matters is different: what does the person receiving your card experience?

The Recipient Experience Problem

When someone receives your digital business card, you’re asking them to do something right there and then, usually at a conference, a meeting, or a networking event. They’re busy. They have three seconds of attention.

In those three seconds, any friction kills the interaction:

• A loading screen that takes too long

• A page asking them to create an account

• A prompt to download an app they’ll never use again

• A web page cluttered with ads or promotions for the card platform itself

The recipient didn’t choose your business card app. They didn’t research it. They just tapped or scanned because you asked them to. The experience needs to be instant, clean, and obvious.

How NFC.cool Handles This

NFC.cool Business Card takes two different approaches depending on the recipient’s platform, both designed to work without any download.

On iPhone: A Native App Clip

When an iPhone user taps your NFC card or scans your QR code, iOS launches an App Clip: a lightweight, native experience built specifically for moments like this.

An App Clip isn’t a web page pretending to be an app. It’s actual native iOS code, compiled in Swift, running on the device. For iOS users, this feels completely natural. It behaves exactly like an app they already have installed, with smooth animations, native UI components, and the responsiveness they expect.

Here’s what happens:

1. Tap or scan: recipient holds their iPhone near your NFC card, or scans your QR code

2. Instant load: the App Clip appears in under two seconds, no App Store visit

3. Full profile: your name, photo, company, phone, email, social media links, and website

4. One-tap save: a “Save Contact” button sits at the bottom of the screen, right where the thumb naturally rests. One tap saves everything to their Contacts app

5. Their language: the App Clip supports 35 languages and automatically matches the recipient’s device language. Hand your card to someone in Tokyo, São Paulo, or Berlin, and they see it in their own language

No account creation. No sign-up prompts. No ads. No tracking URLs. Just your contact info, saved in seconds.

After saving, the recipient sees a gentle invitation to create their own NFC.cool business card. That’s it, no aggressive push, no forced sign-up.

On Android: An Instant Web Profile

Android recipients get a clean web profile hosted on nfc.cool. Tap the NFC card or scan the QR code, and the profile opens directly in their browser.

Same information (name, photo, social links, contact details) with a one-tap save option. No app download, no account required. It works on any Android phone with a browser.

Why the Native Experience Matters

Most digital business card services use some form of web view or web page for recipients, and that works fine in many cases. But there’s a meaningful difference between a web page and a native App Clip, especially on iOS.

Speed: App Clips are cached by iOS after the first load. If someone taps your card a second time (at a follow-up meeting, for example), the experience loads even faster.

Trust: iOS users are accustomed to native experiences. An App Clip looks and feels like something Apple built into the system. There’s no browser chrome, no URL bar, no cookie consent popups, just your card.

Reliability: Native code handles contact saving through iOS’s own frameworks, which means the save action works consistently. No browser quirks, no “did it actually save?” uncertainty.

Localization: A web page can be translated, but a native App Clip localizes everything (UI labels, button text, date formats, contact field ordering) the way iOS users expect. NFC.cool supports 35 languages natively, so the recipient experience is localized whether they speak English, Japanese, Portuguese, or Arabic.

What the Recipient Doesn’t See

What makes a recipient experience truly good isn’t just what’s there, it’s what isn’t.

When someone receives your NFC.cool business card:

• No ads: the profile page doesn’t promote NFC.cool or show third-party ads

• No tracking redirects: your links are your actual links, not wrapped in analytics URLs

• No solicitation: the recipient doesn’t get follow-up emails from NFC.cool asking them to sign up

• No data harvesting: recipient information isn’t used for marketing

This matters more than most people realize. Your business card is often someone’s first impression of you. If tapping your card leads to a cluttered page with banner ads or sends the recipient spam emails the next day, that reflects on you, not just the app.

Conference Mode: Sharing from Your Lock Screen

At conferences and events, you’re sharing your card dozens of times. NFC.cool has a feature called Conference Mode that uses iOS Live Activities to put a QR code directly on your lock screen.

No need to unlock your phone, open the app, or navigate to your card. Just show your lock screen, the other person scans the QR code, and the App Clip does the rest.

It’s a small thing, but at a busy event where you’re holding a coffee in one hand and shaking hands with the other, it makes a real difference.

Getting Started

As the card owner:

• Download NFC.cool Business Card (App Store / Google Play)

• Create your card with your details, photo, and social links

• Share via NFC tag, QR code, or direct link

As the recipient:

• Nothing. That’s the whole point.

NFC.cool Business Card is available on iOS and Android. App Clip functionality is an iOS feature; Android recipients receive an instant web profile instead.

If you 3D print, you’ve probably been there: a shelf full of half-used spools, no idea how much filament is left on any of them, and that one unlabeled spool that might be PETG or might be PLA, with no way to tell without a test print. I’ve been there too, and it’s the kind of small, recurring annoyance that NFC is genuinely good at solving.

That’s what OpenPrintTag does. It’s an open-source NFC standard created by Prusa Research that turns any compatible NFC tag into a smart label for your filament spool. Material type, brand, color, remaining weight: all stored directly on the spool and readable with a quick tap of your phone.

No cloud. No proprietary ecosystem. No internet required. I’ve spent years building NFC.cool, an app for reading and writing NFC tags, and this is exactly the kind of standard I like to see - one that puts the data on the tag and lets it work anywhere. Here’s how it works, and how I read and write OpenPrintTag spools with nothing but a phone.

What Is OpenPrintTag?

OpenPrintTag is a universal, open data format for 3D printing materials. Instead of every manufacturer inventing their own incompatible smart spool system - which is exactly the mess I’ve watched play out in other corners of the NFC world - OpenPrintTag defines a single standard that anyone can adopt, including filament makers, printer manufacturers, slicer software, and apps like NFC.cool.

The key principles, and the reasons I think it’s worth paying attention to:

• Open source: published under MIT license, free to implement, no licensing fees

• Offline by design: all data lives on the tag itself, no cloud service needed

• Rewritable: update remaining filament as you print, reuse tags on new spools

• Universal: works across brands and ecosystems

• Supports both FFF (filament) and SLA (resin)

Over 22 companies and groups have expressed interest, including Prusament, Voron, Fillamentum, 3DXTech, SimplyPrint, and PrintedSolid. The full specification is available at specs.openprinttag.org.

What Data Does an OpenPrintTag Store?

This is the part that won me over. OpenPrintTag isn’t just a label with a name on it. It’s a properly structured data format with fields for almost everything you’d want to know about a spool, and the spec has clearly been written by people who actually print.

Material identification:

• Material class (filament or resin)

• Material type (PLA, PETG, ABS, TPU, ASA, PC, PA6, and 30+ others)

• Material name (e.g. “PLA Galaxy Black”)

• Brand name (e.g. “Prusament”)

• Material property tags: over 68 defined properties like abrasive, conductive, glow-in-dark, food-safe, ESD-safe, flexible, and more

Weight and length tracking:

• Nominal weight (advertised, e.g. 1000g)

• Actual weight (measured for this specific spool)

• Filament length (nominal and actual, in mm)

• Empty container weight (so you can weigh the spool and calculate remaining material)

• Consumed weight (updated as you print; this is the field that makes spools truly “smart”)

Color:

• Primary color in RGBA format

• Up to 5 secondary colors (for multicolor, galaxy, or gradient filaments)

• Transmission distance (opacity value, useful for HueForge projects)

Metadata:

• Manufacturing date and expiration date

• Country of origin

• UUIDs for brand, material, and specific spool instance

• Write protection settings

The spec even covers resin-specific fields like last_stir_time, which records when the resin was last stirred before printing. That’s the kind of detail that tells me the people behind it have actually been burned by un-stirred resin.

The Tag: Not Your Usual NFC Sticker

Here’s a technical detail I’d flag before you buy anything: OpenPrintTag is designed for ISO 15693 (NFC-V) tags, specifically NXP ICODE SLIX and ICODE SLIX2 chips. These are NFC Forum Type 5 tags with a significantly longer read range than standard NFC-A tags, up to 1.5 meters with a dedicated reader. If you’ve only ever bought the cheap NTAG stickers most projects use, this is a different family of tag - I cover the full landscape in NFC tag types for iPhone.

Why NFC-V? A printer’s built-in NFC reader needs to detect the spool regardless of its rotation. The longer range of NFC-V makes this possible without requiring precise tag alignment, which is a smart bit of design.

What about regular NTAG stickers? The OpenPrintTag data format is NDEF-based, so a phone app like NFC.cool can technically read and write OpenPrintTag data on any NFC tag, including NTAG213/215/216. I’ve done it - it works fine for phone-to-phone reading. However, printer hardware and apps like Prusa’s only recognize NFC-V tags. So if you want your tagged spools to work with built-in printer readers, use ICODE SLIX2 tags. Don’t make the mistake I’d expect most people to make and buy a bag of NTAG213s for this.

If you’re buying blank tags, look for ICODE SLIX2 or ISO 15693 specifically. You can find compatible tags on Amazon US or Amazon Europe (affiliate links).

How to Read and Write OpenPrintTag with Your Phone

You don’t need a Prusa printer or any special hardware to work with OpenPrintTag, just your phone. This is the part I was most keen to build, because a phone in your pocket is the most accessible NFC reader there is.

NFC.cool Tools supports OpenPrintTag natively on both iOS and Android, and I made sure the feature is completely free.

Reading a tag:

1. Open NFC.cool Tools

2. Hold your phone near the NFC tag on the spool

3. NFC.cool detects the OpenPrintTag format automatically

4. View the structured data: material, brand, color, weight, length, properties

Writing a tag:

1. Stick a blank ICODE SLIX2 tag on your spool

2. Open NFC.cool → NFC Apps section → OpenPrintTag

3. Fill in the material details: type, brand, color, weight, length

4. Tap to write

Updating remaining material: After a print, update the consumed weight field on the tag. Next time you scan, you’ll know exactly how much filament is left, no guessing, no weighing. This is the bit that turns a smart spool from a novelty into something I’d actually rely on.

If you want to look under the hood, you can use Expert Mode to inspect the raw NDEF records - useful when you need to debug a tag or verify the data structure. New to writing tags in general? I walk through the basics in how to write NFC tags on iPhone.

Why Use Your Phone?

Prusa printers are getting built-in NFC readers, and projects like SpoolSense (an open-source ESP32 reader) are adding dedicated hardware options. So why bother with your phone? Here’s the case I’d make:

• Works with any printer: Voron, Bambu Lab, Creality, Ender, whatever you use

• Write tags for any filament: Prusament comes pre-tagged, but you can tag Fillamentum, eSUN, Hatchbox, or any brand yourself

• Manage inventory away from your printer: scan spools at your desk, in your storage, or at a makerspace

• Debug tags: when a printer can’t read a tag, scan it with your phone to see what’s actually on it - this is the use I’d reach for most

• No extra hardware: your phone already has an NFC reader, and that’s the whole point

Practical Use Cases

Personal inventory: Tag every spool in your collection. When you’re planning a print, scan spools to check material type, remaining length, and color without unboxing anything.

Remaining filament tracking: Weigh your spool before and after a print, update the consumed weight on the tag. No more “will this spool have enough for a 14-hour print?” anxiety.

Makerspace or team use: Tag spools with material details so anyone in the shop can scan and identify them. No more mystery filament.

Filament testing notes: Found the perfect temperature for a specific spool? Update the tag with your notes for next time.

Multi-color and specialty materials: OpenPrintTag supports up to 6 colors per spool and 68+ property tags. Your glow-in-dark, carbon-fiber-filled PETG can finally be properly labeled, abrasive flag and all.

The Ecosystem Is Growing

OpenPrintTag is still young, but the momentum is real:

• Prusament ships with OpenPrintTag NFC tags on every spool

• Prusa printers are adding native NFC readers

• Open-source hardware readers like SpoolSense (ESP32-based) are emerging from the community

• 22+ companies have joined the initiative

• NFC.cool is the only general-purpose NFC app with full OpenPrintTag support on both iOS and Android, and I added it because I wanted to use it myself

I’ve watched the 3D printing industry need an open standard for smart spools for years, and I’ve watched a few proprietary attempts come and go. OpenPrintTag is the most credible one I’ve seen: backed by a major manufacturer, fully open source, and already shipping on real products. That combination is rare enough that I’d bet on it.

Getting Started

What you need:

• iPhone 7 or later, or an Android phone with NFC

• NFC.cool Tools (App Store / Google Play), free, OpenPrintTag included

• Blank ICODE SLIX2 / ISO 15693 NFC tags (Amazon US / Amazon Europe, affiliate links)

• Some filament spools to tag

That’s it. Five minutes from now, your first spool could be smart. If NFC itself is new to you, my beginner’s guide to NFC tags is the place I’d point you first, and the NFC reader/writer feature page covers what NFC.cool Tools can do beyond OpenPrintTag.

OpenPrintTag is an open-source initiative by Prusa Research. NFC.cool is an independent supporter of the standard. Learn more at openprinttag.org.

Most people know their iPhone can read NFC tags - tap to pay, scan a transit card, open a link. But the thing I keep having to convince people of is that your iPhone can also write to NFC tags, turning blank tags into smart triggers for just about anything.

I’ve spent years building NFC.cool, an app for reading and writing NFC tags, and writing is genuinely the part I never get tired of. Want a tag on your nightstand that silences your phone and sets an alarm? A tag on your desk that opens your work playlist? A tag at your front door that shares your Wi-Fi password with guests? Your iPhone can program all of these, and once you’ve done it once you’ll wonder why you waited.

This is the walkthrough I’d give a friend who just bought their first pack of tags: what you need, how to write the different types of data, and the practical projects I’d actually set up in minutes. If you’re brand new to the technology itself, my complete beginner’s guide to NFC tags covers the groundwork first.

What You Need

You only need three things to start writing, and none of them are expensive.

1. A Compatible iPhone

NFC tag writing requires iPhone 7 or newer running iOS 13 or later. If you bought your iPhone in the last eight years, you’re covered.

For the best experience, I’d reach for an iPhone with background NFC reading (iPhone XS and newer). These models can read NFC tags without opening an app first, which makes the tags you write far more pleasant to actually use. If you want to know exactly how the iPhone hardware handles all of this, I went deep on it in an insider look at NFC on iPhones.

2. Blank NFC Tags

You can buy blank NFC tags online for as little as €0.30-€1.00 each. They come in several form factors:

Which chip should you buy?

If you asked me to pick one, for most projects NTAG216 is the sweet spot - 888 bytes of usable memory, widely compatible, and affordable in bulk. It’s the chip I recommend and test against most. Here’s the quick breakdown:

• NTAG213 (144 bytes) - Enough for URLs and simple text. Cheapest option.

• NTAG215 (504 bytes) - Enough for contact cards, Wi-Fi credentials, and multiple records.

• NTAG216 (888 bytes) - Best all-rounder. The most headroom for contact cards, Wi-Fi credentials, and longer content like detailed vCards - what I recommend for most projects.

If you’re unsure, start with a mixed pack of NTAG216 stickers and stop overthinking it - they handle 90% of use cases. For the full chip-by-chip rundown, including which types iPhones actually like, I wrote a guide to NFC tag types for iPhones.

3. An NFC Writing App

Your iPhone needs an app to write data to tags. Apple’s built-in NFC support handles reading, but for writing, you need a dedicated app.

This is the part I’ve spent years on, so I’ll be upfront about my bias: NFC.cool Tools is purpose-built for exactly this, on both iPhone and Android. It supports writing all standard NDEF record types - URLs, text, Wi-Fi configurations, contacts, and more - with a clean interface that shows exactly how much tag memory you’re using. It also lets you lock tags, read technical details, and automate writing through iOS Shortcuts. You can see the full feature list on the NFC reader and writer page.

Other options exist (like Apple’s Shortcuts app for basic URL writing), but a dedicated NFC app gives you more control over what you write and how.

Step-by-Step: Writing Your First NFC Tag

I’ll start you where I start everyone: writing a URL to a tag. It’s the most common use case and the fastest win.

Writing a URL

1. Open NFC.cool Tools and tap the Write tab

2. Select “URL” as the record type

3. Enter your URL - for example, https://nfc.cool

4. Tap “Write to Tag”

5. Hold your iPhone near the blank NFC tag - the top edge of your iPhone (where the NFC antenna is) should be within 2-3 cm of the tag

6. Wait for the success confirmation - you’ll feel a haptic tap and see a checkmark

That’s it. Anyone who taps that tag with their phone will now be taken to your URL - no app needed, no QR code to scan. The first time I saw a colleague’s face when a blank sticker opened a website, I knew this was the demo to lead with.

Pro tip: The NFC antenna on iPhones sits at the top edge of the phone, near the camera. For the strongest connection, hold the top of your iPhone directly over the tag. If you want to double-check what you wrote without an app, you can read NFC tags right from your browser on Android.

What Can You Write to NFC Tags?

NFC tags use a format called NDEF (NFC Data Exchange Format) that defines standard record types. Once that model clicked for me, the whole technology stopped feeling like magic. Here’s what you can write:

URLs and Links

The most common use, and the one I reach for most. Write any web address, and tapping the tag opens it in the phone’s browser.

Practical uses:

• Restaurant menu link on a table tag

• Portfolio or LinkedIn profile on a business card

• Product page link on retail shelf tags

• Feedback form link at reception

Memory needed: ~30-80 bytes (most URLs fit on any tag)

Wi-Fi Network Credentials

Write your Wi-Fi network name (SSID) and password to a tag. Guests tap the tag and connect automatically - no typing long passwords.

How to write Wi-Fi credentials:

1. In NFC.cool Tools, select “Wi-Fi” as the record type

2. Enter your network name (SSID)

3. Enter the password

4. Select the security type (WPA2 or WPA3 for most home networks)

5. Write to the tag

Pro tip: Place a Wi-Fi tag near your router, on a keychain by the door, or inside a guest room. Label it “Tap for Wi-Fi” - in my experience this is the one tag every guest ends up thanking you for.

Memory needed: ~60-120 bytes depending on password length

Contact Cards (vCard)

Write a vCard contact to a tag. When someone taps it, your contact details pop up ready to save - name, phone, email, company, address.

This is essentially what a digital business card does, but baked directly into a physical tag. No app, no internet connection needed - the contact data lives on the tag itself.

How to write a contact:

1. Select “Contact” as the record type

2. Fill in the fields you want to share (name, phone, email, etc.)

3. Write to the tag

Memory needed: ~100-400 bytes depending on how many fields you include. Use NTAG215 or NTAG216 for contacts with addresses and notes.

One honest warning from the support emails I read: raw vCards on a tag can behave inconsistently on iPhone. If yours isn’t opening cleanly, I dug into the causes in why your vCard NFC tag isn’t working on iPhone.

Note: For a richer experience with photos, social links, and analytics, take a look at NFC.cool Business Card - it creates a hosted digital business card profile and can write the link to any NFC tag. When someone taps, iOS users see a native App Clip and Android users open a website on the nfc.cool domain - no app needed. In my own networking I’ve found this far more reliable than raw vCards.

Plain Text

Write any text message to a tag. Less common than URLs, but useful for:

• Inventory labels (serial numbers, descriptions)

• Instructions or notes attached to equipment

• Easter egg messages in scavenger hunts

• Asset tracking in warehouses

Memory needed: Varies by text length (~1 byte per character)

Phone Numbers and Email Addresses

Write a tel: or mailto: URI to trigger a phone call or compose an email when tapped.

Useful for:

• Emergency contact tags on medical equipment

• “Call for service” tags on vending machines

• Support contact tags on products

App-Specific Data

Some apps can write custom NDEF records that trigger specific app actions. For example, you could write a record that opens a specific shortcut, playlist, or app screen.

Advanced: Writing with iOS Shortcuts

This is where things get fun for me. Apple’s Shortcuts app has built-in NFC writing support, and NFC.cool Tools extends it further with its own Shortcuts actions.

Basic URL Writing with Shortcuts

1. Open the Shortcuts app

2. Create a new shortcut

3. Search for the “Set NFC Tag” action (under Scripting → NFC)

4. Configure what to write (URL, text, etc.)

5. Run the shortcut and tap a tag

This is useful for batch-writing multiple tags with the same data.

NFC.cool Tools Shortcuts Integration

NFC.cool Tools adds its own Shortcuts actions, giving you more options:

• Write Tag - Write any supported record type programmatically

• Read Tag - Scan and return tag data to your shortcut

• Scan History - Access your recent scan results

This opens up automation possibilities. For example, you could create a shortcut that:

1. Asks for a product name

2. Generates a URL like https://yoursite.com/product/{name}

3. Writes it to an NFC tag

4. Logs the tag to a spreadsheet

Perfect for batch inventory tagging or event badge setup.

Practical NFC Tag Projects

These are the projects I keep coming back to - ready to build, and each one takes a few minutes:

Smart Home Tags

Nightstand Tag - “Bedtime Mode” Write a URL that triggers an iOS Shortcut to:

• Enable Do Not Disturb

• Set tomorrow’s alarm

• Lower screen brightness

• Start a sleep playlist

Desk Tag - “Work Mode”

• Open your task manager

• Start a focus timer

• Connect to your work VPN

• Play a concentration playlist

Door Tag - “Leaving Home”

• Check weather forecast

• Show commute time

• Trigger smart home “away” scene

Business Tags

Conference Badge Tag Write your NFC.cool Business Card URL to a tag stuck on the back of your conference badge. Contacts tap your badge → your full digital business card appears.

Product Tags Write links to product documentation, warranty registration, or support pages. Attach to products or packaging.

Meeting Room Tags Write links to room booking calendars or Wi-Fi credentials. Stick near the door.

Creative Projects

Music Tags Write Spotify or Apple Music album links to NFC stickers. Stick them on physical album art, and tapping plays the album.

Board Game Tags Write links to rule PDFs or tutorial videos. Stick inside the box lid.

Recipe Tags Write links to favorite recipes and stick tags on spice jars or cookbook pages.

Locking NFC Tags

Once you’ve written a tag and you’re happy with its content, you can lock it. Locking makes the tag permanently read-only - nobody can overwrite your data. I treat this as a deliberate, final step, never something to tap through quickly, because there is no undo.

In NFC.cool Tools:

1. Tap the Lock option after writing

2. Confirm - this is irreversible

When to lock:

• Tags in public locations (prevent tampering)

• Product tags (protect your URLs)

• Business cards (keep your contact data safe)

• Any tag you don’t plan to rewrite

When NOT to lock:

• Tags you might want to update later (Wi-Fi password changes, seasonal URLs)

• Experimentation/learning - leave them rewritable while you test

Troubleshooting

Most of the “why won’t it write” questions I get land on one of these four causes. Here’s how I’d work through them.

“Unable to Write” Error

• Tag might be locked. If someone (or you) previously locked the tag, it’s permanently read-only. You’ll need a new tag.

• Not enough memory. Your data might be too large for the tag’s capacity. Try a tag with more memory (NTAG215 → NTAG216) or reduce your data.

• Tag not positioned correctly. Move the top edge of your iPhone slowly over the tag. Some surfaces (metal, thick cases) can interfere.

• Tag is damaged. NFC tags are durable but not indestructible. Extreme heat, bending, or puncture can kill them.

Writing Seems to Work But Tag Doesn’t Respond

• Check NDEF format. The data must be written in NDEF format for phones to read it automatically. NFC.cool Tools handles this for you, but custom-written tags might have formatting issues.

• iPhone model matters. Older iPhones (7, 8, X) require an app to read tags. iPhone XS and newer read tags automatically in the background.

Tag Works on Android But Not iPhone

• Check the chip type. iPhones work best with NTAG-series chips (NTAG213, 215, 216). Some other chip types may not be compatible with iOS.

• NDEF formatting. The tag must be NDEF-formatted. Some bulk-purchased tags arrive unformatted - write to them with NFC.cool Tools to auto-format them.

Tips for Getting the Most Out of NFC Tags

These are the small lessons I’ve picked up the hard way, so you don’t have to.

1. Label your tags. A blank sticker on a desk isn’t helpful. Use a label maker or Sharpie to indicate what the tag does (“Tap for Wi-Fi”, “Work Mode”, etc.).

2. Avoid metal surfaces. Metal interferes with NFC signals. If you must attach to metal, use anti-metal NFC tags (they have a ferrite layer that shields against interference). They’re slightly thicker and more expensive but work perfectly on metal surfaces.

3. Test before you stick. Write the tag, test it, then peel the adhesive and stick it in place. Peeling a stuck tag back off to rewrite it is the kind of small annoyance I’ve learned to avoid entirely.

4. Use the right tag for the job. Don’t waste NTAG216 (888 bytes) on a simple URL that takes 40 bytes. And don’t try to fit a full vCard on an NTAG213 (144 bytes).

5. Waterproof options exist. Epoxy-coated NFC tags are waterproof and more durable. Good for outdoor use, kitchens, or bathrooms.

6. Combine NFC tags with Shortcuts. The real power of NFC tags on iPhone isn’t just opening URLs - it’s triggering complex automations. An NFC tag can launch any iOS Shortcut, which can control smart home devices, send messages, log data, and more.

Frequently Asked Questions

Can I rewrite an NFC tag?

Yes, as long as the tag hasn’t been locked. Standard NFC tags can be rewritten 100,000+ times. Just write new data over the old data - no need to “erase” first.

How close does my iPhone need to be?

Within 2-4 cm (about 1-2 inches). The NFC antenna is at the top edge of the iPhone. Hold the top of your phone directly over the tag for the best connection.

Can I write to NFC tags without an app?

iOS Shortcuts has a built-in “Set NFC Tag” action for basic writes (URLs, text). But for Wi-Fi credentials, contacts, and more complex records, you’ll need an app like NFC.cool Tools.

Do NFC tags need batteries?

No. NFC tags are passive - they have no battery and draw power from your phone’s NFC reader when you tap them. Tags can last 10+ years because there’s nothing to run out.

Can I password-protect an NFC tag?

Yes. NFC.cool Tools can set password protection on NTAG tags, on both iPhone and Android. Note that this only prevents the tag from being overwritten - it does not stop anyone from reading what’s already on the tag. If you need the contents themselves to be unreadable without a key, you want encrypted data instead - see our guide to NFC Safe. Locking a tag is the other option: it permanently blocks any further writes.

Will NFC tags work through a phone case?

Yes, most phone cases are fine. NFC works through plastic, silicone, leather, and even thin wallets. Very thick cases (like heavy-duty rugged cases) or cases with metal plates (for magnetic car mounts) might interfere.

How many tags can I write with one iPhone?

Unlimited. There’s no restriction on how many tags you write. The limiting factor is the tags themselves, not your phone.

What’s Next?

Now that you know how to write NFC tags, the possibilities are wide open. My advice is the same as ever: start with one simple project - a Wi-Fi tag for guests or a business card tag - get the small win, and build from there.

If you’re looking for a powerful, easy-to-use NFC writing app, NFC.cool Tools is the app I’ve built to handle exactly this - from basic URL writing to advanced tag management, with iOS Shortcuts integration for automation.

And if you want to turn NFC tags into professional digital business cards, NFC.cool Business Card lets you create a beautiful card profile and write its URL to any NFC tag. The app UI and App Clip support 35 languages on iOS, and Android recipients see a website on the nfc.cool domain (currently English only).

Download NFC.cool Tools: App Store | Google Play

Download NFC.cool Business Card: App Store | Android (in NFC.cool Tools)

Think about what’s on your business card. Your full name. Your email address. Your phone number. Maybe your office address, your LinkedIn profile, your company name and title.

Now think about this: when you share a digital business card, you’re not just handing someone a piece of cardboard. You’re giving a platform access to that data - and to data about the person you’re sharing it with.

Most digital business card apps collect information about both sides of the exchange. Who shared, who viewed, when, where, on what device, for how long. Some go further than you’d expect.

This isn’t a scare piece. Digital business cards are genuinely better than paper - for networking, for the environment, for keeping your info up to date. But not all platforms treat your data with the same care, and most people never think to ask.

You should.

What Actually Happens When You Share a Digital Business Card?

Here’s the typical flow when someone taps your NFC card or scans your QR code:

1. Their phone opens a URL hosted by the platform

2. The platform serves your contact information

3. The platform logs the interaction - at minimum, a timestamp

4. Depending on the platform, it may also capture: the viewer’s IP address, device type, browser, approximate location, time spent on your card, which links they tapped

That’s the baseline. Some platforms do more.

Recipient Solicitation

Several digital business card platforms - especially on their free tiers - will market to the people who view your card. Meaning: someone scans your QR code to get your email, and then the platform sends them promotional emails about signing up.

You didn’t ask for that. The person who viewed your card definitely didn’t ask for it. But it happens because the platform needs to grow, and your contacts are free leads.

Not every platform does this. But enough do that it’s worth checking before you sign up.

Conversation Recording

This one might surprise you. Some platforms now offer AI-powered notetaking features that record in-person conversations. The pitch is appealing: meet someone at a conference, tap record, and let AI capture the key points automatically.

The problem is consent. In many jurisdictions - including most of the EU under GDPR and over a dozen US states with two-party consent laws - recording a conversation without the other person’s knowledge or explicit consent is illegal. Even where it’s technically legal, secretly recording a networking conversation raises serious ethical questions.

The person you just met thinks they’re having a friendly chat. They don’t know your phone is transcribing everything they say and uploading it to a cloud server.

Data Enrichment

Some platforms offer “AI contact enrichment” - you scan a business card or exchange contacts, and the platform automatically pulls in additional data from public sources: LinkedIn profiles, company info, social media accounts.

Convenient? Sure. But it means the platform is building a profile of the people you meet, often without their knowledge. Your contacts didn’t sign up for this. They shared their business card, not their entire digital footprint.

The Hidden Cost of “Free”

Many digital business card platforms offer generous free tiers. That’s great for accessibility, but it raises an important question: how does a free product make money?

The honest answers vary:

• Upselling to paid plans - The healthy model. Give away basic features, charge for advanced ones.

• Platform branding as advertising - Your card becomes a billboard for the platform. Every share is marketing.

• Recipient data harvesting - Your contacts become leads for the platform itself.

• Data aggregation - Anonymized (or not) networking patterns sold to third parties.

Not every free plan has hidden catches. Some platforms - like Wave Connect - genuinely offer useful free tiers without soliciting your recipients. Others use “free” as a pipeline to collect contact data at scale.

The rule of thumb: if a platform offers unlimited features for free and doesn’t have a clear business model, your data is the business model.

What to Look for in a Privacy-Respecting Platform

Here’s a practical checklist. You don’t need to audit every line of a privacy policy (though you can). Just ask these questions:

1. Does It Solicit Your Recipients?

When someone views your card, does the platform contact them with marketing? This should be a dealbreaker for most professionals. Your contacts trusted you with their attention, not a random platform.

2. What Data Does It Collect About Viewers?

Basic analytics (how many views) are reasonable. IP addresses, device fingerprinting, and behavioral tracking are not - especially without disclosure. Check if the platform’s privacy policy specifically lists what it collects about card viewers (not just cardholders).

3. Where Is the Data Stored?

This matters especially in Europe. Under GDPR, transferring personal data outside the EU requires specific legal safeguards (Standard Contractual Clauses, adequacy decisions). If your platform stores data in the US without these protections, you may be non-compliant just by using it.

4. Can You Export Your Data?

GDPR gives you the right to data portability - you should be able to download everything the platform has about you. If there’s no export option, that’s a red flag. You should own your contacts, not rent access to them.

5. Can You Actually Delete Your Account?

Not “deactivate.” Delete. With all associated data removed from their servers. Some platforms make this surprisingly difficult, burying it behind support tickets rather than offering a self-service option.

6. Does It Have Access Controls?

Can you set your profile to private? Can you protect it with a PIN? Can you choose which information is visible and to whom? These aren’t enterprise features - they’re basic privacy tools that every platform should offer.

7. Does It Record Audio?

This is newer, but becoming more common in the lead-capture space. If a platform offers conversation recording or AI notetaking, understand the legal implications before you use it. In the EU, recording conversations without all parties’ consent violates GDPR. In the US, laws vary by state.

GDPR and Digital Business Cards: What You Need to Know

If you’re based in Europe - or do business with anyone in Europe - GDPR applies to your digital business card. Here’s what that means in practice:

For you as a cardholder:

• You have the right to access, export, and delete your data

• The platform needs a lawful basis to process your information

• You should know exactly what data is collected and shared

For the people who view your card:

• They have rights too - even if they never signed up for the platform

• The platform can’t just harvest their data without a legal basis

• Collecting IP addresses, device info, and browsing behavior counts as processing personal data under GDPR

For your employer (if using team/enterprise plans):

• Your company may be jointly responsible for data processing through the platform

• CRM integrations multiply the number of systems handling personal data

• Each integration requires its own data processing assessment

The practical takeaway: choose a platform that takes GDPR seriously by default, not one that bolts it on as an enterprise add-on.

Why I Built NFC.cool Business Card With Privacy First

Full disclosure: this is the NFC.cool blog, so I’m going to talk about my approach. But I’ve tried to be honest about the landscape above, and I’ll be honest here too.

When I built NFC.cool Business Card, privacy wasn’t an afterthought or a marketing checkbox. It shaped the product:

PIN-Protected Profiles - You can lock your business card behind a 4-digit PIN with rate-limited attempts. Share your card URL freely, but only let people see your details when you want them to. This is useful for NFC cards you might lose, or for times when you want to control who sees your full contact info.

Public/Private Toggle - Choose exactly which fields are visible. Maybe your phone number is only for close contacts. Maybe your address is private. You control the granularity.

No Conversation Recording - I don’t record audio. Period. I think networking should be built on trust, not surveillance.

No Recipient Solicitation - When someone views your card, they see your card. They don’t get marketing emails from me. Your contacts are yours, not my leads.

No Data Monetization or Advertising - Your vCard and account data are stored on my server to power the service, but nothing is used for advertising or third-party data processing.

GDPR Data Export - On iOS, export your contacts as CSV anytime. No support tickets, no waiting period.

NFC Hardware Freedom - It works with any standard NFC tag. NFC.cool doesn’t sell NFC hardware - you’re free to use any third-party tag you choose, without proprietary tracking you can’t audit.

European Indie Developer - I’m a solo developer based in Portugal. I don’t have VC investors pushing me to monetize user data for growth metrics. My incentive is building a product people trust, not maximizing data collection.

I’m not perfect. Analytics and lead capture are currently iOS-only (Android support coming soon). There are no CRM integrations or webhooks yet - iOS offers CSV export for getting contacts out. My marketing budget is a fraction of the bigger players. But my privacy model is something I genuinely believe in, and I think it matters.

A Privacy Checklist for Choosing Your Platform

Before you sign up for any digital business card service, run through this:

• ✅ No recipient solicitation on your plan tier

• ✅ Clear privacy policy that specifies what viewer data is collected

• ✅ Data export available (GDPR right to portability)

• ✅ Account deletion is self-service, not hidden behind support

• ✅ Profile visibility controls (public/private toggle, PIN protection)

• ✅ No mandatory conversation recording features that affect people you meet

• ✅ GDPR compliance if you do business in Europe (or with Europeans)

• ✅ Transparent business model - you understand how the platform makes money

If a platform fails more than one or two of these, consider whether the convenience is worth the trade-off.

The Bottom Line

Digital business cards are the future of networking. Paper is wasteful, outdated, and can’t be updated after you hand it out. The benefits are real.

But your business card is your professional identity. It’s the first thing people see when they meet you. The platform you trust with that information should earn that trust - through transparency, through user controls, and through a business model that doesn’t depend on exploiting your data or your contacts’ data.

Privacy isn’t about having something to hide. It’s about having the right to choose what you share, with whom, and on whose terms.

Choose wisely.

Ready to try a privacy-first digital business card? Download NFC.cool Business Card for iPhone or get it on Android inside NFC.cool Tools. App UI and App Clip available in 35 languages.

You’ve been there.

It’s day two of a three-day conference. You’ve already handed out your entire stack of business cards. The keynote speaker you’ve been waiting to meet is standing right there at the coffee station, and you’re patting your pockets like you lost your wallet.

Or maybe you made it through the event with cards to spare - only to come home with a crumpled pile of 47 other people’s cards that you now need to manually type into a spreadsheet before you forget who was who.

Paper business cards and conferences have never been a great match. They just happened to be the only option for a very long time.

They’re not anymore.

Why Paper Cards Fail at Conferences

Before we get to the solution, let’s be honest about the problem. Paper business cards weren’t designed for high-volume networking events. They were designed for one-on-one meetings where you hand one card to one person, maybe twice a day.

At a conference, everything that’s slightly inconvenient about paper becomes a real problem:

You run out. The average conference attendee meets dozens of people over two or three days. Most people bring 50-100 cards and hope for the best. If you’re a speaker, exhibitor, or just genuinely good at networking, that’s not enough.

They get destroyed. Cards get shoved into badge holders, folded into jacket pockets, stacked under coffee cups, and dropped on expo floors. By the time someone finds your card a week later, it looks like it went through the wash.

You can’t track anything. Which of those 47 cards came from the fintech panel? Which was the person who wanted to partner on that project? Paper doesn’t come with timestamps, notes, or context.

88% end up in the trash. That’s not a guess - it’s the most-cited statistic in the industry (originally from Adobe research). Within one week of a conference, nearly 9 out of 10 paper cards are thrown away. All that printing, all that exchanging, and the vast majority produces zero follow-up.

They can’t be updated. Got promoted between conferences? Changed your phone number? Launched a new product? Your old cards are already in people’s pockets with outdated information, and there’s nothing you can do about it.

The Three-Phase Plan: Before, During, and After

Going digital isn’t just about swapping paper for an app. The real advantage is having a system that works across the entire conference timeline - from preparation to follow-up. Here’s how to set it up.

Phase 1: Before the Conference

The worst time to set up your digital business card is while you’re standing in a registration line. Get this done at least a week before the event.

Choose your digital card platform

If you don’t have one yet, look for these conference-specific features:

• Multiple sharing methods - You’ll want NFC tap, QR code display, and a shareable link. Different situations call for different approaches at a conference.

• Reliable in poor connectivity - Conference WiFi is notoriously unreliable. NFC taps are instant (they transmit a link), and the card profile loads quickly even on a spotty connection - much more reliable than loading a full app or website.

• Multiple card profiles - If you’re attending as both a speaker and a vendor, or if you work across different brands, you need separate cards for separate contexts.

• No app required for recipients - The person you’re meeting shouldn’t need to download anything. If your card requires the other person to install an app before they can see your info, you’ve already lost them.

• Multi-language support - For international conferences, having your card available in the recipient’s language is a real differentiator.

NFC.cool Business Card covers all of these - NFC + QR + link sharing, multiple card profiles, no app needed for recipients (App Clip on iOS, website on Android), and the app UI and App Clip support 35 languages. It’s what we’d recommend, but whatever you choose, make sure it hits those criteria.

Create an event-specific card (or update your existing one)

Don’t just use your generic card. For conferences, consider:

• Adding your talk title and time if you’re speaking (“Catch my talk: ‘AI in Fintech’ - Hall B, Thursday 2pm”)

• Including a conference-specific CTA (“Let’s grab coffee at the event - text me”)

• Linking to relevant work samples - a portfolio, a case study, a demo video

• Removing clutter - At a conference, people don’t need your fax number. They need your name, what you do, and the fastest way to reach you.

With a digital card, you can make these changes in seconds and revert after the event. Try doing that with 500 printed cards.

Prepare your hardware

This is optional but makes a big impression:

• NFC-enabled phone - Most modern smartphones (iPhone 7+ and most Android phones from 2018+) support NFC. Make sure yours has it enabled.

• NFC card or sticker - A physical NFC card that links to your digital profile gives you the best of both worlds. You physically hand someone something (the familiar ritual), but it instantly opens your digital card on their phone. No app install. No typing. Just a tap.

• Phone case with NFC sticker - Even simpler. Stick an NFC tag on the back of your phone case that links to your card. When someone asks for your info, you just say “tap your phone on the back of mine.”

Put your QR code on your lock screen (iOS)

NFC.cool Business Card’s Conference Mode uses an iOS Live Activity to put your card’s QR code directly on your lock screen. This is the fastest sharing method at conferences:

• Your QR code is always visible - no unlocking, no opening any app

• People just scan your screen while you’re talking to them

• It’s even faster than Apple Wallet because you don’t need to find the right pass

Apple Wallet integration is also available as a backup option.

Phase 2: During the Conference

This is where digital cards actually shine versus paper.

The NFC tap (fastest method)

You’re in a conversation. It’s going well. They say “let me get your card.” Instead of breaking eye contact to dig through your bag, you pull out your NFC card (or your phone) and say “just tap your phone here.”

Three seconds. Your full contact info, links, photo, and whatever else you’ve included is now on their phone. No typing. No fumbling. No “let me spell my last name for you.”

The wow factor is real. At conferences, people remember the person whose card appeared on their phone like magic. It’s a conversation starter in itself.

Pro tip: The NFC tap itself works without WiFi - it’s a direct phone-to-tag communication that opens a link. The recipient’s phone will need a brief data connection (cellular works fine) to load your card profile, but it’s far faster and more reliable than loading a full website in a crowded expo hall.

The QR code (universal fallback)

Not everyone is comfortable with NFC yet, and some older phones don’t support it well. For those situations, pull up your QR code:

• Open your digital card app and display the QR code

• The other person opens their camera and scans it

• Your card opens in their browser - no app needed

It takes about five seconds instead of three, and it works with literally any smartphone with a camera.

Conference hack: If you’re at a booth or table, print your QR code on a small stand. People can scan it while chatting with you - no exchange needed. You can even put it on your conference badge with a small sticker.

The link share (for virtual connections)

Conferences aren’t just about the expo floor anymore. There are Slack channels, WhatsApp groups, LinkedIn DMs, and conference app chats. For those virtual interactions:

• Share your card’s link directly in the chat

• No QR code needed, no physical proximity required

• Works for post-session Q&A, virtual attendees, or people you meet on social media during the event

Keep track as you go

One of the biggest advantages over paper: you can see who viewed your card and when. After a particularly good conversation, make a quick note in your phone: “Sarah - VP Marketing at Acme - discussed partnership on sustainability project.” When you follow up later, you’ll have context that a paper card never provides.

Phase 3: After the Conference

This is where most networking efforts die. You fly home, drop the card stack on your desk, and say “I’ll sort through those tomorrow.” Tomorrow becomes next week. Next week becomes never.

Digital cards fix this because the work is already done.

Follow up within 48 hours

Your contacts already have your digital card with all your info. But the follow-up still matters. Send a quick message referencing your conversation:

“Hey Sarah - great talking at the sustainability panel yesterday. Here’s the case study I mentioned: [link]. Let’s find time to continue that conversation.”

Because your digital card includes your photo, they’ll actually remember who you are when your message arrives. (When’s the last time a paper card had a photo?)

Review your sharing analytics

Many digital card platforms show you who opened your card and when (NFC.cool offers this on iOS, with Android support coming soon). This tells you:

• Who was interested enough to actually look at your profile (not just pocket your card politely)

• When they looked - someone reviewing your card three days after the conference is a warm lead

• What they clicked on - your portfolio? Your LinkedIn? Your booking link?

This data is conference gold. It tells you who to prioritize in your follow-up.

Update your card for next time

The conference is over. Remove the event-specific details, update your card with any new info (new title? new project? new headshot?), and you’re ready for the next one. Zero printing lead time. Zero waste.

“But What If They Expect a Paper Card?”

This is the most common hesitation, and it’s fair. Depending on the industry and region, some people still expect a physical exchange.

Here’s the thing: an NFC card is a physical exchange. You hand someone a card. They hold it near their phone. Your info appears. The ritual is preserved - it’s just faster and more impressive.

And if someone genuinely insists on paper, you can always say “I’ve gone digital, but let me send you my card right now” and share it to their phone via QR or link. In two years of conferences, we’ve never heard of anyone refusing a digital card. Most people are relieved they don’t have to type your info later.

Quick-Start Checklist

Here’s everything you need to do, in order:

• Download a digital business card app (we recommend NFC.cool Business Card - free on iOS and Android (inside NFC.cool Tools))

• Create your card with name, title, company, contact info, and links

• Add your photo - it helps people remember you after the event

• Save your QR code to Apple Wallet (iOS) for quick lock-screen access

• Optional: Order an NFC card or sticker for the physical tap experience

• Customize your card for the specific event (talk details, special CTA)

• Practice the tap/QR flow once before the event so it feels natural

• Follow up within 48 hours after the event using your sharing data

Frequently Asked Questions

Does the other person need an app to receive my digital card?

No. When you share via NFC tap, QR code, or link, your card opens in their web browser. They can save your contact info directly to their phone’s address book - no app install required.

What if the conference WiFi is terrible?

The NFC tap itself works without WiFi - it transmits a link directly from the tag to the phone. Both NFC and QR codes will need a brief data connection to load the card profile, but most phones can fall back to cellular data. The profile is lightweight and loads quickly even on slow connections.

Can I use different cards for different conferences?

Yes - most digital card platforms support multiple card profiles. Create one for each event, role, or audience. Switch between them in seconds. With NFC.cool BC, you can create and manage as many cards as you need.

Are NFC business cards compatible with all phones?

All iPhones since iPhone 7 (2016) and the vast majority of Android phones from 2018 onward support NFC reading. The recipient doesn’t need NFC to receive your card - they can always scan the QR code or click a link instead.

How much does it cost compared to printing paper cards?

A basic digital business card is free on most platforms (including NFC.cool). A physical NFC card or sticker typically costs $5-$30 as a one-time purchase and can be reprogrammed for every event. Compare that to $50-$150 per print run of paper cards that can’t be updated and go straight to the recycling bin.

What about data privacy at conferences?

This is worth asking about any platform you use. Some digital card providers track recipients, record conversations, or sell contact data. NFC.cool BC is privacy-first: no data monetization or advertising, no recipient solicitation, no conversation recording, PIN protection for sensitive cards, and full GDPR compliance with data export.

The Bottom Line

Conferences are where paper business cards are at their worst: you need too many, they get destroyed, they can’t be tracked, and 88% end up in the trash within a week.

Digital business cards are where conferences are at their best: fast sharing that actually impresses people, analytics that tell you who’s interested, and follow-up that happens automatically instead of “someday.”

Your next conference is coming up. This time, leave the paper at home.

NFC.cool Business Card is available for free on iOS and on Android inside NFC.cool Tools. Create your first card in under a minute.

You’ve probably tapped your phone to pay for a coffee, scanned a transit card, or unlocked a hotel room door with it. Every one of those is NFC at work.

I’ve spent years building NFC.cool, an app for reading and writing NFC tags, and the one thing I wish more people knew is this: NFC isn’t only for payments and keycards. A tiny NFC tag - a chip that costs a few cents and never needs a battery - can automate your home, hand over your contact details in a single tap, and wire the physical world to digital actions.

This is the guide I’d give anyone starting out. I’ll walk through what NFC tags are, how they actually work, which ones I’d buy, and the uses I’ve genuinely seen pay off.

What Is NFC?

NFC stands for Near Field Communication. It’s a short-range wireless technology that lets two devices swap data when they’re held within a few centimeters of each other.

It runs at 13.56 MHz and works up to about 4 cm (roughly 1.5 inches). That tiny range trips people up at first, but it’s deliberate - it’s a security feature. Unlike Bluetooth or Wi-Fi, you can’t accidentally connect to something across the room.

Every modern smartphone has an NFC chip inside. iPhones have read NFC since the iPhone 7 in 2016, and Android phones longer than that. Hold your phone near a tag and the phone powers the tag and reads it - the whole exchange happens in a fraction of a second.

What Is an NFC Tag?

An NFC tag is a small, passive chip built into a sticker, card, keychain, or just about any form factor. “Passive” is the word that matters: an NFC tag has no battery. It’s powered entirely by the field of whatever device reads it.

That’s what makes them so easy to live with:

• Practically indestructible - no battery to die, nothing to wear out

• Cheap - a few cents each in bulk

• Tiny - smaller than a coin, thinner than a credit card

• Long-lived - a decent tag lasts 10+ years

Each tag holds a small amount of memory. You can store a URL, contact details, Wi-Fi credentials, plain text, or instructions that tell the reading phone what to do.

How Is NFC Different from RFID?

NFC is actually a subset of RFID (Radio-Frequency Identification). Here’s how I explain the difference:

All NFC is RFID, but not all RFID is NFC. The badge you swipe to get into an office often runs at 125 KHz, and your phone simply can’t read that. NFC tags use the 13.56 MHz frequency phones do support. “Why won’t my phone read my work badge?” is one of the questions I get asked most, and this is almost always the answer. (If that’s the rabbit hole you’re in, I wrote a whole post on why your iPhone can’t open an RFID door.)

NFC Tag Types: Which One Should You Buy?

NFC tags come in types defined by the NFC Forum, the industry standards body. The ones you’ll actually run into are built on chips from NXP Semiconductors - the NTAG series.

The NTAG Family

These are by far the most common consumer NFC tags:

NTAG213

• Memory: 144 bytes (about 132 usable)

• Best for: URLs, contact cards, simple automations

• Price: Cheapest option (~$0.15-$0.30 per tag)

• URL capacity: ~130 characters

The workhorse. For a single URL or a short piece of text, NTAG213 is all you need - it’s what most NFC business cards and marketing tags use.

NTAG215

• Memory: 504 bytes (about 488 usable)

• Best for: Longer URLs, vCards with multiple fields, Wi-Fi credentials

• Price: ~$0.20-$0.40 per tag

• URL capacity: ~480 characters

A solid middle option - enough headroom for longer URLs and multi-field vCards, cheap enough to buy in bulk. It’s also the chip inside Nintendo Amiibo figures, which is why writable NTAG215s are so easy to find.

NTAG216

• Memory: 888 bytes (about 868 usable)

• Best for: Full vCards, multiple records, longer text content

• Price: ~$0.30-$0.60 per tag

• URL capacity: ~850 characters

The most memory in the consumer NTAG line, and the tag I’d pick if you only buy one. The extra headroom means you won’t hit a wall - full vCards, multiple records, longer text, room for future edits - and it’s the standard NFC.cool tests against.

Other Tag Types You Might See

• NTAG424 DNA - An advanced chip with cryptographic authentication. It shows up in anti-counterfeiting, luxury-goods verification, and the new EU Digital Product Passport rules. Overkill for personal use, genuinely important for commercial work.

• MIFARE Classic - An older NXP chip used in access cards and transit systems. It isn’t a standard NFC Forum tag, so phone compatibility is a coin toss. I’d skip it for personal projects.

• ST25T - STMicroelectronics’ NFC tag line. Similar to NTAG in function, less common in consumer products.

• ICODE - Built for library and logistics tracking. You probably won’t touch these.

Quick Buying Guide

Where to buy: My recommended NFC tags page lists the NTAG216 stickers I use and test against. Sticker-format tags are the most versatile - they stick to almost anything.

My honest advice: buy a pack of NTAG216 stickers and stop overthinking it. I’ve watched people agonize over chip types for a project that a 20-cent tag handles fine. If you ever want the deeper breakdown, I went chip-by-chip in NFC tag types for iPhone.

How NFC Tags Work (The Simple Version)

People expect this to be complicated. It isn’t. Here’s the whole thing, start to finish:

1. Power transfer - Your phone’s NFC antenna generates an electromagnetic field. When a tag enters that field (~4 cm), the field induces a tiny current in the tag’s antenna coil, and that current powers the chip.

2. Data exchange - The powered chip sends its stored data back to your phone as modulated radio waves at 13.56 MHz. The exchange takes about 100 milliseconds.

3. Action - Your phone reads the data and decides what to do. A URL opens in the browser. A phone number offers to call. A Wi-Fi record offers to connect. An app-specific record opens the matching app.

No pairing. No PIN. No app required for basic reading. Tap and go.

NDEF: The Language Tags Speak

The data on an NFC tag is structured using NDEF (NFC Data Exchange Format). I think of NDEF as the common language that lets any NFC phone understand any NFC tag.

Common NDEF record types:

• URI - A web link (http, https, tel:, mailto:)

• Text - Plain text in any language

• Smart Poster - URL + title + icon combined

• Wi-Fi - Network name, password, and security type

• vCard - Contact information

• MIME - Any custom data type, used by apps for custom actions

When you write a tag in an app like NFC.cool Tools, you’re creating NDEF records. When a phone reads the tag, it parses those records and acts on them. That’s the whole model - once it clicked for me, everything else about NFC made sense.

Reading NFC Tags

On iPhone

iPhones handle tags automatically. On iPhone XS and later (and the 3rd-gen iPhone SE), NFC reading runs in the background - hold the top of the phone near a tag and it reads instantly, no app needed. Older iPhones (7, 8, X) need you to open an NFC reader app first.

What happens when you scan depends on the data:

• URL - a notification appears, tap to open it in Safari

• Phone number - an option to call

• App Clip - launches an App Clip if one exists

• Custom data - opens the associated app

If you just want to see what’s on a tag right now, you can also read NFC tags straight from your browser on Android - no install.

On Android

Most Android phones have had NFC since around 2012. Reading is on by default; you’ll find the toggle under Settings, Connected devices, NFC. Tap a tag and Android hands the data to the most appropriate app - URLs to the browser, contacts to the address book, custom records to their app.

Writing NFC Tags

This is the part I find genuinely fun. Writing to a tag means programming it with whatever data you want.

What You Need

1. An NFC-enabled phone

2. An NFC writing app (like NFC.cool Tools - available for iPhone and Android)

3. A blank or rewritable NFC tag

How to Write a Tag

The process is short:

1. Open your NFC writing app

2. Choose what to write (URL, text, Wi-Fi credentials, contact, and so on)

3. Enter the data

4. Hold your phone against the tag

5. Wait for the confirmation, usually about a second

That’s it. The tag now holds your data and works with any NFC phone that reads it. If you want the iPhone-specific walkthrough, I wrote one here: how to write NFC tags on iPhone.

Important: Locking Tags

Once a tag is written, you can optionally lock it. Locking makes it permanently read-only - nobody can overwrite or erase it. There’s no undo.

I treat locking as a deliberate, final step, never something to tap through quickly. Lock a tag when:

• It’s publicly accessible (on a poster, product, or business card)

• You want to prevent tampering

• The data won’t change

Leave it unlocked when:

• You might update the data later

• You’re still experimenting

• It lives in a controlled environment, like your home

16 Practical Ways to Use NFC Tags

I could list a hundred. These are the ones I keep coming back to - the uses I’ve seen actually stick.

Around the Home

1. Wi-Fi guest network sharing Stick a tag near your front door or guest room and program it with your Wi-Fi credentials. Guests tap it and connect instantly, no typing a long password.

2. Smart home scenes Place tags around the house to trigger automations. Tap the one on your nightstand for “goodnight” (lights off, alarm set, Do Not Disturb on). Tap the one by the door for “leaving home” (lights off, thermostat down, vacuum starts).

3. Alarm clock Put a tag in the kitchen or bathroom and build a shortcut that only dismisses your morning alarm when you physically scan it. It works - it forces you out of bed.

4. Appliance manuals Stick a tag on the washing machine or dishwasher and point it at the manual PDF. You’ll never search for a manual again.

5. Medication reminders Place a tag on a pill bottle. Scanning it logs a timestamp to a note or spreadsheet, so you have a record of when you took it.

At Work

6. Digital business cards The most popular NFC use case in business. Instead of paper cards, an NFC business card shares your contact details with one tap. NFC.cool Business Card lets you build a professional digital card and write its URL to any third-party NFC tag - iOS recipients see a native App Clip, Android recipients open a website on the nfc.cool domain, and both can save your contact in one tap.

7. Conference room check-in Put a tag outside meeting rooms. Tapping it launches your calendar or logs attendance - simpler than any booking system.

8. Shared equipment login Attach tags to shared devices or tools. Scanning logs who checked it out and when.

9. Quick link to shared documents Stick a tag on a whiteboard or in a project area, pointing at the shared drive, Notion page, or task board.

On the Go

10. Car Bluetooth and navigation Put a tag on your car mount. Tapping it connects Bluetooth, opens your navigation app, and starts your driving playlist.

11. Luggage identification Drop a locked NFC tag with your contact details inside your luggage. If it’s found, anyone with a phone can identify the owner.

12. Pet ID tag Attach a tag to your pet’s collar with your contact details and their medical info - more durable and data-rich than an engraved tag.

13. Gym and workout launch A tag on your gym bag or locker that opens your workout app with today’s routine loaded.

Creative Uses

14. Restaurant table ordering If you run a restaurant, embed tags in the tables. Customers tap to see the menu, order, or pay. Plenty of places adopted this during COVID and never went back.

15. Interactive art and exhibits Museums and galleries place tags next to pieces so visitors can tap for audio guides, artist notes, or AR experiences.

16. Scavenger hunts and games Hide tags around a location, each revealing a clue or puzzle. Great for team-building, kids’ parties, or escape-room-style games.

NFC Tags and iPhone Shortcuts

This is my favorite thing to show people. Apple’s Shortcuts app (built into iOS) has native NFC trigger support, and it’s where tags go from useful to genuinely powerful on iPhone.

Here’s how to set one up:

1. Open the Shortcuts app

2. Go to the Automation tab

3. Tap New Automation, then NFC

4. Scan the tag you want to use as a trigger

5. Build whatever automation you like

The clever part: the tag doesn’t even need data written to it. Shortcuts recognizes the tag by its unique hardware ID, so a completely blank tag can trigger something complex:

• Start a focus mode and a timer when you tap the tag on your desk

• Log your arrival time to a spreadsheet when you tap the office tag

• Text your partner “on my way home” when you tap the car tag

• Toggle specific smart home devices

On Android, apps like Tasker and MacroDroid do the same kind of NFC-triggered automation.

Common Questions

Do NFC tags need batteries?

No. NFC tags are completely passive - they draw power from the reading device’s field. They never run out and can last a decade or more.

Can NFC tags be hacked?

Standard tags have no encryption by default, so anyone with an NFC phone can read an unlocked, unprotected tag. For most uses - sharing a URL, triggering a shortcut - I don’t consider that a problem. For sensitive applications, use a tag with cryptographic features (like NTAG424 DNA), or make sure the tag only triggers an action that needs further authentication.

How close do I need to hold my phone?

Within about 1-4 cm. On iPhones the NFC antenna sits at the top of the phone; on most Android phones it’s in the upper-middle of the back. You’ll find the sweet spot within a few taps.

Can I rewrite NFC tags?

Yes, as long as the tag hasn’t been locked. Most tags handle roughly 100,000 write cycles, so you can reprogram them as much as you like. Once locked, a tag is permanently read-only.

How much data can an NFC tag store?

It depends on the chip: NTAG213 holds ~144 bytes, NTAG215 ~504 bytes, NTAG216 ~888 bytes. A typical URL is 30-80 bytes. It isn’t much - tags are best for short data or pointers to online content.

Do NFC tags work through cases?

Yes. NFC works through most phone cases, stickers, and thin materials. Very thick or metallic cases can cut the range. If you’re sticking a tag on metal, use one designed for metal surfaces - it has a ferrite shielding layer.

What’s the difference between NFC tags and NFC cards?

Nothing fundamental. An NFC card is just an NFC tag in a card-shaped body - the chip and antenna are the same technology. Cards usually use NTAG213 or NTAG215 and are popular for business cards, access badges, and loyalty programs.

Getting Started: Your First NFC Project

Want to try it? Here’s a five-minute project I’d start anyone with:

Project: a Wi-Fi sharing tag for your home

1. Buy tags: grab a pack of NTAG216 stickers (around $10 for 25)

2. Download NFC.cool Tools: for iOS or Android

3. Write your Wi-Fi credentials: open the app, choose Write, then Wi-Fi, enter your network name and password, and hold your phone to the tag

4. Place the tag: somewhere visible - by the front door, on the fridge, in a guest room

5. Test it: tap with a different phone and you should get a prompt to join the network

Total cost: about $0.30 and two minutes. Every guest who visits will thank you for it.

Wrapping Up

NFC tags are one of those technologies that sound complex and turn out to be remarkably simple. No batteries, no pairing, no app needed for basic reading. A few cents buys a programmable chip that lasts years and works with billions of phones.

I’ve built my work around these little chips, and I still find new uses for them. Whether you want to automate your morning, share your contact details, or build something playful - a tag is the bridge between tapping a phone and making something happen in the real world.

Ready to start programming NFC tags? Download NFC.cool Tools for iPhone or Android - it’s the easiest way I know to read, write, and manage NFC tags.

Want a digital business card powered by NFC? Take a look at NFC.cool Business Card - share your contact with a single tap. The app UI and App Clip are available in 35 languages.

You’re at a conference. You just had a great conversation and want to exchange contact info. Do you pull out your phone and show a QR code? Or do you tap an NFC card against their phone?

It’s a question that comes up a lot in the digital business card world - and most articles answering it are written by companies that sell one or the other. I’ll try to be more honest than that.

The short answer: both technologies are good at different things. The real question is which one fits your networking style - and whether you even need to choose.

How NFC Business Cards Work

NFC stands for Near Field Communication. It’s the same technology that powers contactless payments with Apple Pay or Google Pay. When you hold an NFC-enabled business card (or a phone with an NFC tag written to it) close to another phone, it transmits your contact information wirelessly - no camera needed, no QR code to scan.

The experience: You tap your card or phone against someone’s device. Their phone buzzes, a link opens, and they can save your contact info in seconds.

What You Need

• An NFC-capable smartphone (all iPhones since the XS in 2018, most Android phones since ~2017)

• Either a physical NFC card/tag or an app that can broadcast via NFC

• Close proximity - NFC works within about 4 cm (1.5 inches)

How QR Code Business Cards Work

QR codes have been around since 1994, but they went mainstream during the pandemic when restaurants swapped paper menus for scannable codes. Now they’re everywhere - including business cards.

A QR code business card encodes a URL or contact data into a scannable pattern. The other person opens their phone camera, points it at the code, and taps the link that appears. No app download required.

What You Need

• Any smartphone with a camera (essentially every phone in existence)

• A QR code - either printed on a physical card, displayed on your phone screen, or embedded in an email signature

• A clear line of sight between the camera and the code

Head-to-Head Comparison

Let’s compare NFC and QR code across the metrics that actually matter.

Speed

NFC wins. A tap takes less than one second. QR code scanning requires unlocking your phone, opening the camera, positioning it correctly, and waiting for recognition. It’s still fast - maybe 3-5 seconds - but NFC is near-instant.

In practice, the difference feels bigger than the numbers suggest. NFC feels effortless. QR scanning feels like… scanning something.

Compatibility

QR code wins. QR codes work on every smartphone ever made, as long as it has a camera. That’s close to 100% of phones in circulation. NFC requires an NFC-capable device - and while most modern phones support it, some budget Android phones and older devices don’t.

In 2026, NFC compatibility is high (estimated 85-90% of phones in use), but QR is still more universal.

Works Without an App

Tie. Neither NFC nor QR code requires a special app for the person receiving your info. QR codes open via the built-in camera app. NFC triggers a notification via the phone’s native NFC reader. In both cases, the recipient just taps a link to see your profile.

On the creation side, you’ll typically need an app or platform to set up your digital card - but that’s true for both technologies.

Lighting and Environment

NFC wins. QR codes need the phone camera to “see” the code, which means they struggle in dark rooms, conferences with dim lighting, or when there’s glare on a screen. NFC doesn’t care about lighting at all - it works via radio waves, not optics.

If you do a lot of networking at evening events, dinners, or loud venues where pulling out a phone and scanning feels awkward, NFC has a clear edge.

Distance and Flexibility

QR code wins. QR codes work at a distance. You can print them on a poster, include them in a slide deck, embed them in an email signature, or display them on a screen across the room. NFC requires close physical contact - you need to be within a few centimeters.

For one-to-many sharing (a presentation, a booth, a webinar), QR codes are far more practical.

The “Wow” Factor

NFC wins. There’s something memorable about tapping your card against someone’s phone and watching it pop up. It feels futuristic. It’s a conversation starter. People remember it.

QR codes are functional, but nobody’s ever said “wow, that was cool” after scanning a QR code.

Cost

QR code wins. Generating a QR code is essentially free. You can create one in seconds with any digital business card platform, print it on a regular paper card for pennies, or just display it on your phone.

NFC involves buying either NFC-capable cards (typically $5-$50 per card depending on material) or NFC sticker tags ($1-$3 each). Some platforms lock you into their proprietary NFC hardware, which can cost significantly more.

That said, you don’t need expensive NFC cards. Apps like NFC.cool let you write your business card to any standard NFC tag - even the $1 stickers you can buy on Amazon. You’re not locked into any specific hardware.

Durability and Reliability

NFC wins slightly. NFC tags don’t wear out, fade, or get damaged by coffee stains. A QR code printed on a card can get scuffed or bent to the point where it won’t scan. Digital QR codes (displayed on a screen) don’t have this problem, but physical ones do.

Analytics and Tracking

Tie. Both NFC and QR code platforms typically offer analytics - number of taps/scans, location, device type, etc. The tracking capability depends on the platform, not the sharing technology itself.

When to Use NFC

NFC shines in scenarios where you’re meeting people one-on-one, in person:

• Conferences and events - Tap your badge, card, or phone for instant sharing

• Client meetings - Professional, memorable, and fast

• Networking dinners - Works in low light without the awkwardness of scanning

• Sales teams - Lead capture with a tap (some platforms integrate directly with CRMs)

• When you want to stand out - NFC is still novel enough to make an impression

Best For

Professionals who network frequently in person and want a seamless, premium experience. Especially valuable for sales, real estate, consulting, and anyone who goes to a lot of events.

When to Use QR Codes

QR codes are more versatile for broad, flexible sharing:

• Email signatures - Scannable right from someone’s inbox

• Presentations and webinars - Share with a room of 100 people at once

• Printed materials - Brochures, posters, product packaging

• Trade show booths - Visitors can scan from a distance

• Online profiles - LinkedIn, personal websites, social media bios

Best For

Anyone who shares their contact info in both digital and physical contexts. Especially useful for marketers, speakers, exhibitors, and people who want one consistent sharing method everywhere.

The Smart Answer: Use Both

Here’s what the NFC-vs-QR debate usually misses: you don’t have to choose.

Most modern digital business card platforms support both NFC and QR code sharing. You can tap when you’re face-to-face and show a QR code when you’re not. Same card, same contact info, two sharing methods.

This is actually the approach I’d recommend for most people:

• NFC for in-person interactions - It’s faster, more memorable, and works in any lighting

• QR code for everything else - Email signatures, presentations, printed cards, remote sharing

The key is finding a platform that handles both natively, without making you buy separate products or manage separate profiles for each.

What to Look For in a Platform

If you’re going with the “use both” approach, here’s what matters:

NFC Flexibility

Does the platform lock you into proprietary NFC cards, or can you use any standard NFC tag? Some companies charge $30-$50 for branded NFC cards when a $2 generic tag does the same thing. Look for a platform that lets you write your card to any NFC tag - stickers, keychains, wristbands, whatever works for you.

QR Code Quality

Dynamic QR codes (where the destination URL can be updated) are essential. Static codes become useless the moment your info changes. Make sure the platform generates dynamic codes automatically.

Privacy

This is an overlooked but critical factor. Some platforms use your QR code scans and NFC taps to collect data on the recipients - the people viewing your card. They might get marketing emails from the platform itself, which is a bad look for you and an invasion of their privacy.

Choose a platform that respects both your privacy and your contacts’ privacy.

Language Support

If you network internationally, your card needs to work for people who don’t speak English. Some platforms only support English; others support dozens of languages. This matters more than most people realize - a card that a prospect in Tokyo or São Paulo can’t read is a wasted opportunity.

Pricing

Some platforms charge monthly subscriptions ($5-$15/month) for features that should be basic. Others offer one-time purchases or generous free tiers. Don’t overpay for a digital business card - the technology is mature and shouldn’t cost more than a good lunch.

How NFC.cool Handles Both

Full disclosure: this is my blog, so of course I’m going to mention my own solution. But I think it’s genuinely relevant here.

NFC.cool Business Card was built from the start to support both NFC and QR code sharing - not as separate products, but as two sides of the same card:

• NFC tap - Write your business card to any standard NFC tag (stickers, cards, keychains - your choice) and share with a tap. No proprietary hardware required.

• QR code - Generate a scannable code directly in the app. Display it on your phone or print it.

• Apple Wallet (iOS) - Add your card as a Wallet pass for instant lock-screen access.

• Link sharing - Share via text, email, or social media.

A few things that set it apart:

• 35 languages - The app UI and App Clip support 35 languages, so your card displays in your contact’s language on iOS. The Android sharing website is currently English only.

• Privacy-first - No recipient solicitation, optional PIN protection, no data monetization or advertising

• Open NFC - Works with any standard NFC tag - NFC.cool doesn’t sell proprietary hardware

• Affordable - Personal plan at €20/year, Small Business at €50/year (10 cards), Business at €100/year (100 cards)

➡️ Try NFC.cool Business Card: App Store · Android (inside NFC.cool Tools)

FAQ

Do I need an NFC tag to use NFC sharing?

Yes, if you want the “tap a physical card” experience. But many apps also support phone-to-phone NFC sharing (holding two phones back-to-back). The tag or card just makes it more convenient - you don’t have to pull out your phone at all.

Can old phones scan NFC?

Most smartphones manufactured after 2017-2018 support NFC. iPhones from the XS onward (2018+) support background NFC reading - meaning the phone reads the tag automatically without opening an app. Older phones may not support NFC, which is why having a QR fallback is smart.

Are NFC business cards secure?

Yes. NFC has a very short range (about 4 cm), so someone can’t “steal” your data from across the room. The data on most NFC business cards is just a URL linking to your profile - there’s no sensitive information stored on the tag itself.

How many times can an NFC tag be rewritten?

Standard NFC tags can be rewritten tens of thousands of times. You can update your business card info, write a new profile, or repurpose the tag as many times as you want.

Can I use a QR code and NFC on the same physical card?

Absolutely - and many professionals do. Print a QR code on the back of an NFC-enabled card. That way, you’re covered regardless of whether the other person’s phone supports NFC.

The Bottom Line

NFC and QR code aren’t competitors - they’re complements. NFC is faster and more memorable for face-to-face meetings. QR codes are more versatile for distance and digital sharing. The best digital business card setup uses both.

Don’t get locked into a platform that only does one. And don’t overpay for proprietary NFC hardware when generic tags work just as well.

Choose a platform that gives you both - and that respects your privacy while doing it.

I’ve spent years building NFC.cool, an app for reading and writing NFC tags, so I tend to notice when NFC quietly turns up in the news. The EU Digital Product Passport (DPP) is the biggest example I’ve seen yet - and it caught my attention because the regulation effectively writes NFC into law. If you sell physical products in Europe, or buy them, this is a regulation worth understanding. It’s no longer a future concept. It’s happening right now.

Under the Ecodesign for Sustainable Products Regulation (ESPR), which entered into force in July 2024, every covered product sold in the EU will need a machine-readable digital record containing verified data about its materials, environmental impact, and end-of-life handling.

Batteries are already under the first enforcement wave. Textiles, electronics, and furniture deadlines are approaching fast.

I’m not a lawyer, and this isn’t legal advice - but I do work with the technology at the center of it every day. Here’s my read on what it all means, in plain language, with the regulatory facts kept straight.

What Is a Digital Product Passport?

A Digital Product Passport (DPP) is a structured digital record attached to a physical product. The way I think of it: it’s a product’s complete biography. Where it came from, what it’s made of, how it was produced, and how it should be recycled or disposed of when its life is over.

But it’s not a PDF or a webpage, and that distinction matters. A DPP is a standardized, machine-readable data layer linked to a specific product unit or product model. It’s designed to be read by consumers, regulators, retailers, and recyclers - each seeing the data relevant to them.

How Do You Access It?

Consumers and inspectors access a DPP by scanning a QR code or NFC tag physically attached to the product or its packaging. The scan opens a structured data record hosted on compliant digital infrastructure.

This is the part that made me sit up. A regulation this large is, in practice, going to put an NFC tag on millions of products - and that’s where the technology I work on becomes central to the story. More on that below.

Why Is the EU Doing This?

The DPP exists because Europe’s circular economy goals require radical product transparency. Right now, most products carry minimal information about their environmental footprint. Labels tell you fiber composition or energy ratings, but not the full picture. If you’ve ever tried to find out what’s actually inside something you own, you know how thin that information usually is.

The EU wants to change that with three goals:

1. Consumer empowerment - Let people make informed purchasing decisions based on real sustainability data.

2. Regulatory enforcement - Give market surveillance authorities the ability to verify compliance automatically, not through manual inspections.

3. Circular economy - Provide recyclers and repair services with the information they need to handle products properly at end of life.

The mechanism is the ESPR (EU Regulation 2024/1781), which creates the legal framework. Specific requirements for each product category are defined through delegated acts - separate legal instruments that spell out exactly what data must be included.

The Timeline: What’s Covered and When

The DPP rollout is phased by product category, which I think is the sensible call - one big-bang deadline would have been chaos. Here’s the current schedule as of early 2026:

Already in Force

• Batteries (February 2027 full enforcement) - Industrial batteries over 2 kWh, automotive batteries, and light transport batteries. Over 100 data attributes required, including material composition with geographic origin, carbon footprint by lifecycle stage, recycled content percentages, and state-of-health metrics.

Coming in 2027

• Textiles & Apparel - Fiber composition (all fibers above 1% by weight), chemical treatments, water consumption, worker welfare documentation, and care instructions for durability.

• Electronics & ICT - Material composition, repairability index (EU scoring methodology), spare parts availability, and hazardous substance compliance under REACH.

Coming in 2028

• Furniture - Material composition, durability metrics, disassembly instructions, and material separation guidance.

• Construction Products - Material content, environmental performance data, and recycled content.

• Tyres - Material composition, rolling resistance, and end-of-life information.

More categories are expected through 2030 as additional delegated acts are issued.

What Data Does a DPP Contain?

While requirements vary by product category, certain fields are common across all categories:

• Material composition (by percentage weight)

• Country of origin of manufacturing

• Carbon footprint per unit (expressed as kg CO₂e)

• Recycling and end-of-life instructions

• Repairability or durability index (where applicable)

• Hazardous substance information (REACH compliance)

• Unique product identifier (linked to the physical data carrier)

Here’s the detail I find most interesting: the data isn’t static. DPPs can be updated after the product ships - meaning a brand can push new information (recall notices, updated recycling guidance, software updates for electronics) to products already in consumers’ hands. That only works because the tag points to a record rather than storing everything itself, which is exactly how I’d design it.

Tiered Access

Not everyone sees the same data. Access is structured by stakeholder:

• Consumers see sustainability credentials, care instructions, and recycling guidance.

• Retailers and trade partners see supply chain data and compliance certificates.

• Regulators access the full dataset for market surveillance and automated compliance checks.

• Recyclers access end-of-life processing instructions and material composition details.

NFC’s Role in Digital Product Passports

This is the part I’ve been waiting to write about. For me, NFC has always been a handy consumer tool - a way to automate your home, share a contact, tap a tag and make something happen. The DPP is the moment it becomes critical infrastructure.

The ESPR mandates standardized data carriers for product passports. The three approved technologies are:

1. QR codes - Printed on products or packaging. Universal, cheap, but static and easily damaged.

2. RFID tags - Used in logistics and warehousing. Longer range but require specialized readers.

3. NFC tags - Embedded in products or attached to packaging. Scannable with any modern smartphone.

For consumer-facing products, NFC is emerging as the premium choice - and having built around these chips for years, I’d argue the reasons are solid rather than hype:

Why NFC Fits DPP Better Than QR

• Durability - NFC tags can be embedded inside products (clothing labels, battery housings, electronic casings). They survive washing, wear, and years of use. QR codes on packaging get thrown away. This is the one that convinces me most: a passport that has to last a product’s whole life can’t live on a label that gets binned on day one.

• Tamper resistance - NFC chips can be cryptographically locked, making it harder to forge or duplicate passport data. QR codes can be printed by anyone. Locking a tag is a deliberate, one-way step, and for a regulatory data carrier that’s exactly the property you want.

• Updateable links - NFC tags can point to dynamic URLs, ensuring the passport data stays current throughout the product’s lifecycle.

• No line-of-sight needed - You don’t need to find and frame a QR code. Just tap your phone near the product. On most iPhones from the XS onward, that read happens in the background with no app at all.

• Higher-value positioning - For premium products (luxury textiles, electronics, furniture), NFC signals quality and modernity.

I’ll be honest about the trade-off, though: QR codes remain essential as a fallback and cost-effective option for mass-produced, low-cost items. NFC is not free, and for a disposable item the math doesn’t always work. Most implementations will likely use both - NFC embedded in the product itself, QR printed on the packaging - and I think that’s the right answer rather than a compromise.

Writing NFC Tags for DPP Compliance

If you’re a manufacturer or brand implementing DPP via NFC, you’ll need tools to program NFC tags at scale with the correct URLs pointing to your passport data infrastructure. The underlying mechanics are not exotic - a DPP tag is, at heart, a tag carrying a URL record, the same thing I cover in my walkthrough on how to write NFC tags on iPhone.

This is exactly what apps like NFC.cool Tools are built for. It’s the app I build, and it lets you read, write, format, and lock NFC tags directly from your iPhone or Android device - no extra hardware required. For small-batch production, prototyping, or testing your DPP implementation, it’s the fastest way I know to get tags programmed and verified. If you’re choosing which chip to standardize on, my breakdown of NFC tag types for iPhone covers the practical differences, and for anything that needs the cryptographic locking the regulation rewards, an encrypted, tamper-resistant tag is worth understanding before you commit.

For enterprise-scale deployments, desktop NFC writers (compatible with NTAG, ICODE, and MIFARE chips) handle bulk programming, but the mobile app remains invaluable for field verification - scanning products on the shelf or warehouse floor to confirm the passport link works correctly. You can even check what a tag holds straight from a browser on Android, with nothing to install, which is handy for a quick spot-check.

Beyond the EU: Global Momentum

The EU is leading, but it’s not alone, and I don’t expect this to stay a European story for long.

China

China is developing a parallel state-administered DPP system led by the China Academy of Information and Communications Technology (CAICT). Their focus is on electric mobility and electronics, with a carbon credentialing system intended to reduce trade friction for Chinese exports to Europe.

United States

The US has no federal DPP mandate as of 2026. However, market forces are pushing adoption - especially for brands selling into both US and EU markets. Building DPP infrastructure once for EU compliance and extending it globally is becoming the pragmatic approach.

Global Interoperability

The big challenge ahead is making these systems talk to each other. A product manufactured in China, sold in Europe, and recycled in the US needs a passport that works across all three jurisdictions. Standards bodies (CEN/CENELEC in Europe, ISO/IEC internationally) are working on harmonization, but it’s still early days.

What Should Businesses Do Now?

If your products fall under ESPR categories, here’s the practical action plan I’d follow:

1. Audit Your Data

Start with what you know - and, more honestly, what you don’t. Map your supply chain data against DPP requirements for your product category. The gaps you find now are cheaper to fix than the ones regulators find later.

2. Start with One Product

Don’t try to implement DPP across your entire portfolio simultaneously. Pick one product line (ideally in the earliest enforcement category) and use it as a pilot. Validate your data flow before scaling. I’ve watched enough projects overreach early to believe this one strongly.

3. Choose Your Data Carrier

Decide whether QR, NFC, or both make sense for your product. Consider the product’s lifespan, value, and where the data carrier will be placed. My rule of thumb: for anything consumers keep longer than a year, NFC is worth the investment.

4. Build Updatable Infrastructure

Your DPP needs to last as long as your product does. That means the data must be hosted on infrastructure that will persist, with the ability to update records post-sale.

5. Get Your NFC Tooling Ready

If you’re going the NFC route, get familiar with tag programming before it’s a deadline. NFC.cool Tools supports reading, writing, and verifying NFC tags on both iOS and Android - it’s the app I build, and it’s a practical starting point for testing your DPP tags before committing to bulk production. If you want the bigger picture of what NFC can do beyond passports, my NFC reader and writer feature overview lays it out.

Frequently Asked Questions

Is the Digital Product Passport mandatory?

Yes, for products sold in the EU market that fall under covered categories. The ESPR (EU Regulation 2024/1781) makes it a legal requirement, enforced through CE marking and market surveillance.

When does my product need a DPP?

It depends on your category. Batteries are already covered (2027 full enforcement). Textiles and electronics follow in 2027. Furniture, construction products, and tyres in 2028. Check the latest delegated acts for your specific category.

Does DPP apply to products manufactured outside the EU?

Yes. Any product placed on the EU market must comply, regardless of where it was manufactured. This includes imports.

Can I just use a QR code?

Technically yes - QR codes are an approved data carrier under ESPR. But for durable products, I’d push back: NFC tags offer significant advantages in longevity, tamper resistance, and user experience, and those advantages compound over a product that lives for years.

What happens if I don’t comply?

Non-compliance can result in products being removed from the EU market, seizure by customs, and financial penalties. CE marking requires DPP compliance for covered categories.

How much does DPP implementation cost?

Costs vary widely depending on your product category, data readiness, and chosen infrastructure. NFC tags cost a few cents each at scale, so in my experience the chips are never the expensive part. The bigger investment is in data collection, system integration, and ongoing hosting.

The Bottom Line

In my view, the EU Digital Product Passport isn’t just another regulation to comply with - it’s a fundamental shift in how products communicate their story. For manufacturers, it means more transparency. For consumers, more informed choices. For the planet, better recycling and less waste.

I’ll admit a bias here, since NFC is what I build. But I genuinely think the technology is uniquely positioned to be the physical bridge between products and their digital identities. It’s durable, secure, smartphone-compatible, and already proven at scale - and a regulation this size effectively confirms that the bet was the right one.

Whether you’re a brand preparing for compliance or a consumer curious about what that new NFC tag on your jacket does, the DPP era has begun. And if you’ve never thought much about the chip behind it, my beginner’s guide to NFC tags is the place I’d start.

Need to read, write, or test NFC tags? NFC.cool Tools is available for free on iOS and Android.

Paper business cards are fading fast. Whether you’re networking at a conference, meeting clients, or just want a professional way to share your contact info, a digital business card app is the modern solution.

But with dozens of apps competing for your attention - each claiming to be the best - choosing the right one isn’t easy. Most “comparison” articles are written by the apps themselves (surprise: they always rank #1).

I took a different approach. I actually tested eight of the most popular digital business card apps and compared them across features that matter: pricing, privacy, NFC support, language availability, and ease of use. Here’s what I found.

How I Evaluated

I looked at each app across six key criteria:

• Free Plan Quality - What can you actually do without paying?

• Pricing Fairness - Is the paid tier worth it? Any hidden costs?

• Privacy & Data Practices - Who sees your data? Is there recipient solicitation?

• NFC Support - Can you use NFC tags or cards? Are you locked into proprietary hardware?

• Language Support - Does the app work for non-English speakers?

• Ease of Use - How quickly can you set up and share a card?

I also noted whether each app’s free plan includes platform branding (their logo on your card) or solicits your recipients (sends marketing emails to people who view your card).

Quick Comparison

Here’s an at-a-glance overview of all eight apps:

NFC.cool Business Card

• Free plan: Yes (with branding)

• Starting price: €20/year (Personal, 1 card)

• NFC support: Works with any NFC tag

• Languages: 35 (app UI + App Clip)

• Privacy PIN: Yes

• Recipient solicitation: No

Wave Connect

• Free plan: Yes (generous, no branding)

• Starting price: $7/month

• NFC support: Proprietary cards only

• Languages: Limited

• Privacy PIN: No

• Recipient solicitation: No (on free plan)

Blinq

• Free plan: Yes (with branding)

• Starting price: ~$9.99/month

• NFC support: Proprietary cards

• Languages: Limited

• Privacy PIN: No

• Recipient solicitation: Yes (on free plan)

HiHello

• Free plan: Yes (4 cards)

• Starting price: $6/month (annual)

• NFC support: No hardware offering

• Languages: Limited

• Privacy PIN: No

• Recipient solicitation: Yes (on free plan)

Popl

• Free plan: Basic (via app)

• Starting price: Custom/enterprise

• NFC support: Proprietary stickers and cards

• Languages: Limited

• Privacy PIN: No

• Recipient solicitation: Varies

Mobilo

• Free plan: No

• Starting price: ~$4/month + hardware

• NFC support: Proprietary cards (core product)

• Languages: Limited

• Privacy PIN: No

• Recipient solicitation: N/A

Linq

• Free plan: Limited

• Starting price: Varies (card + subscription)

• NFC support: Proprietary cards

• Languages: Limited

• Privacy PIN: No

• Recipient solicitation: N/A

V1CE

• Free plan: No (hardware purchase required)

• Starting price: $197 (flat, one-time)

• NFC support: Premium physical cards

• Languages: Limited

• Privacy PIN: No

• Recipient solicitation: No

Detailed Reviews

1. NFC.cool Business Card - Best for Privacy & Multilingual Professionals

What it is: A digital business card app from NFC.cool, the indie studio behind 13 NFC and utility apps with over 9 million downloads. Available as a standalone app on iOS and as part of NFC.cool Tools on Android.

What I like:

• 35 languages - the app UI and App Clip are available in 35 languages, making it by far the most multilingual digital business card on the market. If you work internationally, this matters.

• Privacy-first design - PIN-protected profiles (4-digit PIN with rate limiting), public/private toggle, GDPR-compliant data export. No data monetization or advertising, no conversation recording, no recipient solicitation.

• Works with any NFC tag - NFC.cool doesn’t sell NFC tags, and you’re not locked into buying proprietary hardware. Write your card URL to any third-party NFC tag, sticker, or card you already own.

• Up to 100 cards - Create different cards for different roles, events, or clients.

• Conference Mode (Live Activity) - This is a standout feature. An iOS Live Activity puts your QR code directly on your lock screen - always visible, ready to scan, no unlocking or opening any app needed. This is actually more useful than Apple Wallet integration because the QR code linking to your business card is right there on the lock screen. At a conference, you just raise your phone and people scan. No fumbling with Wallet, no searching for the right pass.

• Beautifully designed - The app and card-sharing experience are thoughtfully crafted with custom color theming, company logos, and a polished App Clip on iOS that looks and feels native.

• App Clip + web sharing - On iOS, recipients see a native App Clip experience without needing the app. On Android, recipients open a website on the nfc.cool domain - no app needed either. Both show a “Save Contact” button for easy saving.

• Apple Wallet integration - Also available as an alternative for those who prefer Wallet-based access.

• Lead capture - Available on iOS (with options to trigger before saving, after saving, or turned off). Android support coming soon.

What could be better:

• Some advanced features (analytics, lead capture, Conference Mode, custom themes) are iOS-only for now, with Android support coming soon.

• No CRM integrations or webhooks yet - iOS offers CSV export for contacts. For most individuals and small teams, this is sufficient.

• As a newer entrant, it doesn’t have the enterprise sales team that Blinq or Popl have.

Best for: Privacy-conscious professionals, international networkers, anyone who wants NFC flexibility without hardware lock-in, indie/small business users who appreciate transparent development.

Download NFC.cool Business Card on the App Store · Get it on Android (inside NFC.cool Tools)

2. Wave Connect - Best Free Plan

What it is: A digital business card platform founded in 2020 that’s become one of the most visible players through aggressive SEO and content marketing.

What I like:

• Genuinely generous free plan - QR sharing, Apple/Google Wallet pass, unlimited contacts, analytics, and contact export. All free. No platform branding on your card. This is hard to beat.

• SOC 2 Type II certified - Enterprise-grade security compliance.

• Apple App Clip sharing - Tap and share without the recipient needing an app.

• Easy setup - Clean onboarding that gets you sharing within minutes.

What could be better:

• You can only create one card profile - no switching between personal and business cards.

• No payment link integrations (Venmo, Cash App).

• No Android widgets.

• Limited language support compared to NFC.cool’s 35 languages.

• NFC cards are available for purchase but are proprietary - you can’t use your own tags.

Best for: Individuals who want a solid digital business card without paying anything. If budget is your #1 concern, Wave’s free plan is the one to beat.

3. Blinq - Best for Enterprise Teams

What it is: An Australian company that claims the #1 spot on G2 for digital business cards, lead retrieval, and email signatures. Strongly enterprise-focused.

What I like:

• AI-powered features - Contact enrichment (automatically finds LinkedIn, company info) and a universal scanner that reads badges, cards, QR codes, and LinkedIn profiles.

• AI Notetaker - Transcribes notes from meetings (though this raises privacy questions - see below).

• Email signature management - A nice addition if your company needs consistent branding.

• SOC 2 Type II & GDPR compliant.

What could be better:

• Free plan includes platform branding - Blinq’s logo appears on your card.

• Free plan solicits recipients - When someone views your free-tier card, Blinq may send them marketing. This is a dealbreaker for many professionals.

• Privacy concerns - The AI Notetaker and conversation recording features raise real questions about consent and data handling. Who has access to those recordings?

• Higher individual pricing (~$9.99/month) compared to competitors.

Best for: Enterprise teams (50+ people) that need centralized card management, CRM integration, and don’t mind the data collection trade-offs.

4. HiHello - Strong Customization

What it is: A digital business card app with customization options and enterprise features.

What I like:

• Good customization - HiHello offers decent card design options, though NFC.cool Business Card’s App Clip experience and custom color theming are equally polished.

• Good free tier - 4 cards, email signature, QR sharing, and virtual backgrounds included free.

• Virtual backgrounds - Ready-made backgrounds for Zoom/Teams calls with your card info. A clever touch.

• Strong enterprise directory sync - Integrations with Workday, Okta, and Entra ID for large companies.

What could be better:

• Analytics and contact export are locked behind paid plans.

• Free plan solicits recipients.

• No NFC hardware offering at all - purely digital.

• Limited language support.

Best for: Design-conscious professionals who prioritize how their card looks. Good for companies that want polished, on-brand cards.

5. Popl - Best for Event Lead Capture

What it is: Originally an NFC sticker company, Popl has pivoted heavily toward enterprise event lead capture. Claims to be “trusted by 90% of Fortune 500.”

What I like:

• Event lead capture is strong - Badge scanning, lead qualification, enrichment, and real-time CRM sync.

• ROI attribution - Track which events and interactions lead to deals.

• Custom NFC cards available.

What could be better:

• Pricing is completely opaque - Individual plans redirect to the app store, team plans require “booking a demo.” This is frustrating.

• Free plan is extremely limited (max 5 contacts).

• The product has clearly shifted toward enterprise event teams, leaving individual users behind.

• No free analytics.

Best for: Enterprise event and sales teams who need lead capture at scale. Not recommended for individual professionals anymore.

6. Mobilo - Best NFC Hardware Experience

What it is: An NFC-first digital business card company where the physical card is the core product, paired with a digital platform.

What I like:

• NFC hardware is excellent - Well-made physical cards, stickers, and tags.

• Lead tracking dashboards - Useful CRM-like features built in.

• SOC 2 Type II certified.

What could be better:

• No free plan - You must buy hardware and subscribe to use the platform.

• Hardware lock-in - You can only use Mobilo’s NFC products, not your own tags.

• Expensive to get started (card purchase + monthly subscription).

Best for: Professionals who want a premium physical NFC card and are willing to pay for a polished hardware + software combo.

7. Linq - Best for Sales CRM Integration

What it is: A digital business card platform with integrated CRM and even a phone system, aimed at sales professionals.

What I like:

• All-in-one sales tool - Card + CRM + phone system is genuinely useful for sales-heavy roles.

• Physical NFC cards available in various styles.

What could be better:

• Over-engineered for most users who just need a business card.

• Can be confusing for less tech-savvy contacts on the receiving end.

• Costs add up quickly when bundling features.

Best for: Sales professionals who want their business card, CRM, and calling in one platform.

8. V1CE - Best Premium Physical Cards

What it is: A UK-based company specializing in premium NFC business cards made from metal, wood, and other luxury materials.

What I like:

• Stunning physical cards - If first impressions matter (and they do), a metal or wooden NFC card is a conversation starter.

• Simple flat pricing - $197 one-time, no subscription.

• No recipient solicitation.

What could be better:

• No free option - this is a premium product.

• The digital platform behind the card is basic compared to competitors.

• Limited customization after purchase.

Best for: Professionals who want a luxury physical card that makes a statement. Executives, luxury real estate agents, high-end consultants.

The Privacy Question

This deserves its own section because it’s something most comparison articles conveniently skip.

When you share a digital business card, you’re not just giving someone your contact info - you’re also choosing who gets access to the interaction data. Some things to consider:

Recipient solicitation is when a platform sends marketing emails to people who view your card. Blinq and HiHello do this on their free plans. Wave Connect and NFC.cool do not. If you hand someone your business card and they start getting spam from your card provider, that reflects poorly on you.

Conversation recording features (like Blinq’s AI Notetaker) create privacy and consent issues, especially under GDPR and similar regulations. Make sure you understand what’s being recorded and who can access it.

Data collection practices vary widely. NFC.cool takes a privacy-first approach with PIN-protected profiles, public/private toggles, and GDPR-compliant data export. Others collect more data to power AI features - which can be useful, but comes with trade-offs.

If privacy matters to you (and in 2026, it should), ask these questions before choosing an app:

1. Does the free plan include branding or solicitation?

2. What data is collected about my recipients?

3. Can I export or delete my data?

4. Is the company transparent about its practices?

Pricing Overview

Pricing changes frequently, so always check the latest on each app’s website. Here’s what I found as of March 2026:

• NFC.cool - Free tier available; Personal at €20/year (1 card), Small Business at €50/year (10 cards), Business at €100/year (100 cards)

• Wave Connect - Free (generous); Pro at $7/month or $59/year; Teams at $60/user/year

• Blinq - Free (with branding); Premium ~$9.99/month; Business $4.99/user/month (min 5)

• HiHello - Free (4 cards); Professional $6-8/month; Business $5-6/user/month

• Popl - Free (very basic); Teams/Enterprise require demo booking

• Mobilo - No free plan; ~$4/month + hardware purchase

• Linq - Varies by card type + subscription tier

• V1CE - $197 flat (one-time, no subscription)

Who Should Choose What?

“I want the best free option” → Wave Connect. Their free plan is genuinely generous with no branding and free analytics.

“I work internationally and need multilingual support” → NFC.cool Business Card. 35 languages, no other app comes close.

“Privacy is my top priority” → NFC.cool Business Card. PIN protection, no solicitation, no conversation recording, GDPR data export.

“I need this for my entire company (50+ people)” → Blinq or HiHello. Both have strong enterprise features, SSO, and directory sync.

“I attend a lot of events and need lead capture” → Popl. They’ve built their entire product around event lead capture.

“I want a premium physical NFC card” → V1CE for luxury materials, Mobilo for a good hardware + software combo.

“I want NFC but don’t want to buy proprietary hardware” → NFC.cool Business Card. Write your card URL to any NFC tag you own.

“I want to look professional above everything” → HiHello. Good customization with enterprise features, though NFC.cool Business Card matches it on design quality.

Final Thoughts

There’s no single “best” digital business card app - it depends on what you value most. What I can say is that the market has matured significantly, and you have real choices now.

If you value privacy, multilingual support, and NFC flexibility, NFC.cool Business Card stands out as the most thoughtful option in the space. Built by an indie developer (not a VC-funded growth machine), it prioritizes the features that actually matter for day-to-day professional networking.

If you want the best free experience, Wave Connect’s generous free tier is hard to argue with.

And if you need enterprise-scale deployment, Blinq and HiHello both offer solid team management tools.

Whatever you choose, ditch the paper cards. It’s 2026 - your business card should be as smart as the rest of your workflow.

Ready to try NFC.cool Business Card? Download it free on the App Store or get it on Android inside NFC.cool Tools.

In 2025 I gave my first conference talk, and I picked a topic I’d spent years living inside but had never had to explain to a room: how the App Clip behind NFC.cool Business Card actually works. The talk was at mDevCamp 2025 in Prague, and I gave it the same title as this post.

If you haven’t run into one, an App Clip is the small piece of an iOS app that opens instantly from an NFC tap or a QR scan - no App Store, no install. It’s what lets someone see your NFC.cool business card about a second after you tap phones, without downloading anything. Making that feel instant, while still keeping shared-card data secure and not forcing anyone to sign up, takes more architectural decisions than it looks like from the outside. The talk walked through them: how the App Clip is structured, where SwiftUI earns its place, and how the backend handles the card data.

Explaining it from a stage was good for me. It made me justify choices I’d mostly made on instinct, and the questions afterward - from iOS developers who had clearly fought the same fights - were sharper than any code review. The shape I’d settled on, App Clips with SwiftUI and a secure backend API, held up to that scrutiny, and a couple of suggestions from the hallway conversations have already made it into the app.

You can watch the full talk on Slideslive.

I’ve spent years building NFC.cool, an app for reading and writing NFC tags, and there’s one question that lands in my inbox more than almost any other: “Why won’t my iPhone open my condo door?” Someone confidently taps their phone on the building’s entry reader, expects the magic to happen, and gets the cold, indifferent silence of a locked door instead.

If that’s you, you’re in good company - and no, Siri isn’t holding a grudge. The honest answer is simpler and more technical than most people expect: your condo’s card isn’t playing by your iPhone’s rules. Let me explain why, because once you see the frequency mismatch underneath, the whole thing stops feeling like a glitch.

The tech talk, without the geek-speak

When people ask me this, I always start by separating two terms that get used interchangeably but really shouldn’t be:

• RFID (Radio-Frequency Identification) is a broad technology used to wirelessly identify and track objects. I think of RFID like shouting across the street to a friend - typically a one-way exchange where your condo’s RFID card broadcasts a signal and the door listens. RFID comes in different flavours: low-frequency (LF), high-frequency (HF), and ultra-high-frequency (UHF). It powers access cards, pet microchips, inventory tracking, and yes, those condo cards.

• NFC (Near-Field Communication) is essentially a specialised subset of RFID operating at high frequency (13.56 MHz). It’s a cosy chat between two friends standing very close to each other. NFC enables two-way communication, secure data exchange, and rich interaction - which is exactly why your iPhone uses NFC for features like Apple Pay, AirTags, and digital business cards.

So all NFC is RFID, but not all RFID is NFC. That single sentence is the root of almost every “why won’t it work” email I get. If you want the fuller breakdown of how NFC fits inside RFID, I covered it in my beginner’s guide to NFC tags.

Why your iPhone says “no” to your condo card

Here’s the part I’ve had to explain hundreds of times. Your condo access card most likely uses a form of RFID that sits outside the NFC standard your iPhone recognises - often low-frequency RFID, or a proprietary high-frequency scheme encrypted in ways iPhones can’t interpret. Apple deliberately built the iPhone to work exclusively with NFC at 13.56 MHz for security, battery efficiency, and a consistent user experience.

Put plainly: your iPhone doesn’t speak your condo’s RFID dialect. It’s like expecting your Netflix subscription to get you into a cinema. Same general idea, completely different worlds. And this isn’t a bug I could patch around in my own app either - the radio on the inside of the phone simply can’t tune to the frequency that card is talking on. If you’re curious about exactly what Apple did and didn’t open up in the NFC stack, I wrote about it in an insider’s look at NFC on iPhones.

Can you clone or copy the condo card to your iPhone?

In short: no, and I’ve stopped being shy about saying so. Apple’s Wallet and NFC stack are deliberately locked down to avoid the obvious security nightmares - someone casually copying your credit card or your building key onto a phone. Picture a world where anyone could clone access cards onto an iPhone: your lobby turns into a revolving door. Apple’s limitation here exists to keep your digital life safe, and as someone who works with this stack every day, I’d make the same call.

It’s also worth knowing that the cards which can hold secrets - the ones with real cryptographic protection - aren’t trivial to copy by design. I dug into that side of things in keeping secrets safe on encrypted NFC tags.

What you can do instead

Apple isn’t budging on this anytime soon, so here’s how I’d suggest making peace with the RFID reality:

• Smartphone-compatible systems. Ask your condo administration about upgrading to modern access systems that integrate with digital wallets. This is the real fix, and it’s becoming more common every year.

• NFC stickers or tags. Programmable NFC tags are genuinely useful at home and in controlled scenarios - I use them constantly - but they only help here if your condo’s reader actually speaks NFC. If you want to try, writing your own NFC tags on iPhone is the place to start.

• Dedicated RFID cards or fobs. For now, keep that condo card on your keyring. It’s still the right tool for that particular lock.

Bottom line

It’s not your iPhone being stubborn - it’s Apple prioritising security and consistency, and a frequency gap that no software update can close. Until buildings broadly adopt NFC-compatible access systems, that piece of plastic stays your key to the lobby. Your iPhone is brilliant for payments, digital business cards, and impressing your friends - but condo doors are, for now, still stuck in the past.

At least the next time you’re stuck in an awkward elevator ride, you’ve got a good story about why.

NFC tags are small integrated circuits that store information any NFC-enabled device, like your phone, can read. But here’s the thing I wish someone had told me earlier: not all NFC tags are created equal. There’s a whole zoo of types from different manufacturers, each with its own quirks, and that makes picking the right one for your iPhone surprisingly fiddly.

I’ve spent years building NFC.cool, an app for reading and writing NFC tags, and “which tag should I buy for my iPhone?” is easily one of the questions I field most. So this is the answer I give. I’ll walk through the five NFC tag types, who actually makes them, and why one of them is the safe bet for almost any iPhone project. If you’re brand new to all of this, you might want to start with my complete beginner’s guide to NFC tags first - this post goes a layer deeper.

Understanding NFC tag types

NFC tags fall into five types: Type 1, Type 2, Type 3, Type 4, and Type 5. That classification isn’t something manufacturers made up - it comes from the NFC Forum, the industry consortium that sets the standards. Each type has its own memory capacity and speed, and can be either read-write or read-only.

That’s the lens I use whenever I look at a tag’s spec sheet, so let me go through them one by one.

Type 1 & 2 - Topaz and MIFARE Ultralight®

Type 1 (Topaz, by Broadcom) and Type 2 (MIFARE Ultralight®, by NXP Semiconductors) are the cheap, cheerful end of the spectrum. They’re well suited to simple applications like posters and business cards. Their memory capacity is small (48 bytes to about 2 KB), but in my experience that’s plenty for a URL or a short text payload, which is what most people actually want.

Type 3 - FeliCa™

Type 3 tags, also known as FeliCa™, were developed by Sony. You’ll mostly see them in Asia, powering public transport tickets and e-money. They offer higher speed and memory (up to 1 MB), but their use is fairly limited because they cost more and are tied to region-specific applications. I rarely reach for them outside that context.

Type 4 - MIFARE DESFire®

MIFARE DESFire® tags, also from NXP Semiconductors, are Type 4. These are the high-security, high-capacity option, built for complex jobs like secure access control and public transport systems. They can store up to 8 KB. When a project genuinely needs cryptographic protection, this is the family I look at - I went into the security side in more detail in my post on keeping secrets safe on encrypted NFC tags.

Type 5 - ISO 15693

Type 5 tags conform to the ISO 15693 standard and are relatively new to the NFC ecosystem. They’re mostly an industrial story, and their headline feature is an extended read range compared to the other types. Useful if you’re tracking inventory across a warehouse, less so for the tag stuck to your fridge.

Which NFC tags should you choose for your iPhone?

Here’s the part that matters most. iPhones from iPhone 7 onward are compatible with NFC Type 1, 2, and 5, but they offer the best support for Type 2. Type 2 NFC tags are the NTAG series from NXP Semiconductors.

The NTAG213, NTAG215, and NTAG216 models are the most popular in that series, and they work brilliantly with iPhones - it’s what I test against day in, day out. They give you enough memory (144 to 888 bytes) for most practical projects, they’re fully writable and readable by any NFC-enabled iPhone, and they’re rewritable, so you can change their contents as often as you like.

One practical note that has saved me a lot of frustration: the larger the tag and its antenna, the more reliably an NFC reader picks it up. I’d avoid the extremely cheap, flimsy stickers if reliability matters for your project - the few cents you save aren’t worth a tag that only reads on the third tap.

The main thing iPhones do with NFC is read NFC Data Exchange Format (NDEF) messages - URLs, plain text, or vCards (digital business cards). Any tag that supports NDEF, and most NTAG-series tags do, is a solid choice for iPhone users. When you’re ready to actually put data on one, I wrote a step-by-step walkthrough on how to write NFC tags on iPhone.

Summary

If you’re shopping for NFC tags to use with your iPhone, my honest recommendation is simple: Type 2 tags from the NTAG series by NXP Semiconductors. They’re cost-effective and they give you the best compatibility and functionality for what most people actually want to do with NFC on iPhones. Buy a pack of NTAG215 stickers and you’ll be set for almost anything.

NFC keeps evolving, so it’s worth keeping half an eye on new developments and tag specifications. For more, see my earlier post on tapping into the magic of NFC on iPhones, and if you just want to see what’s already on a tag, you can read NFC tags right from your browser.

Happy tagging!

After years of building digital business card software, there was one problem that kept bothering me: we’d solved the wrong half.

The paper-card problem is real - cards go stale, fill your wallet, get lost, can’t be updated. Digital cards fixed that. But they didn’t fix the actual networking problem, which is much simpler:

I meet 50 people at a conference, exchange info with 20, and three weeks later I cannot remember a single conversation.

The contact details on your phone are useless if you can’t remember why that person is in your address book.

Context is the missing piece

So I added what I’ve been calling the “memory upgrade” to NFC.cool Business Card. Right after connecting - via the NFC tap, the App Clip, or the Conference Mode lock-screen QR - you get prompted to capture context:

• Where and when you met. Auto-populated with date and place, editable.

• What they’re working on. A short note about their project, company, or focus area.

• Conversation highlights. The one or two things you actually talked about that you’d want to remember.

• Follow-up plans. “They’re sending an intro to their VC.” “Should send the deck on Monday.”

That last bit syncs into your calendar and reminders, because we’re all bad at follow-through and we all need the nudge.

Why it’s part of the exchange, not after

The trick is that the prompt appears immediately after the contact is saved - while the conversation is still fresh in your head. Five minutes later you’ve moved on to the next person. Three days later you don’t remember whether the AI founder was the one from the Austin pitch competition or the Berlin hackathon.

Capturing the context in the same flow as the contact exchange means the data is actually written down. The alternative - adding context manually next week from memory - never happens.

What it changed for me

During beta testing across a few events, the experience shifted from “I have these business cards in my phone now” to “I have a queryable graph of people, what they do, and what I owe them”.

I open the Networking tab in NFC.cool Business Card and see: who I met where, what we talked about, what I said I’d follow up on, what’s still open. After meeting someone again, I update the entry - new conversation, new context. The card becomes a living record of the relationship, not a snapshot of contact details.

Works across the stack

The Smart Context layer works regardless of how the contact got into your address book:

• NFC tap. Standard flow - you tap their card, save the contact, capture context.

• App Clip. iOS recipients see the App Clip overlay, save the contact, and get the same context prompt.

• Conference Mode (lock-screen QR). Show your lock-screen QR for fast exchange in noisy environments; the same context prompt fires once they save.

• Android browser. Android recipients open the web page version, save the contact, and can capture context inside the NFC.cool Business Card app afterwards.

The app handles up to 100 different cards (different roles, different events, different versions of you) and the Smart Context data stays separate per card - so a contact you met as “design consultant at the Berlin meetup” is a different record from the same person you met as “co-founder at the YC demo day”.

Why this matters now

The reason this didn’t exist five years ago is that the bottleneck wasn’t tech - it was friction. Capturing context required pulling out a separate notes app, typing while the other person watched, and then somehow associating those notes with the contact later. Most people gave up.

With NFC.cool Business Card, the capture is one tap inline with the contact exchange. It’s the difference between “I should remember this” and “this is now remembered”.

In a world where we trade contacts faster than ever, the data that matters isn’t who you know - it’s why you know them.

Download NFC.cool Business Card for iPhone. Android users get the same business card and Smart Context features bundled into NFC.cool Tools for Android.

When NameDrop arrived in iOS 17, a few people asked me the same thing: does this kill the NFC business card? I build a digital business card app, so it was a fair question to put to me - and I didn’t mind it, because NameDrop genuinely is lovely.

You bring two iPhones close, a small animation plays, a soft haptic taps, and a contact moves from one phone to the other. It is exactly the kind of polished little interaction Apple is good at. I have used it plenty. It works, and it feels nice.

But I have watched enough people try to swap details in the real world to know where it stops being enough.

NameDrop is iPhone to iPhone. That is the whole story. The moment the person across the table is holding an Android phone - and globally, most people are - the elegant animation has nothing to connect to. At a conference, a client dinner, a property viewing, you don’t choose what the other person carries. A contact-sharing method that only works when both sides happen to own the right phone isn’t really a method. It is a happy accident.

An NFC business card doesn’t care what the other phone is. It runs on the open NFC standard that both iOS and Android have read for years. The other person taps it, or scans its QR code, and your details land on their phone - whether that phone is an iPhone or not, and whether or not they have any app installed. No gesture to learn, no feature to switch on, no operating system to match.

That is the unglamorous reason I still build around NFC rather than NameDrop. NameDrop optimizes the best case: two iPhone users, both with the feature enabled, both knowing the gesture. NFC optimizes the case that actually happens at an event - two people, two phones, and no shared assumptions about either. NameDrop is the better demo. NFC is the better business card.

Want one? Get NFC.cool Business Card on iPhone, or use the bundled business card in NFC.cool Tools for Android.

A paper business card is a frozen artefact. The minute your job title changes, your phone number changes, or you move agencies, every card in someone’s wallet becomes wrong information about you.

The NFC.cool digital business card flips that around: one URL that you control, written to an NFC tag (or a QR code, or both). You edit your details on your phone, and every existing tag updates instantly. Here’s how to set it up.

Install the app

Download NFC.cool for iPhone or Android. The business card feature is bundled into NFC.cool Tools on both platforms - no separate purchase, no separate download.

Build the source contact in Contacts

Open the iOS Contacts (or Android contacts) app and create a contact for yourself with the details you want available to the world: name, organisation, job title, work email, work phone, website, LinkedIn URL. Double-check spelling and formatting - this is the master record.

You don’t need to put everything in. Anything sensitive (personal mobile, home address) can stay off this contact entirely.

Open NFC.cool and create the business card

Inside NFC.cool, navigate to the Business Card section and tap Create Account. You’ll set a username and PIN - the PIN is what protects future edits, so don’t lose it.

Tap Open Contacts and select the contact you just built. NFC.cool pulls the data in and shows it as your draft business card.

Pick which fields are public

This is the most important step. You can untick any field you don’t want shared - if your Contacts entry has a personal mobile number you’d rather keep private, untick it here and it won’t appear on your shared card.

Common loadouts:

• Sales: name, title, work phone, work email, company, LinkedIn.

• Engineering: name, title, work email, GitHub, website.

• Creative: name, title, Instagram, portfolio URL, work email.

Tap Next when you’re done.

Customise the logo

Tap Your logo → Change logo to upload your company logo or personal mark. Transparent PNG gives the cleanest result - it composites correctly on both light and dark themes.

Write the URL to an NFC tag

Now the physical side. You can buy an NFC tag from the NFC.cool shop or any third-party retailer - sticker, card, keyring, whatever form factor fits.

In NFC.cool, tap Write business card to NFC tag. Hold your phone against the tag. The app writes a short URL pointing at your card page on nfc.cool. Once it’s written, anyone with a phone can tap it.

If you want to lock the tag so no one can overwrite the URL later, tap Lock after the write succeeds. This is irreversible - only lock tags you’re sure about.

Preview before sharing

Tap View Business Card to see exactly what a recipient sees. The page is mobile-first, loads instantly, and offers a one-tap “Save to Contacts” button. On iOS, recipients see a native App Clip (no app install required); on Android they see a clean web page on the nfc.cool domain. Both end up with your contact in their address book.

Why this beats a vCard QR

The classic alternative is a QR code with a vCard embedded directly. It works without any service in the middle - the QR encodes the contact data itself.

The trade-off: it can’t be updated. Print 500 cards, change your job, and you’ve got 500 cards with stale data.

The NFC.cool flow keeps your contact details on the server. The tag (or QR) just points at the URL. You change your details once in the app; every tag everyone has ever tapped now resolves to the updated info.

That’s the only feature that matters for serious networking - the data outlasts the printed card.

NFC.cool Tools (iPhone) · NFC.cool Tools (Android) · or the standalone NFC.cool Business Card for iOS.

NFC.cool Tools is now available on the Google Play Store. After years on iOS, the Android version is live - and it ships with the bundled NFC.cool Business Card built in.

What’s in the Android app

The Android version focuses on the core NFC surface that’s shared across both platforms:

• Read NFC tags. Any NDEF-formatted tag, any record type - URL, vCard, Wi-Fi, plain text, custom MIME.

• Write NFC tags. Compose any record type and write to blank tags. Lock when you’re done if the tag is going somewhere public.

• NFC.cool Business Card (bundled). The Android edition includes the business card flow as a feature inside the app - create a card, write it to a tag, share it with one tap. Recipients on iOS see an App Clip; recipients on Android open a web page on the nfc.cool domain.

What’s iOS-only (for now)

A few features in NFC.cool Tools rely on Apple hardware that has no Android counterpart - the LiDAR sensor for 3D scanning and room scanning, the Vision framework for document scanning, and the system QR scanner that lives behind the Camera app. Those stay iOS-only.

The NFC reading and writing surface, however, is identical. Anything you can do with a tag on iPhone, you can do on Android.

Why we held back

Android has had NFC support since 2012, longer than iPhone. So why did the Android app take so long?

The honest answer: we wanted the NFC.cool Business Card flow to work cross-platform before launching on Android. That meant designing the App Clip + web fallback so an iOS user and an Android user could exchange cards without either side caring what phone the other one carried. Once that was working, Android became a viable launch.

Where to get it

• Android: Google Play

• iOS: App Store

Same brand. Same feature set for the parts that share hardware. The plan from here is to keep both platforms shipping in lockstep on anything NFC-related.

A few years ago, 3D scanning meant a dedicated scanner the size of a microwave, plus software that cost more than the hardware. Today an iPhone with a LiDAR sensor and Apple’s Object Capture API can produce a useable 3D model from a handful of photos.

NFC.cool Tools’ 3D Scan feature wraps that pipeline into a pocketable workflow.

What’s actually happening

Two technologies work together:

• Photogrammetry - The app captures dozens of photos of the object from different angles. A photogrammetry engine (Apple’s Object Capture API on iOS) finds matching features across the photos and triangulates them into a 3D mesh.

• LiDAR - On iPhones with a LiDAR sensor (Pro models from iPhone 12 onwards), each frame is augmented with depth measurements taken by the sensor. This sharply improves the mesh in two ways: scale is accurate (the model is the real-world size), and surfaces without obvious visual features (a plain white wall, a glossy curve) get usable geometry where photogrammetry alone would fail.

You don’t have to think about either step - the app guides you through capture, then runs the reconstruction on-device.

How to capture a good scan

A few practical rules:

• Move slowly around the object. The app expects roughly continuous coverage. Don’t jump from one side to the opposite side - walk around.

• Keep the object in frame. A consistent margin around the object is fine; cutting it off at the edges loses data.

• Even lighting. Hard shadows confuse the photogrammetry stage. Diffuse light (open sky, a softbox, daylight indoors) gives the cleanest mesh.

• Textured objects scan better than featureless ones. A patterned mug scans almost perfectly. A polished metal sphere is genuinely hard. LiDAR helps with the latter but won’t completely save it.

• Stand still for a moment at each angle. Motion blur eats detail.

The full scan takes 20-40 seconds of walking, then another 30-60 seconds of processing.

Export formats

NFC.cool Tools exports to the formats you actually need downstream:

• .stl - 3D printers. Slicers like Bambu Studio, Cura, PrusaSlicer all accept it.

• .obj - Universal 3D format. Imports into Blender, Cinema 4D, Unity, Unreal, basically every modelling tool.

• .ply - Mesh format that preserves vertex colours - useful when texture matters more than UV-mapped materials.

• .usdz - Apple’s AR format. Drop into Quick Look, AR Quick Look, or use in RealityKit.

• .abc (Alembic) - Animation pipelines.

• .usd - Universal Scene Description, supported by most modern DCC tools.

The model is the same. The format just decides which downstream tool can consume it.

What you can do with the result

The most fun applications I’ve seen from users:

• 3D print a one-off replica. Scan a found object, slice, print.

• Document a real-world asset. Estate documentation, museum cataloguing, “what does grandma’s vase actually look like”.

• Share in AR. Send the .usdz to someone on an iPhone - they tap it and see the object floating in their living room via AR Quick Look.

• Drop into a game engine. A real-world prop in a Unity scene, modelled in 90 seconds without a 3D artist.

When it works, and when it doesn’t

Photogrammetry plus LiDAR is strong on:

• Solid, opaque objects

• Textured or patterned surfaces

• Static subjects (anything that doesn’t move during the scan)

It struggles on:

• Transparent or refractive objects (glass, water, lens)

• Highly reflective metal

• Very thin features (cables, wire, hair)

• Anything that moves

For the things it’s good at, the result is genuinely useful - not a toy. For the rest, expect to clean up the mesh in Blender or accept the limits.

3D Scan is part of NFC.cool Tools for iPhone. Apple’s Object Capture needs a LiDAR sensor, so it runs on the Pro iPhones (iPhone 12 Pro and later) and iPad Pro models (2020 and later).

A modern iPhone has enough camera and processing power that “scanning a document” is no longer a printer feature - it’s a tap. NFC.cool Tools’ document scanner is built on Apple’s Vision framework, which means you get fast capture, automatic edge detection, and OCR that runs entirely on-device.

Here’s how to use it well.

Capture: hold steady, light matters

Open NFC.cool Tools, tap the document icon, and frame the page. The scanner draws a yellow quad around what it thinks the page edges are. Most of the time it’s right. When it isn’t, drag the corners until they fit.

A few tips that genuinely improve the output:

• Natural light beats overhead light. Office ceiling lights cast shadows from the phone itself onto the page. Daylight from a window, or a desk lamp angled across the page, is better.

• Flat surface. A curved page bends the text and confuses OCR.

• Avoid glare. Tilt the phone slightly to avoid the white square reflection on glossy paper.

• Multi-page documents. Just scan one page after another - the app stacks them in a single document.

Post-processing: snap corners, adjust colour

After capture, you get a post-processing pass. The two things worth using:

• Corner adjustment. The scanner’s auto-detection is good but not perfect. If the page has low contrast against the surface, drag the corners precisely.

• Colour mode. Three options: colour (photos, coloured documents), greyscale (text on white paper - sharpest result for OCR), and black-and-white (handwriting, receipts - cleanest possible).

For most paperwork - invoices, receipts, contracts - greyscale gives the best balance of file size and OCR accuracy.

OCR: scanned image → searchable text

Tap Show recognised text below the scanned image to run OCR. The text appears in a panel you can copy from, search through, or save.

OCR quality depends on three things: image sharpness, lighting, and font. Printed text on a clean white background is recognised at very close to 100%. Handwriting is harder - Vision’s handwriting recogniser is decent on neat block letters and struggles on cursive. If a scan came out wrong, the most common fix is to re-scan with better lighting rather than fight the OCR result.

Export: searchable PDF

The trick that makes scans actually useful long-term is the searchable PDF export. It’s a PDF where each page is the scanned image, with the OCR text layered invisibly underneath - so the document looks like an image, but search engines (and macOS Spotlight, and Finder) can find words inside it.

In NFC.cool Tools, hit Share page as PDF and the export includes the OCR layer automatically. Drop the PDF into your filing system, search for “invoice 2024-02 acme corp” three months later, and the right document comes up.

Why scan instead of photograph?

You could just take a photo of the document. The reasons to use a scanner instead:

• Edge cropping. A scan is trimmed to the page. A photo includes the desk, the coffee cup, the cat.

• Perspective correction. Even held flat, a phone is slightly off-perpendicular. Scanners correct this so the page looks “as if scanned” rather than “photographed at an angle”.

• Multi-page bundling. Five photos = five files in your camera roll. Five scans = one PDF.

• Searchable text. OCR baked into the export.

For receipts, contracts, signed forms, business documents - scan, don’t photograph.

Document scanning is part of NFC.cool Tools for iPhone (Android version focuses on NFC; the document scanner needs Apple’s Vision framework).

A QR code is just a bucket of bytes. URLs are by far the most common payload, but the spec doesn’t care - you can encode Wi-Fi credentials, a calendar event, a map pin, a contact card, plain text, or any custom payload an app knows how to decode.

NFC.cool’s QR generator covers all of those. Here’s what each one actually does when scanned.

URLs

The basic case. Encode https://example.com, scan with any camera, and the device offers to open it. Works on every phone made in the last decade.

A useful variant: short links. If you have analytics-heavy URLs, generate the QR over the short version - it makes the QR code physically smaller (fewer modules = less dense) and easier to scan from a distance.

Wi-Fi credentials

Encode an SSID, password, and security type (WPA2, WPA3, open) in the standard WIFI:T:WPA;S:...;P:...;; format. iOS, Android, and modern Windows all recognise the format and prompt to join.

Print this on a small card in your guest room. Stick it on the back of the router. Tape it to the wall in a café. Guests scan, join, done - no typing 24-character passwords.

Calendar events

Encode an event as a BEGIN:VEVENT block (the iCalendar format). Scanning offers to add it to the device’s calendar app, complete with start time, end time, location, and description.

Useful on event posters, conference signage, or “save the date” cards. The recipient doesn’t have to find the event on a website - they tap once and it’s on their calendar.

Locations

Encode a geo: URI with latitude and longitude. Scanning opens the default maps app at that pin - Apple Maps on iOS, Google Maps on most Android phones.

Restaurants, venues, meetup spots: stick a small QR on the flyer or invite, recipients get directions with one tap.

vCard (contacts)

The most common alternative to URLs. Encode a full vCard (name, phone, email, organisation, address, URL, photo) and the device offers to save it as a contact.

QR business cards work this way out of the box. It’s also why a vCard QR works on every phone with no special app - vCard is a 30-year-old standard the OS already knows.

The trade-off vs the NFC.cool business card flow: a vCard QR can’t be updated. Once printed, the contact data is frozen. If you want a “single source of truth” that you can edit later, encode a URL to your live business card page instead - that’s what NFC.cool Business Card does, and it’s why we recommend it over raw vCard QR for serious networking.

Plain text

If you just want to display a string when scanned - a message, a coupon code, a riddle - you can encode plain text. Most scanner apps will display it and offer to copy or share.

Custom payloads

Some apps register custom URL schemes (myapp://...) and recognise QR codes encoded with them. NFC.cool’s scanner respects those - it reads the payload and hands off to the registered app, the same way iOS or Android would do via Universal Links.

On the scanning side

NFC.cool’s scanner reads any of the above formats and routes them to the right action: URLs open in the browser, vCards offer to save, Wi-Fi prompts to connect, locations open in maps. It also keeps a local history of every scan, which is useful when you’ve scanned 30 menus at a conference and want to revisit one.

The whole QR stack - generator and scanner - is available inside NFC.cool Tools for iPhone and Android.

QR codes don’t have to be plain black-and-white squares. The error-correction in the QR spec is forgiving enough that you can decorate the code with colour, logos, and small images, and it’ll still scan reliably. NFC.cool’s QR Studio is built around that idea - a designer for QR codes that look like part of your brand instead of an afterthought.

Colour: pick anything, but respect contrast

QR Studio lets you choose any colour for the foreground (the modules) and the background. You can match your brand palette, hint at a campaign theme, or just make the code less visually offensive on a poster.

There’s one hard rule though: contrast. A QR scanner works by sampling pixels and deciding which are “dark” and which are “light”. If your foreground and background are too close in luminance, the scanner gives up - even when the code passes a human eyeball test.

Practical rule of thumb: dark foreground on a light background. Reverse contrast (light on dark) works on most modern scanners but fails on older ones. If you’re not sure, scan with three different phones before printing 10,000 of anything.

Backgrounds: subtle is better

QR Studio also supports backgrounds - solid colours, gradients, or a subtle image behind the code. The same contrast rule applies, but more strictly: any noise in the background eats into the scanner’s margin for error.

If you want a busy background image, put the QR code on a small solid panel inside the design rather than placing the modules directly on the noisy texture. The panel can be brand-coloured. The code on it should still pop.

Personality: emojis, symbols, logos in the middle

QR codes have built-in error correction - they’re encoded with redundancy so a partly damaged code still decodes. QR Studio uses that headroom to let you drop a logo, emoji, or icon into the centre of the code without breaking it.

A few guidelines:

• Keep the centre overlay small. Roughly 20-25% of the code’s width is safe. Past that, you eat into more error correction than the code can spare.

• Use error correction level H if you plan to add a large logo. Higher correction = more redundancy = bigger logo possible. QR Studio sets this automatically when you add a centre element.

• Test on multiple scanners. iOS Camera, Google Lens, and dedicated scanner apps all have different tolerance levels. A code that scans in iOS Camera should scan everywhere.

Sizes: print vs digital

Print needs more physical area. For a business card, you want the QR code at least 2 cm × 2 cm. For a poster viewed from 1 metre away, scale up to ~5 cm. For a billboard, scale to whatever the audience distance demands - the rule is roughly “code size = viewing distance ÷ 10”.

QR Studio exports sharp PNG at up to 4096×4096 pixels, so you don’t have to worry about pixelation.

Where personality actually pays off

Customised QR codes aren’t just aesthetic - they’re recognisable. A branded QR code in a museum, a restaurant menu, a product label, or a business card tells the viewer “this is curated content, not spam”. The 0.5 seconds of trust that buys is the difference between a scan and a pass.

That’s what QR Studio is built for: pretty codes that still scan, ready to drop into any design.

Available inside NFC.cool Tools for iPhone and Android.

A lot of the technology we use every day disappears into the background. You tap to pay, unlock, scan, share - and never think about the protocol underneath. NFC is one of those quiet pieces of plumbing, and after years building NFC.cool, an app for reading and writing NFC tags, I’ve spent more time inside that plumbing than most people ever will. Here’s how it actually works on your iPhone, the way I’d explain it to a curious friend.

What NFC actually is

Near Field Communication is a short-range wireless protocol - two devices can exchange data when they’re within about 4 cm of each other. I think of it as a simplified, much shorter-range cousin of Bluetooth and Wi-Fi.

That short range trips people up at first, but it isn’t a limitation. It’s the security model, and once that clicked for me a lot of NFC’s design choices made sense. You can’t accidentally tap a payment terminal from across the room, and a malicious reader can’t quietly siphon data out of your wallet at a distance. If you’re new to all of this, I wrote a gentle beginner’s guide to NFC tags that starts further back than this post does.

NFC on iPhone: a short history

Apple shipped NFC hardware for the first time with the iPhone 6 and 6 Plus in 2014, but the radio was locked down to Apple Pay only. Third-party apps couldn’t read NFC tags at all - which, as someone who would later build an NFC app, was a frustrating few years to watch.

That changed with iOS 11 (2017), which introduced the Core NFC framework and finally let developers like me read NDEF tags. Apple kept opening the door wider in later releases - iOS 13 added writing support, and iPhone XS and newer added always-on background tag reading. Today, on any modern iPhone, you can tap a tag without opening anything: the OS recognises it and offers the right action.

How NFC actually moves data

NFC devices operate in one of two roles per interaction: active (powered, generates a field) or passive (no battery, harvests power from the field). This is the single idea I come back to whenever someone asks me how NFC works.

When you make an Apple Pay payment, your iPhone is the active reader. It generates a radio field at 13.56 MHz. The payment terminal’s NFC element wakes up inside that field, identifies itself, and exchanges a small amount of cryptographic payload with your phone. Your card data never leaves the Secure Element - a dedicated, hardware-isolated chip on the phone. What goes out is a one-time token.

When you tap an NFC sticker on a poster, the roles flip. The poster’s tag is passive - it has no battery. Your iPhone’s reader powers it, the tag responds with whatever NDEF records are stored on it, and iOS decides what to do (open a URL, launch an app, show a contact card, trigger a Shortcut). That second half - the tag side - is the part NFC.cool lives in, and if you want to see it in action without installing anything, you can read NFC tags straight from your browser on Android.

NDEF: the lingua franca

The data layer on top of the NFC radio is NDEF - NFC Data Exchange Format. I describe it as a tiny self-describing record format: a tag carries one or more records, and each record has a type (URI, text, vCard, Wi-Fi credentials, custom MIME) and a payload.

Every NFC-capable phone on the planet speaks NDEF, which is why a tag programmed on an Android device will read fine on an iPhone and vice versa. It’s one of the few places in mobile where iOS and Android genuinely share a standard, and honestly that interoperability is the thing I’m most grateful for when I’m building features - I write to the format, not to a platform. If you want to try writing your own records, I walk through it in how to write NFC tags on iPhone.

Privacy and security

Two layers of defence are worth mentioning, and they’re the two I find myself explaining most often:

• Range. A few centimetres is hard to intercept without a noticeable antenna - this is the original threat model NFC was designed around.

• Tokenisation. Apple Pay never transmits your real card number. Each transaction uses a Device Account Number plus a one-time cryptogram, generated inside the Secure Element. Even a compromised terminal can’t replay it.

For tag reading, the threat surface is different - the tag itself is the thing being trusted. If you control what’s on the tag (your own home automations, your business card), you’re fine. If you tap a random tag in a public space, you should still see a confirmation prompt in iOS before anything happens. When I do need a tag to actually hold a secret rather than just point at one, I reach for cryptographic tags, and I covered that in storing safe, encrypted secrets on NFC tags.

Why this matters

NFC is one of those protocols that disappears when it works, and that’s exactly why I find it satisfying to build on. You tap a turnstile, a payment terminal, a business card, a smart speaker - and something happens. There’s no pairing, no PIN, no app launch. Just a deliberate physical gesture that authorises one specific exchange.

That’s why I built NFC.cool Tools - to make the full NDEF surface of NFC available without anyone having to learn the protocol first. Read any tag, write any record type, lock a tag when you’re done. On iPhone or Android.