On this page
LF, HF and UHF: what should a buyer compare?
Start with the intended action: identify an existing credential, open a phone link, authenticate a card or count items passing a checkpoint. These technology families are not interchangeable specifications.
| Buying question | LF | HF / NFC | Passive UHF / RAIN |
|---|---|---|---|
| Common frequencies | 125 kHz or 134.2 kHz; confirm the system | 13.56 MHz | Regional UHF bands; confirm the reader configuration |
| Starting point | An installed LF identification system | Deliberate taps, contactless cards or NFC phone interactions | Inventory, item tracking and controlled batch reading |
| Protocol checks | Exact encoding and data format | ISO/IEC 14443, ISO/IEC 15693 or other specified technology | EPC Gen2 / ISO/IEC 18000-63 and required commands |
| Built-in phone NFC | Does not read LF credentials | Supported tags and functions only | Does not read UHF inventory tags |
| Distance and security | Verify the complete implementation | Verify the complete implementation | Verify the complete implementation |
When does LF RFID make sense?
LF is a starting point when extending an existing LF installation. A 125 kHz access credential and a 134.2 kHz animal identification system have different requirements; matching the broad band does not make their tags interchangeable.
LF does not mean every chip is read-only. EM4200 is a read-only identification IC, while EM4205/EM4305 provide read/write functions. Confirm the chip variant, encoding and identifier format accepted by the reader. For access projects, have the administrator approve enrollment and replacement before ordering personalized credentials.
HF and NFC: will a phone read the tag?
NFC operates at 13.56 MHz, but an HF label is not automatically phone-ready. The tag technology, accessible data and phone software must support the action. Detecting a card does not grant access to protected files or authorize a door credential.
For tap-to-website projects, specify a supported NFC tag with an NDEF URI record. Apple documents conditions for background reading; Android distinguishes NDEF handling from direct tag communication. Test the final URL on target phones, operating systems, cases and tap positions. State whether writing requires an app and whether delivered tags will be writable or locked.
UHF RFID: match the region and read zone
Passive UHF, often called RAIN RFID, is a candidate for identifying multiple items without presenting each tag to a tap point. The current GS1 EPC Gen2 air-interface specification covers 860–930 MHz. Catalogs also use 860–960 MHz as a broad label. Neither label authorizes every channel in every country.
Provide all deployment countries and confirm the reader configuration and tag antenna coverage. For carton or pallet trials, include real packing patterns, tag positions and nearby stock. The useful outcome is a defined read zone with acceptable missed and unwanted reads, rather than an isolated maximum-distance result.
Metal and liquids: test the finished assembly
A label tested in air is not evidence of performance on steel, a liquid container or a body-worn item. Surface, spacing, curvature, antenna orientation and adjacent objects can change the result. Selecting LF alone does not solve metal mounting.
NXP explains how metal changes NFC antenna behavior and how suitable ferrite shielding can help. UHF on-metal products use constructions designed for that application; a generic ferrite or foam recipe is not interchangeable across bands. Attach representative samples to the actual assets before approving a design.
Security comes from the chip and system
A band cannot rank every product as low, medium or high security. Reading a public identifier, writing memory and completing cryptographic authentication are different functions. The reader and application must correctly use the selected chip’s protection features.
DESFire EV3, for example, supports AES-128 and application authentication. These are features of the selected chip; reading a DESFire UID does not authenticate its holder. Define the required protection, provisioning owner, key handling and replacement process with the integrator. Share only non-secret configuration information in an initial inquiry.
Identify the reader before ordering replacements
A reader logo, housing color or USB connector cannot establish compatibility. Ask the operator or integrator for:
Dual-frequency credentials contain separate technologies; each side must be supported and enrolled independently. For a reader replacement, confirm the exact revision and software migration requirements before purchasing evaluation hardware.
- Reader/controller model, firmware, regional settings and supported tag protocols.
- Credential specification, non-secret data format and enrollment procedure.
- Required operation: identifier capture, memory read/write, NDEF encoding or authenticated commands.
- Host interface, operating system and software or SDK support.
Choose between deliberate taps and batch reading
Customer phone taps and warehouse inventory are different interactions. Define the trigger, reader location and expected business event before comparing hardware.
Near-field UHF arrangements and HF multi-tag systems also exist. Treat tap and batch as workflow requirements to verify, not absolute capabilities assigned by a frequency label.
| Workflow | Starting point | Pilot acceptance |
|---|---|---|
| Replacement access card or fob | Installed credential specification | Enrollment, permitted access, revocation and replacement |
| Customer taps a product label | Supported NFC tag and NDEF URL | Correct page opens on representative phones and packaging |
| Inventory or dispatch checkpoint | UHF reader, antenna and tags | Required items captured; adjacent stock excluded |
| Existing library system | Documented HF or UHF implementation | Compatible data, circulation equipment and security workflow |
Build a useful sample request
Agree acceptance conditions before comparing quotations. Specify finished size, attachment, encoding and test objects; record reader settings so samples are assessed under comparable conditions.
Keep the approved chip, antenna, housing and data specification with the sample record. This helps evaluate repeat orders and proposed material substitutions before they affect an installed system.
- Test orientations and positions throughout the required read zone.
- Record successes, misses and unwanted reads across repeated realistic trials.
- Repeat functional checks after relevant handling or environmental testing.
- Confirm sample costs, setup and encoding charges, quantities and delivery schedule.
Common decisions
Questions buyers ask before choosing
What frequencies are used for RFID?
Common LF systems use 125 kHz or 134.2 kHz. HF uses 13.56 MHz, including NFC. Passive UHF uses regional channels; the current GS1 EPC Gen2 specification covers 860–930 MHz. Confirm operating region, reader settings and tag specification rather than treating a broad catalog band as a complete configuration.
Can a 125 kHz tag work with a 13.56 MHz reader?
A reader supporting only 13.56 MHz cannot read a 125 kHz tag. A multi-technology reader or dual-frequency credential may support both, but each frequency, protocol and application must be explicitly supported. Sharing a housing or connector does not establish compatibility.
Can an iPhone or Android phone read every HF RFID card?
No. Built-in phone NFC works with supported 13.56 MHz technologies and functions. The chip, data, formatting, operating system and app or background-reading support determine the result. Detecting a card does not grant access to protected files or authorize a payment or door credential.
How far can LF, HF and UHF RFID read?
No distance is guaranteed for an entire band. Reader and tag antennas, power, orientation, mounting and environment determine the usable read zone. Define your required operation and distance, then validate representative finished tags with the intended reader and local settings.
Which RFID frequency works on metal or liquid containers?
Choose a construction designed for the surface and validate it on the actual object. Frequency alone does not solve antenna interference. HF/NFC shielding and UHF on-metal designs are different; a successful bare-tag test does not qualify the mounted product.
Is HF RFID always more secure than LF or UHF?
No. Security depends on the chip, authentication, key management and application. A readable identifier is not proof of authentication. Confirm that both credential and reader implement the required protection; do not infer encryption from the frequency.
Can I use the same UHF tags in several countries?
Possibly, if the selected antenna covers the required regional bands. Readers must also have the correct regional configuration and meet deployment requirements in each country. Confirm every destination and test the combination instead of relying only on a global label.
What should I send for a frequency recommendation?
Send the application, countries, installed reader or target phones, required operation and read zone, mounting material and tag size. Include sample and production quantities. An authorized sample or non-secret specification helps; live keys and personal credential records are not needed.
Move from the guide to a sample
Product options to investigate
These pages describe product formats. Confirm the exact chip, construction and system compatibility for your selected configuration.
Custom PVC RFID Card
Compare blank, printed and encoded PVC RFID cards by chip, artwork, dimensions and issuer workflow. Review a representative sample before bulk ordering.
RFID Keyfob
Compare RFID keyfob housings after confirming the reader and credential format. Plan authorized samples, numbering and repeat orders for access programs.
Custom NFC Sticker
Choose custom NFC stickers by NDEF content, chip memory and mounting surface. Approve artwork and encoded samples on the target phones before production.
Custom UHF RFID Sticker
Select UHF RFID stickers by item, finished inlay and reader setup. Confirm EPC data, printing and roll format, then validate mounted samples.
HF Library RFID Label
Specify HF library labels around the reader protocol, library data format and circulation workflow. Validate checkout, returns, gates and shelf inventory.
RFID Reader Writer
Choose an RFID reader writer by card protocol, read/write task and host software. Compare USB, network and OEM hardware before requesting an evaluation.
Check the basis for your decision
Sources and technical references
Chip and standards references describe their own scope. They do not establish a finished product’s read distance, durability or compatibility.
- EM Microelectronic: EM4200
Read-only LF IC, operating frequencies and protocol options.
- EM Microelectronic: EM4205/EM4305
Read/write LF ICs, encoding and ISO 11784/11785 support.
- Texas Instruments: 134.2 kHz RFID
An LF reader example used to verify the frequency, not a recommendation of current availability.
- NFC Forum: NFC technology
13.56 MHz technology and NDEF messages.
- Apple: background tag reading
NDEF URI handling and background-reading conditions.
- Android Developers: NFC basics
NDEF handling and communication with tags.
- GS1: EPC Gen2 standard
Current passive UHF air interface with a scope of 860–930 MHz.
- NXP: PN7120 antenna design
Section 2.2: metal influence and ferrite shielding.
- Impinj: choosing a RAIN RFID tag
Region, mounting, attachment and read-zone considerations.
- NXP: MIFARE DESFire EV3
AES-128 and application authentication for this specific IC.