Back to guides

DESFire Light vs EV3: Which MIFARE Card Fits Your Project

DESFire Light is a single-application card with 640 bytes and a fixed file layout. EV3 is the multi-application card, from 2 to 16 KB. Here is how to choose between them.

Published

Short answer

Pick DESFire Light when one card does one job and you can live with a fixed layout. Pick DESFire EV3 when the card may carry several applications, needs more memory, or must meet a higher security certification. Both are NXP chips, both speak ISO/IEC 14443 A and ISO/IEC 7816, and a Light design can later move up to EV3.

What each card is

NXP describes DESFire Light as a secure, easy-to-integrate, cost-effective IC with a predefined file structure, built for single-application use. It authenticates with AES-128 and optionally LRP, and it is certified to Common Criteria EAL4.

EV3 is the multi-application card. The same NXP page lists it at Common Criteria EAL5+ for hardware and software, with DES, 2K3DES, 3K3DES and AES available. Typical jobs are transport ticketing, access management and closed-loop payments.

Memory and files

Light has 640 bytes of user memory, the same as a MIFARE Classic 1K according to Wakdev. That memory is split into six files created at the factory and not deletable:

  • three data files totaling 544 bytes (two of 256 bytes, one of 32 bytes)
  • a value file holding a 4-byte signed integer
  • a cyclic record file of four 16-byte records
  • a Transaction MAC file

You can reconfigure file IDs and access rights, but not the layout. Only the Transaction MAC file can be re-created, to change its key.

EV3 comes in 2, 4, 8 and 16 KB, with up to 32 files per application across six file types and up to 14 keys per application. NXP also lists a typical write endurance of 1,000,000 cycles and 25-year data retention. Wakdev gives Light a minimum of 200,000 write cycles and 10 years.

DESFire LightDESFire EV3
ApplicationsOne, fixed structureMany
Memory640 bytes2, 4, 8 or 16 KB
CryptoAES-128, optional LRPDES, 2K3DES, 3K3DES, AES
CertificationCC EAL4CC EAL5+
Write endurance200,000 cycles minimumAbout 1,000,000 typical

One application or many

On a DESFire card, data lives in applications, and each application holds files protected by its own keys. We cover this in how a DESFire card stores data in applications, files and keys. Light gives you exactly one application with the fixed file set above. EV3 lets several applications share one card, each with its own keys, so a campus card can carry door access, a canteen balance and a library record without the operators sharing secrets.

Security: EAL4, EAL5+ and what each adds

The certification gap is the headline: EAL4 for Light, EAL5+ for EV3. Past that, each adds its own protections. Light can permanently enable LRP, a mode Wakdev describes as resistant to side-channel and fault attacks. Light also keeps a Transaction MAC file, which gives the backend proof that a transaction happened.

EV3 adds Secure Unique NFC (SUN) messaging, a Transaction Timer, Proximity Check and Originality Check, per NXP's EV3 page. Whether you need any of them depends on your threat model. A one-shop loyalty card and a transit card face very different attackers.

Moving from Light to EV3 later

Light's secure messaging is a subset of EV2's, so a Light application can migrate to EV2 or EV3 without redesign. You still have to issue new cards. The chip can't be upgraded in the field. If you are weighing the newer generations against each other, read what changed between EV2 and EV3. Teams coming from MIFARE Classic may also look at EV3C, which can emulate a MIFARE Classic 1K card.

Which card fits which project

  • One-purpose card (single-site access, event ticket, simple stored value): Light. Six fixed files cover a counter, a balance and a short history.
  • A card shared by several services or operators: EV3, because Light has one application.
  • Data that outgrows 640 bytes, or many files: EV3.
  • Hard security requirements or certification demands: EV3, at EAL5+.
  • Unsure which family at all: see DESFire vs MIFARE Plus first.

Whichever you choose, a DESFire card isn't a tag you can write from a phone with a plain NDEF app. You need the keys. With NFCore you can inspect what a card you own reports, so you can confirm which chip you are holding before you plan around it. Get NFCore on the App Store or Google Play.

Frequently Asked Questions

Is DESFire Light the same as DESFire EV3?

No. Light is a cut-down, single-application chip with a predefined file structure and 640 bytes of user memory. EV3 is the multi-application card, in 2, 4, 8 and 16 KB.

Can a DESFire Light card hold more than one application?

No. NXP positions Light for single-application use cases with a predefined file structure. You configure keys and access rights, not the file layout.

Can I move from Light to EV3 later?

Yes in design terms: Light's secure messaging is a subset of EV2's, so a Light application can migrate to EV2 or EV3 without redesign. You do have to issue new cards.

Which one is more secure?

On certification, EV3: Common Criteria EAL5+ against EAL4 for Light. Light adds optional LRP, and EV3 adds SUN messaging and a Transaction Timer.