125kHz vs 13.56MHz: Which RFID Card Reader Do You Need?

A 125kHz reader and a 13.56MHz reader are not a basic and a premium version of the same product. They work on different frequencies, talk to different chips and cannot read each other’s cards. So the first question is not which band is better, but which card you already have or plan to issue.

This guide compares the two bands the way we do when quoting a reader: card types, read range, memory, security, interfaces and output format. It ends with four quick checks for identifying an unknown card and a checklist for choosing the reader.

The short answer

• Choose a 125kHz reader when your cards or key fobs are EM4100, TK4100 or another EM4100-compatible proximity card. Suppliers often call these “ID cards”. They are common in existing door, time and attendance, locker and parking systems.
• Choose a 13.56MHz reader when your cards are MIFARE Classic, NTAG or other ISO/IEC 14443A cards (often sold as “IC cards”), or ICODE labels under ISO/IEC 15693.
• For a new project, 13.56MHz is usually the better base: more chip choice, on-card memory, anti-collision, and cards that NFC phones can also detect.
• During a migration from 125kHz to 13.56MHz, a reader that reads both bands lets old and new cards work side by side.

How 125kHz and 13.56MHz differ

Both bands are near-field technologies. The reader’s antenna coil creates a magnetic field. A passive card in that field takes its power from it and answers by varying the load it places on the field. Neither card type has a battery. The practical differences come from the carrier frequency and the chips designed for it.

Which cards live on each band

125kHz: EM4100 and compatible chips

An EM4100-type chip holds a 64-bit code fixed at manufacture. Forty of those bits are data: an 8-bit version or customer code and a 32-bit ID number. The rest are a header, parity bits and a stop bit. TK4100 and SMC4001 are compatible chips; a reader cannot tell them apart and outputs the same kind of number. The card stores nothing else, and its number cannot be changed. The full bit layout is in EM4100 and TK4100 cards explained.

Not every 125kHz card is EM4100. Some access-control systems use proximity formats with FSK or PSK modulation instead of EM4100’s ASK and Manchester coding. A reader built for EM4100 does not read them, even though both boxes say “125kHz”. Our 125kHz readers are specified for EM4100-compatible cards only.

13.56MHz: ISO/IEC 14443A and ISO/IEC 15693

13.56MHz is a band, not a single protocol. ISO/IEC 14443A dominates access, membership and NFC tags: MIFARE Classic 1K (S50) and 4K (S70), NTAG203 and NTAG213 all use it. ISO/IEC 15693 “vicinity” labels such as ICODE are common in libraries and item labeling. Readers support specific standards, so an ISO/IEC 14443A reader will not see an ISO/IEC 15693 label.

Our 13.56MHz readers read the UID of ISO/IEC 14443A cards, and the H155-U USB reader for ICODE labels covers ISO/IEC 15693. ISO/IEC 14443B, FeliCa and MIFARE DESFire are not listed for our readers. For the HF standards in detail, see ISO 14443 vs ISO 15693.

Read range: the housing matters more than the band

At card-reader distances, the band is not what decides range. Antenna size, reader power, card form factor and mounting do. Our 125kHz and 13.56MHz siblings share housings, and their specified ranges are the same:

Key fobs read at shorter range than ISO cards because their coil is much smaller, as the keypad reader’s 50 mm versus 15 mm shows. Metal behind the reader or the card detunes both bands. If you need to read passive tags at 1 m or more, neither band is the right tool; look at UHF RFID readers instead.

Security: what each band can and cannot protect

• EM4100 has no security features. There is no password, no encryption and no authentication. The ID is sent in the clear to any 125kHz reader in range, so the number alone cannot prove that a card is genuine. It works for identification where convenience matters more than strong protection.
• 13.56MHz chips vary widely. MIFARE Classic protects each sector with keys, but its proprietary cipher has published weaknesses. AES-based chips are the current choice for secure credentials.
• A UID-only system is an identification system on either band. Most keyboard-emulation and Wiegand card readers, including all our 125kHz and 13.56MHz models, read only the card UID. A UID can be read by any compatible reader without a key. Moving from EM4100 to MIFARE UID reading gives you more chip choice and phone compatibility, but not cryptographic security.

If your project needs cards that authenticate with keys, you need suitable HF cards plus a reader and software that perform the authentication. Our current 125kHz and 13.56MHz readers are read-only UID readers and do not do this.

Interfaces and output: the same options on both bands

The band decides which cards a reader can read. The interface decides how the number reaches your system, and here the two bands offer the same choices:

Because most USB and RS232 models on both bands default to a 10-digit decimal number, one software field can accept either card type. The value comes from different data: the 32-bit EM4100 ID on 125kHz and the 4-byte UID on 13.56MHz. NTAG203 and NTAG213 tags, MIFARE Ultralight and some MIFARE Classic cards carry a 7-byte UID, which does not fit in a 10-digit decimal number, so tell us if you use them and the output format will be confirmed before shipment. The card number formats guide and the card number converter show how one ID looks in each format.

How to identify an unknown card: 4 checks

1. Read the print. “EM”, “ID”, “TK4100” or “125KHz” points to LF. “IC”, “M1”, “S50”, “S70”, “1K” or “NTAG” points to HF. Many EM4100 cards also carry a 10-digit number plus a pair such as “212,12687”.
2. Try an NFC phone. Switch NFC on and hold the card to the phone’s NFC area. Any reaction, such as a sound, an app opening or an “unsupported tag” message, means 13.56MHz. No reaction does not prove 125kHz: the card could be UHF, or you may have missed the antenna spot.
3. Hold the card up to a bright light. On many thin white cards, a 125kHz card shows a small, dense coil with many turns, while a 13.56MHz card shows a few turns of antenna running near the card edge. Thick clamshell cards and heavily printed cards hide this.
4. Ask for the chip name. The card supplier or the system’s documentation should state it. The chip, not only the frequency, decides which reader works.

If you are still unsure, send a photo of both sides of the card, or a sample card, with your inquiry, and we will confirm the band and suggest a matching reader.

Migrating from 125kHz to 13.56MHz

Sites rarely replace every card in one day. Three approaches are common:

• Dual-band readers at the door. Install readers that read both bands, then reissue cards department by department.
• Dual-technology cards. Some cards contain a 125kHz chip and a 13.56MHz chip in one card body, so the same card works on old and new readers. Each chip has its own number, so the software must store the right one.
• Separate enrollment. Register the new 13.56MHz UID for each person while the old 125kHz number stays valid until the cut-over date.

For dual-band doors, our 86-box wall readers, the Q420-M slim QR code + RFID reader and the Q430-M QR code + RFID reader with USB output, read EM (125kHz) and MIFARE (13.56MHz) cards as well as QR codes; on the Q430-M, setting codes select IC-only or IC + ID reading. The Wiegand wall reader also has a dual-frequency D410-W version, with availability confirmed in your quotation. Our current USB desktop pads are single-band, so an enrollment desk that handles both card types uses one L-series and one H-series pad, or a Q430-M connected over its USB port, which can type the card number like a keyboard.

Checklist: how to choose the reader

1. Identify the chip, not just the frequency: EM4100-compatible, ISO/IEC 14443A (MIFARE, NTAG) or ISO/IEC 15693 (ICODE).
2. Match what is installed. Existing controllers and printed cards fix the band and often the number format.
3. For a new system, start from 13.56MHz ISO/IEC 14443A cards unless you need ISO/IEC 15693 item labels.
4. Decide what the reader must deliver. Our readers deliver the card UID. Reading or writing card memory needs a different class of reader.
5. Pick the interface for the host: USB keyboard emulation for PC software and spreadsheets, RS232 for serial hosts, Wiegand for access controllers, USB-C RFID readers for Android phones and tablets, Bluetooth for mobile use (iOS and Android are listed for the H510-B).
6. Fix the output format your software expects: 10-digit decimal, hex, reversed byte order, or a Wiegand facility code and card number.
7. Check range against the credential. Plan on a shorter range for key fobs and small tags, and avoid mounting readers directly on metal.
8. Test before rollout. Order sample readers and try them with your own cards. For volume orders with your logo or a custom output format, see private-label RFID readers; terms are confirmed in your quotation.