125 kHz RFID vs 13.56 MHz NFC: What Is the Difference?

[Pavel]

Short answer: 125 kHz systems are low-frequency RFID commonly used for simple proximity identifiers, while NFC operates at 13.56 MHz and is a compatible subset of broader HF RFID technologies with different coupling, protocols and data capabilities. Readers and antennas are not interchangeable across the bands.

Before you start​

• Limit capture and protocol testing to equipment and networks you own or have explicit permission to assess.
• Choose hardware for the protocol and capture mode, not frequency coverage alone: Wi-Fi monitor mode, BLE sniffing, low-frequency RFID and NFC use different interfaces.

Step-by-step method​

1. Step 1: Identify tag frequency from documentation or a safe reader test. A card's physical shape does not reveal whether it is LF, HF or dual-technology.
2. Step 2: Choose a reader and antenna for 125 kHz or 13.56 MHz specifically. Check supported protocols, not only carrier frequency.
3. Step 3: For owned tags, read public identification and capability information first. Do not attempt access-control cloning or protected application data without explicit authorization.
4. Step 4: Record tag type, reader firmware, coupling distance and successful command set. Keep identifiers redacted in public screenshots.

Concrete example​

A 125 kHz proximity credential may transmit a fixed identifier with relatively simple modulation, while a 13.56 MHz NFC card can support anti-collision and higher-level applications. An NFC phone generally cannot read 125 kHz tags.

How to judge the result​

The technology is identified when carrier frequency, reader support and observed protocol agree; do not label every contactless card NFC.

What to record​

• Document channel, bandwidth, adapter chipset and driver mode so another authorized tester can reproduce the capture.
• Verify that captured frames pass checksum or integrity checks before interpreting higher-layer fields.
• Redact MAC addresses, SSIDs, tag identifiers, tokens and payloads before sharing files publicly.

Common mistakes​

• Changing several hardware, software or RF variables at once, which removes the controlled comparison needed to identify the cause.
• Treating one autoscaled screenshot or one unusually good result as proof without recording the settings and repeating the test.
• Buying an NFC reader for a 125 kHz tag fails even though both products are described as RFID.

Final check​

Repeat the capture only against the owned or authorized device and verify valid frames after sanitization. Reopen the final shared file to confirm that identifiers, tokens and payloads are gone.