Supported NFC Tags
Full compatibility list for NFC Clone app. Check if your tag type is supported.
| Tag Type | Memory | Standard | Support | Notes |
|---|---|---|---|---|
| NTAG213 | 144 bytes | NFC Forum Type 2 | Full Support | Most popular for URLs and simple data. Cheapest option. |
| NTAG215 | 504 bytes | NFC Forum Type 2 | Full Support | Used in Nintendo Amiibo. Great all-purpose tag. |
| NTAG216 | 888 bytes | NFC Forum Type 2 | Full Support | Largest NTAG. Best for vCards and complex data. |
| MIFARE Ultralight | 64 bytes | ISO 14443A | Full Support | Common in transit systems and event tickets. |
| MIFARE Ultralight C | 192 bytes | ISO 14443A + 3DES | Partial | Encrypted sectors require key. Unencrypted NDEF supported. |
| MIFARE Classic 1K | 1024 bytes | ISO 14443A (proprietary) | Partial | Only unencrypted sectors. Proprietary encryption cannot be read. |
| MIFARE Classic 4K | 4096 bytes | ISO 14443A (proprietary) | Partial | Same as Classic 1K with more memory. Partial support. |
| NTAG210 | 48 bytes | NFC Forum Type 2 | Full Support | Smallest NTAG. Very limited storage. |
| NTAG424 DNA | 256 bytes | NFC Forum Type 4 | Partial | Secure authentication features. NDEF reading supported. |
| ICODE SLIX | 112 bytes | ISO 15693 | Read Only | Different NFC standard. Read supported, clone not available. |
Important Notes
- *UID UID cloning is not possible on standard Android phones due to hardware restrictions.
- *Notes Encrypted sectors on security tags cannot be read or cloned.
- *Target tags must have equal or larger memory than the source tag.
- *Read-only tags can be read and their data viewed, but not written to.
Frequently Asked Questions
Which NFC tags can be cloned?
Any NFC tag that stores NDEF data can be cloned using NFC Clone. This includes NTAG213, NTAG215, NTAG216, and MIFARE Ultralight tags. Tags with full support can have their NDEF data read and written to a blank target tag of the same or larger capacity. Tags with partial support (like MIFARE Classic) can only have their unencrypted sectors cloned.
Can I clone MIFARE Classic tags?
MIFARE Classic tags are partially supported by NFC Clone. You can read and clone unencrypted NDEF sectors, but sectors protected by proprietary MIFARE Classic encryption cannot be read or duplicated. For full MIFARE Classic access including encrypted sectors, a specialized tool like MIFARE Classic Tool (MCT) with known encryption keys is required.
What is the best NFC tag for cloning?
NTAG215 is the best general-purpose NFC tag for cloning because it offers 504 bytes of storage at a reasonable price and has full support in NFC Clone. For smaller data like URLs, NTAG213 (144 bytes) is the cheapest option. For larger data like full vCards, NTAG216 (888 bytes) provides the most storage. Always ensure your target tag has equal or larger memory than the source tag.
Can NFC UIDs be cloned?
No, NFC UIDs (Unique Identifiers) cannot be cloned using standard Android phones. The UID is a hardware identifier burned into the tag at the factory and stored in read-only memory. This is a fundamental hardware limitation, not a software restriction. Access control systems that verify UIDs will not accept cloned tags because each tag has a unique, unchangeable UID.
Do I need a special phone for NFC cloning?
No, you do not need a special phone for NFC cloning. Any Android phone with built-in NFC hardware can read and write NFC tags using NFC Clone. Most Android phones manufactured since 2015 include NFC. You do not need to root your device or install any special drivers. Simply enable NFC in your phone settings and install NFC Clone from Google Play.