Reader compatibility

125 kHz vs 13.56 MHz RFID: start with your reader

A frequency is only the first check. Match the protocol, credential format and application before ordering cards or keyfobs.

The practical answer

125 kHz LF and 13.56 MHz HF are different RFID families. NFC operates at 13.56 MHz. A reader must explicitly support the frequency and protocol of the chosen credential; a shared frequency alone does not establish compatibility.

NFC Forum — NFC technology overview ↗
FamilyFirst questionWhat to confirm next
125 kHz LFDoes the reader support LF?Chip family and ID format
13.56 MHz HF / NFCWhich protocols are supported?Chip, data layout and software

1. Collect the exact reader model

Photograph the model label and obtain the reader documentation from the system supplier. Note the controller and software version as well as the working credential. A card’s printed number or color is not enough to identify its radio technology. A supported multifrequency reader can handle both bands, but this is a specific reader capability, not a universal feature.

NXP — PRH601 multifrequency reader ↗

2. Check more than the frequency

Ask which chip families and protocols the reader supports, and whether the software reads a UID or application data. For a secured system, clarify enrollment, key provisioning and data layout with the integrator. Do not replace a specified chip with a vaguely described “IC card” just because both operate at 13.56 MHz.

3. Run an end-to-end sample test

Use the intended finished card or keyfob. Enroll it, test the relevant doors or terminals and verify the software record. Test several reader positions and the intended carrying or mounting conditions. Successful radio detection is only one step; the application must also accept the credential and apply the right permissions.

4. Plan replacements and future expansion

Keep the approved chip specification, encoding format and sample reference with the purchase order. If moving from an existing system, define whether old and new credentials must coexist and have the integrator confirm the migration path. Request the same test for each new reader or terminal model rather than assuming the first approval covers every installation.

Technical references

Chip specifications come from the sources below. Selection advice is a project checklist, not a compatibility guarantee.

Formats to consider

Browse all products

These catalog options are a starting point. Chip choice, reader support and the finished sample need confirmation for your project.