RFID Key Fob Types for Access Control: How to Choose the Right One
Jul 01, 2026
Leave a message

RFID key fobs differ along three lines: the credential technology inside (frequency and chip), the housing around it, and whether the fob is passive or battery-powered. The chip decides whether a fob works with your readers and how hard it is to copy. The housing decides how long it lasts. This guide sorts the common types by those lines so IT, facilities and procurement teams can shortlist the right fob before asking for samples.
Short answer: match the frequency, chip family and data format to your existing readers first, choose the security level for your actual risk, and pick the housing last. Two fobs that look identical can carry completely different chips.
RFID Key Fob Types at a Glance
Most product listings sort fobs by shape or color. For an access-control decision, sort them first by what the reader sees:
| Fob type | What the reader receives | Copy resistance | Typical fit | Verify before ordering |
| 125 kHz read-only (EM4100 / TK4100) | A fixed ID number | Low: no encryption or challenge-response | Existing 125 kHz systems, low-risk doors, lockers | Reader brand and the ID format it expects |
| 125 kHz proprietary prox (e.g. HID Prox format) | A formatted ID (facility code + card number) | Low: no cryptographic authentication | Replacing fobs in an installed prox system | Exact format, bit length and facility code |
| 13.56 MHz MIFARE Classic | UID and/or sector data protected by Crypto-1 keys | Limited: keys can be recovered with published attacks | Membership, cashless, internal doors where a clone is an inconvenience, not a breach | UID-only or sector data, and who holds the keys |
| 13.56 MHz MIFARE DESFire EV3 | Application data after AES mutual authentication | High, if keys are managed and diversified properly | New installations, sensitive areas, multi-application credentials | Reader and firmware support, application ID, key ownership |
| 13.56 MHz NFC tags (NTAG family) | UID and/or NDEF data readable by phones | Low to moderate, depending on configuration | Membership, visitor passes, tap-to-open-a-link use | Whether the system uses UID, NDEF content or both |
| Dual-frequency (LF + HF in one housing) | Two independent credentials, one per band | Equal to the weaker chip on any door that reads it | Phased migrations from 125 kHz to 13.56 MHz | Both chips and both formats, tested on both reader generations |
| UHF (860–960 MHz) tags | An EPC/TID read at a distance | Depends on chip features and system design | Vehicle gates, asset and logistics tracking | Regional band, mounting surface, antenna placement |

Shape, color and material tell you nothing about compatibility; the chip and its data format do. Two fobs that look identical can carry completely different chips, and two fobs that look nothing alike can carry the same one.
Almost all door-access fobs are passive: they have no battery and take power from the reader's field when presented. Battery-powered active tags exist, but they are used where long read distance matters more than cost, such as some vehicle and asset applications.
Types by Frequency and Chip: The Compatibility Decision
Readers are built for a frequency band, and a reader built only for 125 kHz will not read a 13.56 MHz fob, or the reverse. Matching the band is only the first step: within a band, the chip family and the data format must also match what the controller expects. For a deeper treatment of band selection, see choosing the right frequency for RFID key fobs.
125 kHz (Low Frequency)
Common LF fobs such as EM4100 and TK4100 key fobs transmit a fixed identifier with no handshake and no encryption. That makes them inexpensive and easy to integrate with older readers, and it is also why they are easy to duplicate. Writable LF chips such as T5577 can be programmed to emulate other LF formats, which is useful for replacements but is also how many LF copies are made.
"125 kHz" alone is not a compatibility guarantee. Proprietary prox formats, such as HID Prox, use their own data layout, so a generic EM-format fob may not be accepted by a prox system even though both run at 125 kHz. Confirm the format and test a sample on the installed readers; the note on ordering HID Prox-compatible credentials lists the details to collect.
13.56 MHz (High Frequency)
HF fobs used for access control generally follow the ISO/IEC 14443 proximity standard, which is what lets compliant readers and credentials work together. Three chip families account for most HF fobs:
- MIFARE Classic 1K. Widely installed and low cost. Its proprietary Crypto-1 cipher was reverse-engineered and broken in published research (Garcia et al., "Dismantling MIFARE Classic", ESORICS 2008), which showed keys could be recovered from communication with a genuine reader. Treat it as a convenience credential. A 13.56 MHz MIFARE 1K key fob fits membership, cashless and low-risk door applications.
- MIFARE DESFire EV3. NXP's MIFARE DESFire EV3 product page lists hardware AES with 128-bit keys, mutual three-pass authentication, Common Criteria EAL5+ certification for hardware and software, and a backward-compatibility mode for DESFire EV2, EV1 and D40. Those features are why DESFire is a common starting point for new installations where cloning is a real threat. Security still depends on how keys are generated, diversified and held.
- NTAG (NFC Forum tags). Designed to be read by phones, which suits visitor passes, membership check-ins and product interactions. Most configurations are not intended as hardened access credentials.
Dual-Frequency Fobs
A dual-frequency key fob carries an LF chip and an HF chip in one housing, so one credential can open doors on both reader generations during an upgrade. Each door only checks the chip its reader supports, so an LF door stays as easy to defeat as any LF door until it is replaced.
UHF
UHF tags are read at distances measured in metres rather than centimetres. That suits vehicle gates, yards and asset tracking, where hands-free reading is the point.
At a pedestrian door, long range can work against you, because a credential may be read when the holder did not mean to present it. Keep UHF for gates, vehicles and assets.

Types by Security Level: What Can Be Copied
Whether a fob "can be cloned" depends on what the reader trusts:
| Security tier | Examples | What an attacker needs | What it means for buyers |
| Fixed ID, no authentication | EM4100, TK4100, LF prox formats; any system that checks only the UID | A brief read of the fob and a writable blank | Use where a copied fob is an acceptable risk, or plan an upgrade path |
| Legacy cryptography | MIFARE Classic (Crypto-1) | Published attack methods and suitable tools | Acceptable for convenience use; not for doors where a clone is a breach |
| AES mutual authentication | MIFARE DESFire EV3 | The secret keys, which proper key management keeps out of reach | Specify key ownership and diversification before production |
A common myth is that a phone can copy any RFID fob. A phone with NFC can read and emulate open 13.56 MHz tags, but it cannot read 125 kHz fobs at all, and it cannot complete an AES authentication without the keys.
The chip is only part of a secure installation. Three system-level measures matter as much:
- Reader-to-controller wiring. The Security Industry Association describes OSDP as an open standard for communication between access panels and readers, with bi-directional, supervised communication and a Secure Channel that supports AES-128. It was published by the IEC as IEC 60839-11-5 in 2020. Wiegand wiring offers none of those protections, so an encrypted fob behind an unprotected Wiegand link leaves a gap.
- Key diversification. Each fob derives its own key from a master key, so one compromised fob does not expose the others.
- Role-based permissions and audits. The NIST RBAC model, adopted as ANSI/INCITS 359, is a common reference for assigning access by job function. Review logs, remove unused credentials and keep reader firmware current.
More checks are covered in the RFID data security buyer checklist.
Types by Housing: Match the Environment
The housing protects the chip and antenna. It sets durability and appearance far more than it sets compatibility. Metal housings are the exception to watch: metal near the antenna can affect reading, so test metal designs on the actual readers.
| Material | Character | Where it fits |
| ABS plastic | Light, low cost, easy to mold and print | General office and residential access |
| Epoxy | Glossy, sealed surface | Promotional or branded fobs, frequent handling |
| Silicone | Soft and flexible | Gyms, pools and other wet areas |
| Leather | Premium feel, takes embossed or printed logos | Hotels, residences, corporate gifts |
| Wood | Natural material, distinctive look | Design-led or eco-focused brands |
Ask the supplier for tested ratings, such as ingress protection or temperature range, when the environment demands them; do not assume them from the material name. For a material-by-material comparison, see the RFID key fob material guide and the range of leather RFID key fobs.
Five Checks Before You Order a Fob Type
Most failed fob orders happen because the buyer matched the frequency and assumed the rest would follow. Work through these before a bulk order:
- Step 1 – Identify the reader and controller. Record the brand, model and firmware from the installed reader or the panel documentation. Some readers need a firmware update or configuration change before they accept a DESFire application.
- Step 2 – Identify a working credential. Printed markings or a scan with a diagnostic reader usually reveal the chip type and format.
- Step 3 – Confirm what the system checks. UID only, a facility code and card number, or an encrypted application with specific keys. Each needs different data from the supplier.
- Step 4 – Decide key ownership. For encrypted credentials, agree who generates and holds the master keys, and how they are diversified, before production.
- Step 5 – Test a finished sample on live readers. A blank housing confirms appearance only; an encoded sample confirms the system accepts it.
- The key fob compatibility test guide describes how to approve a sample, and how to choose a proximity key fob covers each compatibility layer in detail.
Moving From One Fob Type to Another

Upgrading from 125 kHz to encrypted 13.56 MHz fobs does not have to happen in one weekend. A common approach is to replace readers in stages, issue dual-frequency fobs so each user carries one credential throughout, and move reader wiring to OSDP as each area is cut over.
The plan only works if decisions are made early: the HF chip must be supported by the new readers, master keys must be generated and held by the system owner, and the encoded data on both chips must be confirmed on a sample before the full batch is produced. Once the last LF reader is gone, the LF credential can be removed from the access database.
Encoding and Bulk Sourcing
"Programming" a fob means writing its identity, keys or application data. There are three common ways to do it:
- Factory encoding. The supplier writes numbers or data before shipment from a data file you approve. This suits large rollouts.
- On-site encoding. You enroll or write fobs with a desktop encoder or the access system's software. This suits frequent changes.
- Controlled key loading. For encrypted credentials, keys and applications are loaded under agreed security procedures. Define who supplies the keys and how they are protected before anyone quotes.
Send the supplier a complete data pack:
Chip type, plus the format or bit length the system expects
Facility code and card number range, or the UID rules
Encoding method and who supplies any keys
Housing, color, printing and numbering requirements
The approved sample reference for the bulk order
The RFID key fob OEM spec sheet guide lists what each field should contain. Minimum order quantity and lead time depend on the chip, the housing (stock or new mold) and the encoding work, so ask for both in writing against your exact specification.
Syntek's OEM/ODM service supports sample production, artwork confirmation, data encoding tests and bulk manufacturing. Browse the RFID key fob range, or send your reader details and a sample request to confirm compatibility before production.
Request a Compatibility Sample
FAQ
Send Inquiry

