Copying an NFC tag means duplicating the data or functionality stored on it, like a URL, Wi-Fi credentials, or a text message, onto a blank writable tag. However, you cannot copy the tag's unique factory-locked ID (UID), which is what many secure systems actually check. So, to copy an NFC tag for everyday automation or sharing, you're replicating the NDEF data payload, not the tag's identity.
What it really means to copy an NFC tag
Every standard NFC tag (like NTAG213, NTAG215, or NTAG216) comes with a 7-byte UID programmed at the factory. This UID is write-protected and cannot be changed or rewritten. When you copy an NFC tag, you are reading the stored NDEF records, the actual data like a link or a text block, and writing that same data to a blank tag. The new tag will have its own different UID, but for most consumer use cases (opening a website, sharing contact info, toggling device settings), the UID doesn't matter, only the data does, which is exactly what a website NFC tag mean relies on to function. If you want to skip the blank tag entirely and store the data directly on your device, you can copy an NFC card to iPhone for quick access from the Wallet app.
This distinction matters because some people hope to clone access badges or payment cards. Those systems often rely on the UID for security, so a data-only copy will fail. But if your original tag simply triggers a phone action or shares information, copying the data is all you need.
What you'll need to copy an NFC tag
To copy an NFC tag, you need three things:
- An NFC-enabled smartphone (Android has full read/write access; iPhone 7 and newer can read NFC but have limited writing capabilities for certain tag types).
- A blank, writable NFC tag (NTAG216 is a common choice because it has enough memory for most NDEF records).
- An NFC writing app like NFC Tools, TagMo, or NFC TagWriter.
That's it. No special hardware or computer is required. The phone itself does both reading and writing.
How to copy an NFC tag's data in 3 phases
The entire process boils down to three phases: reading the original tag's data, writing that data to a blank tag, and testing the duplicate. Each phase takes less than a minute once you have the right tools. Below is the consolidated method that works with most NFC apps.
Phase 1: Read the original tag
Open your NFC app (like NFC Tools) and tap the original tag against the back of your phone. The app will display the tag's NDEF records, the actual content stored on it. This could be a URL, a plain text message, a Wi-Fi configuration, or a custom app launch command. You'll see the full data payload on your screen. Ignore any UID or serial number shown; that's the factory-locked part you can't copy. Save or note the content.
Phase 2: Write the data to a blank tag
Place your blank, writable NFC tag on the back of your phone. In the same NFC app, choose the "Write" option. If not, you can manually re-enter the data you read in Phase 1. The app will write the NDEF records to the blank tag. The new tag will have its own unique UID, but the data will be identical to the original. Make sure you keep the blank tag still against the phone until the app confirms the write was successful.
Phase 3: Test your duplicated tag
Take your newly written tag and tap it against your phone. It should perform the exact same action as the original, open the same website, connect to the same Wi-Fi network, or display the same text. If it doesn't work, check that you wrote the correct data type and that the tag is fully blank before writing. Testing is the only way to confirm the copy is functional.
Why your copied tag might not work
If your copied tag fails to work for access control or payment systems, it's because those systems use the tag's UID for authentication. The UID is factory-programmed and cannot be replicated. When you copy an NFC tag, you only copy the data layer, not the hardware identity. So a copied tag might open a website or trigger a phone automation, but it won't unlock a door or make a payment if the original relied on the UID. This is a security feature, not a limitation of the copying process. For everyday NFC tags that store URLs or settings, the UID is irrelevant, and your copy will work perfectly.
One more thing: if you want to make an RFID protector for your copied tag, you can use the same NFC app to write a simple text or URL onto a tag and then place it inside a card sleeve. That's the same process, just with a different data type. But for straightforward duplication of a standard tag's functionality, the three-phase method above is all you need.
Remember: copy the data, not the UID, and you'll have a working duplicate for any everyday NFC use case.
