How to encode an NFC card: a step-by-step guide

Overview

This guide walks you through the two key steps to encode an NFC card.
Whether you've received a batch of blank NFC cards from us, or you're planning ahead - encoding is simpler than you might think.

The two steps are:
1. Choose the right chip type for your URL (NTAG-213 vs NTAG-215)
2. Encode the card using a free app on your phone

The most common NFC encoding use case for business cards is simply writing a URL to the chip - so when the card is tapped against a phone, it opens a webpage (your digital business card, Google Reviews page, website, etc.).

Choose your chip: NTAG-213 or NTAG-215?

The amount of data an NFC chip can hold varies by chip type. The two most common standard chips are:

NTAG-213 - the most common chip we supply (cheaper price point).
It has 144 bytes of usable storage. This is enough for most short URLs.

NTAG-215 - the next step up.
It has 504 bytes of usable storage. Required for longer URLs or more complex data.

NTAG-424 DNA - advanced secure chip with 868 bytes + AES-128 encryption. Used for anti-counterfeiting, secure authentication. More info here

• A basic vCard with no logo and basic details will be above 3,000 bytes - far too large for any NTAG chip.
• A basic vCard with logo will be above 8,000 bytes.
• This is why we always encode a URL (link to a digital business card page) rather than a raw vCard directly onto the chip.

URL Byte Counter - will my URL fit?

Paste your URL below to instantly check whether it will fit on an NTAG-213 (144 bytes) or NTAG-215 (504 bytes).
Note: The counter includes a small NDEF overhead (approx. 7 bytes for a URL record) which is automatically accounted for.

Example: A typical Google Reviews URL such as:

https://www.google.com/search?hl=en-AU&gl=au&q=Fluid+The+Color+Salon,+3/8+Martha+St,+Camp+Hill+QLD+4152&ludocid=1745254678834947767&lsig=AB86z5WhAxRg6Cdkd8pOQYk0saj2#ip=1&lrd=0x6b915bb680e0f35f:0x183863e2368ba6b7,1,,,,

This equates to approximately 220 bytes - over the NTAG-213 limit of 144 bytes, so it requires NTAG-215 (or a shortened URL).
How to create a Google Review link

Encoding the card

The most common chips used in NFC business cards - NTAG-213 and NTAG-215 - are from the NTAG series by NXP. They are widely adopted due to their compatibility with NFC Forum Type 2 standards, broad smartphone support, and ease of encoding.
NXP datasheet

We can encode the NFC cards for you - simply fill out the details in this template and return it to us.

Alternatively, you can encode them yourself - this is common when you want to receive blank cards and encode them later, or when each card needs different data.

Encoding with your phone - NFC Tools app

The easiest way to self-encode standard NFC cards (NTAG-213 / NTAG-215) is with your phone and the free app NFC Tools by Wakdev (available on Android and iOS).

To encode a URL (the most common use case):

1. Open NFC Tools and select Write from the top menu
2. Tap Add a record
3. Select URL / URI
4. Enter or paste your URL
5. Tap Write
6. Hold the card against the back of your phone to write

To test: Exit the app, then tap the card to the back of your phone. It should open your URL automatically.

Note for iPhone users: iPhone XS and later support NFC writing. Older iPhones can only read NFC tags. If you have an older iPhone, use an Android device or ask us to encode the cards for you.

Prefer us to encode for you?

We can encode your NFC cards as part of your order. Simply:

1. Download and fill in our NFC data template
2. Include one URL per card (or the same URL for all cards - your choice)
3. Return the completed spreadsheet to us with your order

If each card needs a different URL (variable data), note this when ordering and we'll confirm pricing. Variable encoding is common for:
• Unique customer profile pages
• Individual staff digital business cards
• Per-product authentication pages

See our NFC card range Quick metal NFC cards (MOQ 1)