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.
Product selection · 7 catalog options
HF RFID & NFC Readers: USB, Network & OEM Selection
This reader catalog focuses on HF and NFC hardware for identifier input, card writing, networked stations and embedded development. Choose the required card operation before the connector. Several original Digital Logic µFR models are legacy products, so identify the hardware and firmware for replacements and review current-generation alternatives for new projects.
Explore the range
RFID Readers: model information and sample checks
µFR Nano NFC Reader Writer
Digital Logic’s µFR Nano is a compact 13.56 MHz reader/writer with an 86 × 27 × 8 mm enclosed format. Compare the enclosure, OEM and UART board versions for…
µFR Nano Online — Legacy NFC Reader
µFR Nano Online is Digital Logic’s legacy 13.56 MHz reader with Wi-Fi and BLE plus USB/UART interfaces. The manufacturer places this model in its EOL…
µFR XL OEM NFC Reader with RF Booster
µFR XL OEM is a 178 × 178 × 5 mm, 100 g reader board from Digital Logic. Its larger antenna and RF booster provide a published operating-distance reference…
µFR Classic CS NFC Reader Writer
The µFR Classic CS is an 86 × 54 × 9 mm enclosed USB NFC reader/writer from Digital Logic. Its 84 × 50 × 5 mm OEM variant provides a smaller board outline…
JustID NFC USB Identifier Reader
JustID is Digital Logic’s NFC identifier reader for workflows that send a tag ID to a host application. It supports ISO 14443 A/B and ISO 15693 at 13.56…
NFC Integrino N512 Development Module
Digital Logic’s NFC Integrino N512 is a 51.3 × 23.9 × 20 mm, 26 g development module using Arduino technology. It combines 13.56 MHz NFC with a programmable…
From shortlist to sample
Describe what your application must read or write
Send the chip, required operation, host environment and any existing hardware revision. We can review an evaluation configuration and the model-specific supply and integration requirements.
Include these details
- Exact card or tag chip, protocol and the operation your application must perform; use authorized non-sensitive test data.
- Host OS and architecture, application environment and required driver, API, HID or virtual-COM behavior.
- Current hardware revision, firmware and connector if replacing an installed reader; include enclosure and power constraints.
- Evaluation quantity, rollout quantity, integration deadline, destination and any revision-specific documentation requirements.
Buying questions
What to confirm before you order.
Use the selected model’s information and an agreed sample test for the final decision.
Do I need an NFC UID reader or a reader-writer?
Use an identifier reader when the application only needs a card ID in a defined input format. Use a reader-writer when you need an implemented command to read or change card memory or application data. JustID is an identifier-input starting point; verify a separate writer and its software for NDEF or application programming.
Do the readers listed here support UHF inventory tags?
The reviewed catalog here is HF and NFC hardware. A passive UHF EPC Gen2 inventory or laundry tag needs a compatible UHF reader and application setup; an HF desktop unit is not a substitute. For a UHF request, specify region, antenna arrangement and checkpoint requirements for a separate hardware proposal.
Are the original µFR models suitable for a new project?
Digital Logic labels the original µFR and µFR Online families as legacy. For an existing installation, record the current hardware, firmware and API dependency before reviewing replacement supply. For a new project, compare the manufacturer's current generation and confirm the complete integration; do not assume identical software or connectors.
Will the reader work with my operating system or controller?
Confirm the exact model, interface, driver or library, OS version and architecture. Keyboard emulation, virtual COM and vendor APIs impose different application requirements. A list of SDK platforms or available connector types is not proof that every model supports every host or card operation.
Does reading a card UID prove that the access application will work?
No. Identifier output and application authentication are different operations. The authorized system operator must approve the credential, data format, personalization and application commands. Test the intended operation on the actual reader, firmware and host software without sending live master keys or account passwords in an inquiry.
How are evaluation units and rollout timing confirmed?
Request the exact model and revision, sample-card operation and evaluation quantity. Availability, unit cost, software scope, documentation and shipping are confirmed in the quote; legacy supply needs an explicit check. Agree acceptance and rollout quantities after the evaluation rather than using tag or card MOQs for hardware.
Continue your selection
Related buying guides
Reader-writer integration guide
Define the chip, card command and host application before selecting hardware.
JustID identifier input
Review identifier output and the limits of a UID reader.
Digital Logic reader families
Manufacturer directory identifying original µFR families as legacy and listing current-generation options.
Evaluation planning and charges
Confirm the offered reader and its evaluation terms before shipment.