MIFARE Classic Compatibility Mode: What It Does and Doesn't Fix

Compatibility mode lets NFC Tools on an iPhone read and write standard NDEF records on MIFARE Classic 1K chips. It does not give you raw memory access, and it does not make Classic behave like an NTAG sticker.

If you already know why an iPhone often can't see a MIFARE Classic card, this is the next question: what the workaround actually buys you, and where it stops.

What the compatibility mode does

The most direct description comes from the NFC Tools developer, who answered a question about Classic 1K chips on the Apple Developer Forums. Their answer: these chips are "not fully compatible" with Core NFC, but the app has a compatibility mode in its settings that can read and write standard NDEF records. Some features, such as reading the chip's memory, can't be used with this type of chip.

The app's own knowledge base says the same in fewer words: Classic isn't compatible with all devices, and on an iPhone you have to enable the compatibility mode in the NFC Tools settings.

Two caveats. The forum posts are community answers, not Apple documentation. And none of the sources we found lists exact iOS versions or card variants that work, so test with your own card before you print a hundred of them.

Why Classic needs a special case

MIFARE Classic isn't built like a typical NDEF tag. According to Android's MifareClassic reference, a card is split into sectors, and each sector into 16-byte blocks. A 1K card has 16 sectors of 4 blocks, which gives 1,024 bytes in total.

Before you can read or write anything in a sector, you must authenticate that sector with one of its two keys. The access bits in the sector decide what each key is allowed to do.

NDEF fits into this through a specific agreement. Android defines a well-known key, KEY_NFC_FORUM, for cards formatted to the NXP specification for NDEF on MIFARE Classic. Compatibility mode works at that layer: standard NDEF records, not the sector-by-sector contents of the card. That's why raw memory reads are the part that stays unavailable on the iPhone.

Android: support depends on the phone

Android doesn't promise Classic support at all. Per the reference, implementing the MifareClassic class is optional on an Android NFC device. If a phone doesn't implement it, the class never shows up for the tag. If it does, all Classic I/O operations work, and NDEF on Classic is supported too.

That matches what the NFC Tools team reports in practice: some Android devices read basic information like the UID but can't read or write data. If a Classic card works on one Android phone and not another, the hardware is the first suspect, not the card.

When to switch to a different chip

Buying new cards for a tap-to-open-a-link or tap-to-share job? Don't start with Classic. The NFC Tools knowledge base recommends NXP NTAG21x chips, specifically NTAG213 or NTAG216, for reliable compatibility.

NXP's page on NFC with iOS 13 points the same way. It names NTAG and ICODE tags, and lists MIFARE DESFire, Plus and Ultralight as supported product lines. DESFire and Ultralight can hold NDEF-formatted content compatible with NFC Forum tag types. The page doesn't mention MIFARE Classic. If you're weighing a bigger card family, our comparison of DESFire on iPhone and Android covers what a phone can and can't do with it.

If you're stuck with existing Classic cards, treat compatibility mode as a way to handle NDEF messages, not as full Classic support.

Bottom line

Compatibility mode is a narrow fix. It covers standard NDEF records on Classic 1K for iPhone, and it leaves raw memory out. Android depends on whether the phone implements Classic at all. For anything you'll deploy widely, choose NTAG213 or NTAG216 and skip the testing.

When you want to check what is actually on a card, NFCore reads and writes NDEF on iPhone and Android. What a given card allows still depends on the chip and the phone.

Frequently Asked Questions

Can an iPhone write NDEF to a MIFARE Classic card?

According to the NFC Tools developer in an Apple forum thread, the app's compatibility mode can read and write standard NDEF records on Classic 1K chips, but features such as reading the chip's memory can't be used. These are community statements rather than Apple documentation, so test with your own card.

Why does my Android phone only show the UID of a Classic card?

Android's MIFARE Classic support is optional per device. NFC Tools' maker notes that some Android devices read basic information such as the UID but can't read or write data.

What chip should I buy instead?

For reliable cross-device use, NFC Tools' maker recommends NTAG213 or NTAG216.