Christmas Card NFC Tags: Write the Same Link to a Whole Batch
Writing NFC tags for a stack of Christmas cards? Set up one link, repeat a short write loop, test one card first, then lock and sort the batch.
Mailing 20 or 40 cards with the same link on each? Treat it as one setup and one repeated loop: enter the link once, then place a card, write, confirm, move on. A few habits keep you from locking a typo into the whole stack. This guide covers the batch. For the basics of adding one NFC tag to a greeting card, start there first.
One link for the whole stack
A tag stores an NDEF message, and an NDEF message holds one or more records. Android's developer documentation describes it that way, and for a card link you only need one: a single URI record holding a web address. You will write that same record to every card.
Pick a link you control. If the card points at a page of yours, you can swap the video or message later without touching a single tag. A link straight to a file or a private share you may delete leaves you with dead cards.
Size isn't a worry. NXP lists 144 bytes of user memory for the NTAG213, and a short web address uses a small part of that. A cheap NTAG213 sticker is plenty here. The bigger chips in the family add room you won't use.
The batch write loop
Set up once, then repeat.
Set up once
Open your writer app, create a URL record and paste the link. Read it over twice, since a typo multiplies across a batch.
Some apps are built for batches. NXP's TagWriter, for example, lists writing multiple tags in sequence and inserting increasing counter values among its features, and it can also back up a tag before writing and erase one. For the same link on every card you won't need counters. If you'd like each card to carry its own number, that's the feature to look for. Our guide on which writer app fits which job compares the common options.
Per card
- Put one card against the phone, and keep the rest of the stack away. NTAG chips can handle more than one tag in the field, but you want to know exactly which card you just wrote.
- Write the record and wait for the app to confirm.
- Set the finished card on a separate pile.
NXP rates the NTAG21x family for 100,000 write cycles and 10 years of data retention, so a wrong write on an unlocked tag can simply be written again. That is also why you should hold off on locking.
Test one card, then lock
Before you write the rest, write one card and test it on both kinds of phone. Hold an iPhone to it, then an Android phone. Does it open the right page, and does it open quickly?
Android is changing here. According to Android's documentation, from Android 16 a tag holding a web link triggers a view action, and from Android 17 the phone shows an open-link notification that the user has to tap. So a recipient on a recent Android phone may see a prompt rather than a page opening on its own. A line in the card, such as "Tap the notification to open", saves you a confused phone call. See also our notes on testing a tag before you rely on it.
Locking is optional. NXP says the NTAG21x chips offer read-only locking by page, plus a configurable password with an optional limit on failed attempts. A locked tag cannot be edited again, so lock only after the test card behaves and the link is final.
Label and sort the stack
Keep three piles: blank, written and tested, and a "check this one" pile for anything the app did not confirm. A small pencil dot on the back of written cards helps. If you pre-write tags before the cards are assembled, our guide to pre-writing tags before gifting shows how to keep the kit organized.
Once the cards are sealed, tap-test a few from the pile.
Bottom line
One link, one tested card, then a repeat loop with a confirmation on every card. Lock last, and only if you are sure. To write the tags, you can use NFCore on the App Store or Google Play: add a URL record, hold the phone to the tag, and read it back to check.
Frequently Asked Questions
Can I write the same link to 30 cards at once?
Tags are written one at a time, so the batch is a repeated loop: place the card, write, confirm, next card. NXP's TagWriter lists writing multiple tags in sequence as a feature, which keeps the loop short.
Is NTAG213 big enough for a Christmas card link?
Yes. NXP lists 144 bytes of user memory for NTAG213, and a short web link is a small part of that.
Should I lock the tags?
Only after you have tested a card and you are sure of the link. NTAG chips support read-only locking, and a locked tag cannot be fixed later.
Will every recipient's phone open the link straight away?
Not always. Android 17 shows an open-link notification that needs a tap, so tell recipients to tap it.