How to Read RFID: A Practical Guide (NFC/HF vs UHF) + Setup, Software, and Troubleshooting

To read RFID means to use an RFID reader to detect a tag and retrieve data stored on it (an ID, EPC, UID, or user memory). With passive tags, the reader also provides the RF energy the tag needs to respond.

The “how” depends on the RFID type:

• NFC / HF (13.56 MHz): very short-range (tap/close) inductive coupling.
• UHF (RAIN RFID, 860–960 MHz): longer range (meters), fast multi-tag reading, widely used in logistics/retail.

Step 1: Identify what kind of RFID tag you have

Most reading failures happen because people try the wrong frequency.

RFID type	Frequency	Typical read method	Common standards	Can a phone read it?
NFC / HF	13.56 MHz	Tap / close-range	NFC Forum / ISO 14443 family	Yes (most phones with NFC)
UHF (RAIN RFID)	860–960 MHz	Meter-level, multi-tag	ISO/IEC 18000-63 / GS1 UHF Gen2	No (not without external UHF hardware)
LF	~125/134 kHz	Very close range	(varies)	Generally no

Fast rule:
If you’re trying to read warehouse/asset/inventory UHF tags, your phone won’t do it—phones are built for NFC (13.56 MHz), not UHF.

Step 2: Pick the right reader for your scenario

A) Reading NFC / HF tags (13.56 MHz)

Options:

• Smartphone (NFC app): great for UID/NDEF type use cases (tap-to-read).
• USB NFC/HF reader: for PC-based reading, access control, library tags, etc. HF reader/writer concepts are commonly documented in reader IC application notes.

B) Reading UHF tags (RAIN RFID)

Options:

• Fixed reader + external antennas: portals, dock doors, lanes, production lines.
• Integrated reader (reader+antenna in one): simpler installations, controlled zones.
• Handheld UHF reader: mobile inventory, asset audits, item finding.
  UHF systems implement ISO/IEC 18000-63 (aka GS1 UHF Gen2).

Step 3: Hardware setup (UHF is where setup really matters)

If you’re reading UHF, your “reader” is a system:

1) Connect antennas correctly

• Fixed readers typically have SMA antenna ports (e.g., 4-port / 8-port / 16-port designs).
• Use quality coax cables; long/cheap cables can eat RF power.

2) Place antennas to control the read zone

• Use directional antennas for portals/lanes.
• Prefer circular polarization when tag orientation is random (common in cartons/pallets).
• Avoid “blast power everywhere” (it causes stray reads and messy data).

3) Set the correct region (regulatory bands)

UHF must match your region plan (EU vs US vs others). RAIN systems are standards-based around ISO/IEC 18000-63; region settings ensure legal operation.

Step 4: Use software to start reading

“Reading RFID” is usually done via:

• Vendor demo tool (fastest for first tests)
• SDK/API (for your own app)
• LLRP (standardized reader control in many UHF ecosystems)

GS1 describes the EPC “Gen2” air interface and protocol ecosystem used by UHF tags/readers.

Best practice for first test:
Start with a vendor tool → confirm tags are being seen → then move to SDK/LLRP once RF basics are stable.

Step 5: What data are you actually reading?

UHF (EPC Gen2 / ISO 18000-63) memory you’ll see

Most UHF tags expose memory “banks” such as:

• EPC (the ID you usually track)
• TID (chip/tag identifier info)
• User memory (optional)
• Reserved (password-related fields)

These concepts are defined in the Gen2 protocol standard.

NFC / HF (typical)

Common reads include:

• UID (identifier)
• NDEF records (URLs, text, etc., if it’s an NFC tag)

NFC operates at 13.56 MHz and supports short-range tag reading in reader/writer mode.

Step 6: Turn “raw reads” into clean results (so your system is usable)

Readers may output the same tag many times per second. Real deployments usually add a “filter layer” that:

• removes duplicates within a time window
• maps antennas to zones (Dock Door 1 vs Door 2)
• turns reads into business events (arrived / departed / shipped / received)

This is exactly why EPCIS exists as a standard to share “what happened, where, when” event data in supply chains.

Common problems (and how to fix them)

“My phone can’t read this RFID tag”

Likely it’s UHF, not NFC. Phones generally read NFC (13.56 MHz) only; UHF needs an external UHF reader.

“Reader sees tags sometimes, then misses them”

Typical causes:

• tag orientation changes (polarization mismatch)
• metal/liquid near the tag detunes it
• antenna placement creates dead zones or reflections
• power too high → stray reads + noise

“Works in the lab, fails in the warehouse”

Warehouse environments are RF-chaotic. Fix by:

• narrowing read zones (directional antennas, shielding if needed)
• adding triggers (photoeye/PLC) to read only when items pass
• validating with real packaging, not “demo tags”

Quick “first success” checklist (UHF)

1. Confirm tags are UHF Gen2 / ISO 18000-63 compatible.
2. Use one antenna first, short cable, moderate power.
3. Test 1 tag at a time at known distance/orientation.
4. Only then expand to multiple antennas + moving items.

Syncotek Service

If your goal is reading UHF tags in real workflows (fixed portals, integrated zones, handheld inventory), Syncotek’s RFID catalog covers UHF integrated readers, UHF fixed readers, handheld RFID devices, antennas, and tags.
Example fixed reader product pages also highlight multi-interface/multi-OS development support for integration projects.

FAQ: How to read RFID

Can I read RFID with my phone?

You can read NFC/HF (13.56 MHz) tags with NFC-enabled phones at very short range, but not typical UHF inventory tags without external UHF hardware.

What’s the easiest way to read UHF RFID tags?

Use a UHF reader + proper antenna, start with vendor demo software, then integrate via SDK/LLRP when your read zone is stable. UHF RAIN systems are based on ISO/IEC 18000-63 / GS1 UHF Gen2.

Why can RFID read multiple tags at once?

UHF Gen2 systems support anti-collision inventory so readers can identify many tags in the field efficiently (implementation details live in the Gen2 protocol).