13.56MHz Mifare 1K Keyfob vs EM4100, Ultralight, DESFire — Pick the Right Chip Before You Order
13,56MHz Mifare 1K Keyfob sits at the mid-tier of the HF access control fob market — more secure than the read-only EM4100 / TK4100 at 125 kHz, cheaper and more widely supported than MIFARE DESFire EV2, and with dramatically more usable memory than MIFARE Ultralight. It is the correct default choice for gym membership systems, hotel guest cards, employee ID badges, apartment door access, and secondary campus payment loops. It is the wrong choice for banking-grade payment, government ID, or anywhere a Crypto-1 crack is an unacceptable business risk.
This page is a chip selection guide for procurement buyers who already know they need an HF fob but have not yet decided between four viable chip families. If you pick wrong at PO time, you either ship a fob that a security auditor flags for replacement two years later, or you overspend on a DESFire deployment when a Classic 1K would have worked fine.
The Landscape — What HF and LF Fob Options Exist Today
The commercial fob market breaks into two frequency bands and four dominant chip families within HF. LF 125 kHz is a separate ecosystem — see our 125khz RFID EM4100 TK4100 kľúčenky line for that. Within 13.56 MHz HF, the four practical chip choices are:
- MIFARE Ultralight — no encryption, 48 bytes user memory, low cost, disposable tickets.
- MIFARE Classic 1K — Crypto-1, 752 bytes user memory across 16 sectors, mid-price, mainstream access control.
- MIFARE Classic 4K — Crypto-1, 3,440 bytes across 40 sectors, mid-price, multi-application deployments.
- MIFARE DESFire EV2 / EV3 — AES-128, up to 8 KB, higher cost, banking / transit / government-grade.
The 13.56MHz Mifare 1K Keyfob is the volume workhorse of the middle two categories. Every deployment that requires an ID with a checksum-verifiable stored value — a gym visit count, a hotel room number, a corporate access group, a canteen prepaid balance — falls naturally to this chip. Deployments that need only a UID (no stored data) can downgrade to Ultralight and save cost; deployments where a $50k Crypto-1 crack tool represents an unacceptable risk must upgrade to DESFire.
13.56MHz Mifare 1K Keyfob vs EM4100 vs Ultralight vs DESFire — Head-to-Head
| Parameter | EM4100 / TK4100 fob (LF) | MIFARE Ultralight (HF) | 13.56MHz Mifare 1K Keyfob (HF) | MIFARE DESFire EV2 (HF) |
|---|---|---|---|---|
| Frekvencia | 125 kHz | 13.56 MHz | 13.56 MHz | 13.56 MHz |
| Protokol | Manchester read-only | ISO 14443A | ISO 14443A | ISO 14443A + ISO 7816-4 |
| User memory | 0 (UID only) | 48 bytes | 752 bytes / 16 sectors | 2 KB / 4 KB / 8 KB |
| Encryption | None | None | Crypto-1 (48-bit) | AES-128 / 3DES |
| Cloneable with $30 tool? | Yes (any 125 kHz duplicator) | Yes (UID copy) | Partial (Crypto-1 crack ~1 min on gen2 magic) | No (AES-128 unbroken) |
| Read range (typical fob) | 4-10 cm | 3-5 cm | 3-5 cm | 3-5 cm |
| Reader compatibility | HID, Iron Logic, Bolid, ZKTeco (LF only) | All ISO 14443A HF readers | All ISO 14443A HF readers | ISO 14443A + DESFire-capable readers |
| Smartphone read (NFC) | No | Áno | Yes (UID only, no sector decrypt) | Yes with app + key |
| Write endurance | N/A (read-only) | 10,000 cycles | 100,000 cycles | 500,000 cycles |
| Typical unit cost (100 pcs MOQ) | $ | $ | $$ | $$$$ |
| Common deployment | Legacy building access | Event / transit tickets | Gym / hotel / office ID | Bank / transit / gov ID |
| Certifications applicable | ISO 9001, RoHS, REACH | + ISO 14443A | + ISO 14443A, MIFARE trademark license | + Common Criteria EAL5+ |
When to Choose the 13.56MHz Mifare 1K Keyfob Over an Alternative
Choose 13.56MHz Mifare 1K Keyfob over an EM4100 LF fob when:
The system needs to store data on the credential, not just identify it. A gym membership fob that counts remaining visits without a network connection to the central database, a hotel key that encodes room number plus expiry time, a canteen fob that stores prepaid balance — none of these work on EM4100 because the LF chip carries only a UID. Also choose 13.56MHz over 125 kHz when the reader ecosystem is being newly installed rather than replaced: HF ISO 14443A is the modern default, LF is the legacy standard maintained only for existing installations.
Choose 13.56MHz Mifare 1K Keyfob over MIFARE Ultralight when:
The user population is large enough that Crypto-1 offers meaningful protection against casual cloning by end users with a smartphone. A 200-member gym does not need it; a 5,000-employee corporate campus does, because at 5,000 employees at least one motivated individual will try to clone their fob and pass it to a friend. Ultralight has no encryption — its UID is trivially cloneable with any Android phone running NFC Tools. Mifare 1K’s Crypto-1 raises the bar to a purpose-built $50 tool and roughly one minute of computation per fob, which filters out 99% of opportunistic cloning attempts.
Choose 13.56MHz Mifare 1K Keyfob over DESFire EV2 when:
The deployment does not handle real money, real personal data, or real physical security beyond what a determined attacker with a $50 clone tool could compromise anyway. DESFire costs roughly 4-6× more per fob and requires DESFire-capable readers that cost 2-3× more than generic MIFARE readers. If the assets being protected are worth less than the incremental fob and reader cost across the entire deployment population, DESFire is over-specification. A 1,000-room hotel that already accepts the theft of a physical brass key as a manageable risk does not need AES-128 on its RFID replacement.
When NOT to Choose the 13.56MHz Mifare 1K Keyfob
This section exists because reverse recommendations build supplier credibility faster than a hundred positive claims. Do not deploy MIFARE Classic 1K if:
You are protecting anything a bank auditor cares about. Crypto-1 was cryptographically broken in 2008 (Karsten Nohl, Chaos Communication Congress 24C3) and the crack has been productised into commercial tools since 2011. A Proxmark 3 with the appropriate firmware clones a Classic 1K sector in under 60 seconds using the “nested” or “hardnested” attack. This is not a theoretical risk — it is a routine operation in penetration testing and known to organised card cloners. For payment, national ID, or high-security building access, deploy DESFire EV2 or a competitive AES-128-based chip.
You need long read range from a keyfob form factor. HF magnetic coupling drops off with the sixth power of distance; a keyfob antenna at 13.56 MHz reads 3-5 cm on a typical reader and rarely more than 8 cm even on high-power readers. If your use case requires hands-free access from a metre away (vehicle gate entry, garage door), UHF EPC Gen 2 in a keyfob or wristband format is the correct choice, not any HF chip.
You are trying to save money on a 100-piece pilot. Below 100 pieces, the per-unit cost differential between EM4100, Mifare 1K, and even DESFire EV2 is dominated by MOQ overhead and shipping, not chip BOM. Pick the chip that matches the eventual production deployment, not the one that saves $0.15 per pilot fob.
Buyers evaluating specifically the MIFARE Classic ecosystem may also want to review our dedicated Mifare Classic 1K Key Fob product page, which documents the alternate ABS shell shapes, dimensions, and industrial IP-rated variants available in the same chip family.
Technical Deep-Dive on 13.56MHz Mifare 1K Keyfob
The MIFARE Classic 1K chip is an NXP-designed HF integrated circuit implementing ISO/IEC 14443A layers 1 through 3 with a proprietary Crypto-1 stream cipher at layer 4. The 1,024 bytes of EEPROM are structured as 16 sectors of 4 blocks each, where each block is 16 bytes. The last block of every sector (the “trailer”) holds two 6-byte authentication keys (Key A, Key B) plus 4 bytes of access conditions that define which key is required to read, write, increment, decrement, restore, or transfer each of the three data blocks in the sector.
Sector 0 block 0 holds the read-only manufacturer data — the 4-byte or 7-byte UID plus check digit plus factory serial data. All other blocks are user-writable subject to authentication. In access control deployments the pattern is typically to write a facility code and a card number into sector 1 data blocks, protected by an installation-specific Key A that must match at the reader for the fob to enrol. In stored-value deployments (canteen, transit) the balance is stored using MIFARE’s value-block format that supports atomic increment and decrement operations across power interruptions — critical because a fob yanked from the reader mid-transaction must not lose the transaction record.
Our 13.56MHz Mifare 1K Keyfob line ships with either the classic MIFARE Classic 1K chip from NXP or the Fudan FM11RF08 — a Chinese-manufactured, pin-compatible, protocol-compatible chip that reads on the same readers with the same Crypto-1 authentication. FM11RF08 costs approximately 30% less at scale and is functionally indistinguishable to readers; it is the correct choice for cost-sensitive deployments in Asia-Pacific and South America. NXP-branded chips are the correct choice for deployments in the EU and North America where trademark compliance is enforced by procurement audit.
Manufacturing and Quality Control
Production runs on a dedicated HF keyfob line inside a 5,000 m² Shenzhen facility operating since 2008. The antenna is a copper coil ultrasonically embedded in the ABS shell’s internal cavity, tuned to 13.56 MHz ± 200 kHz resonance and verified on an Agilent E4980A LCR meter as the final step before shell closure. Chip bonding uses anisotropic conductive paste cured at 180 °C for 12 seconds, then the shell halves are ultrasonically welded to IP54 as standard (IP67 available with a sealed variant at 1,000 pc MOQ).
Every finished fob passes through a tunnel reader test station that performs three checks: UID readback, Crypto-1 authentication against the factory default keys, and received signal strength at a 3 cm coupling distance. Units failing any check are quarantined; a batch where more than 0.5% of units fail triggers a full production line stop and root-cause investigation. Cavity-level 100% electrical test is standard, not an upgrade — a customer that discovers a dead fob only after their end-user tries to enter the building on Monday morning is a customer that switches suppliers.
Purchase Decision Checklist — 5 Questions to Ask Before Ordering
- Frequency confirmed? Verify the target reader is 13.56 MHz HF ISO 14443A. If the existing reader is 125 kHz LF, a Mifare fob will not read and the buyer will return the entire order.
- Data storage required, or UID only? If UID only, MIFARE Ultralight saves 20% cost. If data storage required (balance, expiry, group), MIFARE 1K is the volume-optimal chip.
- Security requirement above Crypto-1? If protecting payment, personal data, or high-value physical assets, upgrade to DESFire EV2 with AES-128. Ask the security auditor explicitly rather than defaulting to Classic 1K.
- NXP-branded or Fudan FM11RF08? Same protocol, same performance, ~30% cost difference. Fudan is fine for APAC / LATAM; NXP is safer for EU / North America procurement audit trails.
- Custom UID range or default? Sequential UID ranges cost 5,000 pc MOQ; default random UIDs from the chip supplier ship at 100 pc MOQ. Only order custom UIDs if the panel software requires specific facility-code structure.
Product Specifications
| Parameter | Value |
|---|---|
| Frekvencia | 13.56 MHz ± 200 kHz |
| Protokol | ISO/IEC 14443A layers 1-3, Crypto-1 layer 4 |
| Chip | NXP MIFARE Classic 1K (S50) or Fudan FM11RF08 (pin-compatible) |
| User memory | 752 bytes across 16 sectors × 4 blocks × 16 bytes (minus trailer blocks) |
| Encryption | Crypto-1 (48-bit stream cipher, mutual authentication) |
| UID | 4-byte (default) or 7-byte NUID (on request) |
| Read range | 3-5 cm typical; up to 8 cm on high-power readers |
| Reader compatibility | HID iCLASS SE / MultiClass SE, Iron Logic Matrix-II EH, Bolid Proxy-Key MFM, ZKTeco KR503/KR603, Anviz M7, Suprema BioEntry Plus (MIFARE variant), Hikvision DS-K1108MK, Dahua ASR2101A-M, ACR122U, PN532 modules, any ISO 14443A reader |
| Shell material | ABS engineering plastic, ultrasonic-welded |
| Standard shapes | Droplet 34 × 27 × 6 mm; oval 42 × 30 × 6 mm; round Ø32 × 6 mm |
| Stock colours | Blue, red, black, yellow, green, white, grey (Pantone custom, ΔE ≤ 2.0 verified on Konica Minolta spectrophotometer) |
| Split-ring hole | Ø3.5 mm; metal-reinforced insert optional |
| Hmotnosť | ≈ 5-7 g depending on shape |
| Prevádzková teplota | -25 °C to +70 °C |
| IP rating | IP54 standard; IP67 sealed variant at 1,000 pc MOQ |
| Uchovávanie údajov | > 10 years |
| Write endurance | > 100,000 cycles per block |
| Záruka | 5 years electronic + 2 years mechanical |
| MOQ | 100 pcs (stock); 500 pcs (custom colour or logo); 1,000 pcs (custom mould); 5,000 pcs (custom UID range) |
| Lead time | 7-14 business days standard; +30-40 days over Chinese New Year |
| Certifikáty | ISO 9001:2015, RoHS 2011/65/EU, REACH SVHC |
| HS Code | 8523.52 |
ČASTO KLADENÉ OTÁZKY
Can smartphones read the 13.56MHz Mifare 1K Keyfob?
Yes for UID; no for encrypted sector data. Any Android phone with NFC and any iPhone from 7 onward reads the fob’s 4-byte or 7-byte UID via NFC Tools, Mifare Classic Tool, or a custom app. To read sector data the app must know the correct Key A or Key B for each sector, which for a legitimately deployed system is held only by the installer. This is why Mifare Classic 1K remains acceptable for gym / hotel / office access despite the Crypto-1 weakness — the practical attack requires physical possession of an authorised fob plus a dedicated tool, not just a smartphone tap.
What is the difference between the 4-byte UID and the 7-byte NUID?
Older MIFARE Classic 1K chips use a 4-byte UID with roughly 4.3 billion address space, which NXP declared exhausted around 2013. Current-production NXP chips ship with a 7-byte “non-unique ID” (NUID) that expands the address space to 72 quadrillion. Both work on all readers. For deployments enrolling by UID rather than by encrypted sector data, verify the reader firmware handles 7-byte UIDs — some pre-2015 controllers were hardcoded to 4-byte and will not enrol 7-byte fobs. When ordering, specify 4-byte if the target system is legacy.
Can the fobs be pre-encoded with data before shipment?
Yes. Common pre-encoding services include: sector 1 write with facility code + sequential card number, MIFARE value-block initialisation for stored-value deployments, and NDEF record writing for URL-launch consumer applications. Provide the target data structure and any custom Key A / Key B, and every fob ships pre-encoded with CSV mapping of UID to encoded data.
Are Fudan FM11RF08 fobs actually 100% compatible with NXP MIFARE Classic 1K readers?
Yes at the protocol level. The FM11RF08 implements the same ISO 14443A commands and the same Crypto-1 authentication with the same 6-byte keys and same access condition semantics. In roughly 15 years of shipping FM11RF08 fobs to deployments spanning ZKTeco, Iron Logic, Suprema, and HID readers, we have not encountered a documented compatibility failure at the protocol layer. The one exception is deployments that enforce chip trademark validation at the reader firmware — some enterprise HID installations refuse non-NXP MIFARE chips as a procurement policy rather than a technical requirement.
Ready to Order?
Manufactured on one of five dedicated production lines inside a 5,000 m² Shenzhen facility operating since 2008, our 13.56MHz Mifare 1K Keyfob line ships to distributors, integrators, and enterprise buyers across 100+ countries. Customers who source Mifare Classic 1K fobs from us also frequently consolidate their POs across our full HF and LF fob range, DESFire EV2 high-security variants, ACR122U and PN532 desktop readers, and 13.56 MHz USB duplicators — one supplier across the 193-SKU RFID catalogue, one HS Code (8523.52), one customs clearance.
Request samples or a bulk quote:
- Email: [email protected]
- WhatsApp: +852 5989 6589
- WeChat: 147891664
- Or open a project ticket via our Kontaktujte nás page.
