How to Clone an NFC Tag You Own (and What You Can't Copy)

Cloning a tag you own usually means copying its NDEF data to a blank tag, which is easy. Copying the fixed UID is a different story. Here is what works.

Published

Cloning an NFC tag you own usually means copying its NDEF data — the URL, text, or contact card stored on it — onto a blank tag. That part is quick — a minute, maybe two. Copying the tag's fixed UID is a separate, much harder thing, and most projects never need it. This guide covers what you can copy, what you can't, and the line we don't cross.

One ground rule first: this is about tags you own or control. Duplicating someone else's access badge, transit card, payment card, or hotel key is off the table — both because it usually won't work and because it isn't ours to copy.

What "cloning" actually means

People use "clone" for two different jobs. The first is copying the NDEF payload — the readable content a phone taps into, like a website link, a Wi-Fi handoff, or a vCard. The second is copying the UID, the tag's serial number. Almost every everyday use case — spare stickers, a backup of a smart-home trigger, a second copy of your digital business card — only needs the payload. The UID rarely matters unless a system was built to check it.

How copying a tag actually works

Copying the payload is straightforward. You read the source tag's NDEF records, then write the same records to a blank tag. The catch is memory: write to a tag of equal or larger capacity. The common NTAG family gives you 144 bytes on an NTAG213, 504 on an NTAG215, and 888 on an NTAG216, per the NXP datasheet. A vCard that fits an NTAG215 won't squeeze onto an NTAG213.

The UID is where you hit a wall. Every NTAG ships with a 7-byte UID programmed at the factory and locked, so you cannot rewrite it on a normal tag. So-called "magic" or UID-changeable tags exist for developers and labs, but standard stickers won't budge. If a system authenticates by UID, a plain copy won't impersonate the original — by design.

Encrypted tags raise the wall higher. On MIFARE Classic and DESFire, sector data sits behind crypto keys, and the UID lives in a write-protected block. That protection is the whole point of access control, so we treat those tags as read-only territory and leave them alone.

iPhone vs Android

Platform matters here. Apple's Core NFC lets an iPhone 7 or later read and write NDEF tags, which covers the everyday copy-the-payload job. Android exposes the same NDEF support plus lower-level tag technology access for raw reads and writes. For straightforward NDEF cloning, both phones handle it fine.

Where you'll run into the limits

The legitimate cases are the common ones. Duplicate a URL sticker so each room has its own. Back up a vCard tag before you re-stick it. Keep a spare of a smart-home trigger so a second tap point fires the same automation. Every one of those is just a clean payload copy.

The cases that fail are the ones people ask about most: hotel keys, transit passes, contactless payment cards, and workplace badges. These lean on encryption, a locked UID, or a backend that won't recognize a copy — and they're not yours to duplicate anyway. If a tag isn't yours, the answer is no.

Cloning your own tag with NFCore

The flow in NFCore is short, and it goes like this. Read the source tag and look at its NDEF records so you know what you're copying. Grab a blank tag of the same type or larger. Write the records to the new tag, then read it back to confirm it matches. If the copy is going somewhere public, you can lock it afterward so the content can't be changed — just remember locking is permanent.

That's the whole job for the tags you own. If you're new to the format, our explainer on how NFC works is a good next read. Ready to copy your own tag? NFCore is free on the App Store and Google Play.

FAQ

Can I clone an NFC tag with my iPhone?

Yes, for the common case. An iPhone 7 or later can read an NDEF tag and write the same records to a blank tag using Core NFC. It can't rewrite a fixed UID, but most copies don't need that.

Why can't I copy the UID?

The 7-byte UID is programmed at the factory and write-protected, so it can't be changed on a normal tag. Only special UID-changeable tags allow it, and those are meant for development, not everyday stickers.

What blank tag should I buy to clone onto?

Match or exceed the original's memory. An NTAG215 (504 bytes) is a safe general pick; step up to an NTAG216 (888 bytes) for larger payloads like long vCards.

Is it legal to clone an NFC tag?

Copying a tag you own — your own stickers, contact cards, or smart-home triggers — is fine. Duplicating someone else's access, transit, payment, or hotel tags is not, and NFCore won't help with that.


Ready to Get Started?

Download NFCore and start managing your NFC tags like a pro.