Ask “what frequency does RFID run on?” and the honest answer is that RFID frequency by country is the only version of the question worth answering — it depends entirely on where the equipment will be switched on. Passive UHF RFID, the technology behind warehouse portals, apparel stock counts, pallet and asset tracking, sits somewhere inside the 860–960 MHz range. No single national allocation opens that whole range. Each administration carves out a narrower slice, sets its own radiated-power ceiling, and revises the rules from time to time. Buy a reader tuned for one slice, commission it in a market that uses another, and you inherit two problems at once: weaker read performance and an installation that is not compliant.
This guide covers the landscape neutrally: why the bands differ, which allocations buyers most often encounter, and how to verify the correct band for your own country rather than trusting a table on any vendor’s website, this one included. Everything below reflects widely published positions as of 2026. Spectrum rules change, so treat this page as orientation, not as regulatory or legal advice.
Why UHF bands differ from one country to the next
Radio spectrum is a national resource. Every administration decides which slices are licence-exempt, at what radiated power, and under what sharing rules — decisions shaped by whatever already occupies neighbouring spectrum locally, most often cellular and legacy land-mobile services. Because those legacy uses were never identical across regions, the short-range device allocations UHF RFID depends on could not be either. Regional harmonisation helps — European allocations, for instance, are implemented nationally on the back of CEPT and EU-level decisions — but harmonised is not universal.
Two things follow. First, EPC Gen2 (ISO/IEC 18000-63) is a global air-interface standard, but a global standard is not a global frequency licence: the protocol is portable, the spectrum permission is not. Second, the differences are not only about centre frequency. Channel plans, maximum power, duty-cycle limits and spectrum-access behaviour vary too. European-style regulation is generally built around listen-before-talk and channel-sharing rules, while the North American approach relies on frequency hopping across a wider band. Two readers can both be “UHF RFID” and still be legally and electrically different products. Our RFID frequencies guide covers the underlying physics of why that matters to read range.
The major allocations most buyers encounter
These are the long-established, widely cited allocations. Treat them as orientation and re-check anything you design around.
| Regulatory regime | Commonly cited UHF RFID band | Notes |
|---|---|---|
| North America (FCC Part 15) | approx. 902–928 MHz | Wide band, frequency-hopping approach; also referenced by several markets that follow FCC-style rules |
| Europe (ETSI EN 302 208) | 865–868 MHz | Listen-before-talk regime; adopted or mirrored by many non-EU administrations |
| India (WPC) | 865–867 MHz | De-licensed for low-power UHF RFID; narrower than the ETSI window |
| Elsewhere | varies | Several markets in Asia-Pacific, the Middle East and Latin America use allocations in the upper 900 MHz range; some maintain more than one band or split them by application class |
That last row is deliberate. China, Japan, Brazil, Australia, South Korea and the Gulf states each have their own arrangements, and several have been revised in recent years. Europe shows that even a familiar figure is rarely the whole story: alongside the 865–868 MHz window, additional spectrum in the upper 900 MHz range has been opened for RFID in parts of Europe, subject to national implementation. Publishing a confident megahertz figure for every country would make this page more quotable and less trustworthy. What we can say with confidence is that allocations and power limits do change, that “everyone in Asia uses the same band” is false, and that verification sits with the buyer and their supplier jointly — not with a blog post.
Tags are mostly global. Readers are the region-critical item
Most modern passive UHF tags and inlays are built on broadband chips and antenna designs intended to work across the full 860–960 MHz span. A tag is a passive device: it has no transmitter of its own and no region setting to get wrong. In practice a well-designed global-band inlay reads acceptably in both ETSI and FCC regions. Some inlays also come in region-optimised tunings that trade a little universality for extra range at one end of the spectrum — worth asking about if your read distances are marginal, and worth avoiding if tagged goods will be read in several countries along a supply chain.
UHF readers are the opposite case. A reader is an active transmitter, so its region profile — the channel plan, the permitted power, the spectrum-access behaviour — is exactly what a regulator cares about. Most professional fixed and handheld readers ship with selectable region profiles in firmware, but “selectable” is not automatic: the unit is configured to one region at dispatch, and on some models it is locked at the factory or needs a specific tool to change.
The failure modes when readers and region do not match are practical, not theoretical:
- Reduced read range and inconsistent captures, because tag tuning, reader channel plan and antenna are no longer working with each other.
- Non-compliant emissions in the destination market, with the operator — usually your end customer — carrying the exposure.
- Interference complaints where the mismatched band overlaps something the local regulator protects.
- Avoidable delay, when a shipment arrives correct in every respect except its region setting.
How to verify the band for your country
Do not take one source’s word for it, ours included. Three checks, in order:
- Go to the national spectrum regulator. Every administration publishes its short-range-device or licence-exempt allocation rules — the FCC in the United States, ACMA in Australia, ANATEL in Brazil, WPC in India, the relevant national administration in each European country. This is the authoritative source, and the one that gets updated.
- Cross-check against GS1 guidance. GS1 maintains and periodically republishes a summary of UHF RFID regulatory status by country, a practical way to notice that a rule has moved.
- Ask your supplier a direct question. Not “does this work in my country?” but “which region profiles does this reader firmware support, which one will it ship configured to, and can it be changed in the field?” Those are answerable questions, and a supplier used to export will answer them quickly and in writing.
One more detail: power limits are expressed differently across regimes — some in ERP, some in EIRP — so a headline wattage figure from one market is not directly comparable with another. If read range is critical to your business case, get the limit and the unit, not just the number.
HF, NFC and LF are the easy case
The regional complexity is essentially a UHF problem. HF and NFC at 13.56 MHz, and LF at 125/134.2 kHz, are globally harmonised bands — one card, wristband or animal tag design works everywhere, which is why credentials, ticketing and livestock identification standardised there. Product-level electrical safety and EMC approvals still apply wherever you sell, but you are not re-tuning the radio for each market. If you are still choosing a band, our comparison of UHF vs HF vs NFC walks through the trade-offs.
What to tell your supplier: a checklist
Send these eight items with your enquiry and most frequency problems disappear before quotation:
- Destination country or countries where the hardware will actually operate — not your billing address.
- Which region profile you need the readers configured to at dispatch.
- Whether the profile must be field-changeable, if units may be redeployed across markets later.
- Your power-limit constraint, with the unit (ERP or EIRP) as your regulator states it.
- Global-band or region-optimised tag tuning, and whether tagged goods will cross regions in transit.
- The read environment — metal, liquids, distances — since problems here look identical to a frequency mismatch in the field.
- Which compliance documents your customs broker, integrator or end customer will ask for.
- Who is responsible for any local type-approval or registration in the destination market.
Where Identium stands, stated plainly
We manufacture UHF, HF and LF hardware in New Delhi and sell both domestically and for export, so it is worth being precise rather than promotional here.
Our verified regulatory approval is for India: Identium is BIS certified, and our UHF readers and antennas are WPC-approved for India’s 865–867 MHz band. We do not claim to hold FCC, CE or other overseas marks, and we would apply the same scepticism to any certification list, ours included — ask to see the certificate and its scope. Instead, tell us the destination market at enquiry stage: we will confirm the correct region configuration for your order and discuss what documentation is realistic there before anything is built. Any local type-approval, import or registration requirement in the destination country should be confirmed with that country’s regulator or your own customs and legal advisers. Buyers importing from India can read our BIS and WPC buyer’s guide for the Indian side of that paperwork, and our manufacturer and exporter overview for what we build in-house.
Frequency is the one specification that cannot be fixed after delivery by adjusting software or swapping a bracket. Settle it first. Tell us where the system will run and we will tell you what needs to change — get in touch with your destination market and application, and we will work back from there.