ACCESS CONTROL
31 AUGUST 2026

Most conversations about RFID start in the wrong place. Someone asks for RFID wristbands, the supplier asks which chip, and the answer comes back as a brand name copied off an old spec sheet. Then the readers arrive on site and the two do not agree.
The chip is not a box you tick. It decides how far away a credential can be read, how fast, how many at once, and whether a phone can read it at all. Get it wrong and you find out at the gate, which is the worst possible place to find out anything.
Here is the short version, without the acronym soup.
Start with the frequency, not the brand name
RFID is not one technology. It is three frequency bands, and they behave in genuinely different ways. We work across all three, and across fourteen chip families, because no single one covers every job.
Low frequency (125 kHz). Short range, slow, very tolerant of moisture and metal. You still meet it in legacy building access. It is rarely the right answer for an event today.
High frequency (13.56 MHz). This is where NFC lives, along with MIFARE and NTAG. Read range is a tap: a few centimetres, one credential at a time. Deliberately so.
Ultra high frequency, or UHF (roughly 860 to 960 MHz depending on region). Range in metres, and it reads many tags in the same moment. This is the band for portals and zone counting.
That last bracket matters. The UHF band is not identical in every country, so a tag tuned for one market can underperform in another. If your event travels, say so before you order.
The tap: NTAG, MIFARE and the rest of the 13.56 MHz family
Everything in this band behaves the same way at the door. Someone presents the wristband or badge, a reader a few centimetres away picks it up, one person at a time. It is a queue you control.
NTAG. NFC Forum compliant, small user memory, and readable by any modern smartphone with NFC switched on. Good when you want a wristband to open a URL, carry a simple identifier, or let staff check something with the phone in their pocket instead of a dedicated reader.
MIFARE Classic. The widest installed base in the world, which is exactly why people keep specifying it. Worth knowing: its proprietary security was publicly broken years ago. Perfectly fine as an identifier that your system validates server side. Not where you would hold a cash balance.
MIFARE Ultralight. Low memory, built for credentials that live one event. The workhorse of single-use ticketing.
MIFARE DESFire. Real AES encryption and a file structure, which is why cashless and multi-operator venue access tend to end up here. It carries a higher unit cost and it earns it when there is money or personal data on the credential.
The practical takeaway for this whole band: a phone can read it. For small teams, spot checks and backstage sign-offs, that is worth a lot.
UHF: reading a crowd, not a person
UHF is not a better version of NFC. It is a different job.
A UHF reader picks up credentials several metres away and reads a lot of them at once. That is what you want for a portal people walk through, for knowing how many bodies are in a room, or for stewarding a site where stopping everyone to tap would create the exact queue you were trying to avoid.
The trade-offs are real. Phones cannot read UHF, so every check needs dedicated hardware. Range is a feature until it is not: a reader that sees three metres also sees the person standing behind the barrier who has not entered yet, so portals need tuning and shielding. And the human body is mostly water, which detunes a UHF antenna. A UHF wristband has to be engineered to work on a wrist, not just on a table.
So which one
Ask what happens at the moment of contact.
Someone stops, presents, and is checked individually. Access levels, backstage, registration desks, session doors. High frequency, and which family depends on your security needs.
Money or personal data sits on the credential itself. DESFire, or an equivalent with real encryption.
Attendees keep walking and you need a count or a zone read. UHF.
Staff need to verify credentials with the phones they already carry. NFC compliant high frequency, NTAG or Ultralight.
The credential has to survive several days outdoors and still read. That is a material and construction question as much as a chip one, and we cover it in our guide to choosing event wristbands.
Plenty of events run both. A UHF portal at the perimeter and a high frequency tap at the backstage door is a normal, sensible setup, not a compromise.
The four questions to send your supplier
Before you approve anything, get these in writing.
1. The exact chip reference, not the family. MIFARE is not a specification. MIFARE DESFire EV3 2K is.
2. A sample encoded the way you will actually use it, tested on your readers. Not a blank one.
3. The frequency band, confirmed against the country you are operating in.
4. Who encodes, and when. Blank, pre-encoded at the factory, or personalised with variable data are three different production paths and three different timelines.
We build against a defined chip reference and produce in 10 to 12 days from artwork approval, which only holds if point one is settled first.
The chip is half the answer
The other half is what the chip is sitting in. A fabric wristband, a Tyvek band, a silicone strap and a PVC, FSC wood or rPET conference badge all treat an inlay differently, and all age differently across a multi-day event.
If you already know what your readers speak, send us the reference and we will match it. If you do not, that is a normal place to start, and it is a shorter conversation than it sounds. There is more detail on formats and encoding in our FAQ, or write to hello@accesioid.com and we will work backwards from your gate.
YOU MAY ALSO LIKE
