NFC vs RFID: Board Design, Tags, and Reader Choices

Quick answer

• For phone-tap configuration or pairing, start with a connected or dynamic near-field communication (NFC) tag rather than making your board a reader.
• For badge access, use a secure high-frequency (HF) radio-frequency identification (RFID) reader-and-tag system.
• For inventorying many tags several meters away, investigate ultra-high-frequency (UHF) RFID.
• Animal identification requires standards-compliant low-frequency (LF) equipment with the correct duplex protocol, not just any LF reader.
• Counterfeit authentication calls for a cryptographic NFC tag plus backend provisioning and freshness checks, not a readable serial number.

The difference between NFC and RFID

RFID describes a family of radio identification systems, including LF, HF, and UHF technologies. NFC is a standardized HF contactless technology within the RFID family. For an NFC vs RFID board design, specify the intended application, carrier, protocol, operating role, antenna, and security model.

LF RFID is used in some existing credential systems and in animal identification. LF includes 125 kHz systems, illustrated by the EM4095 datasheet, Version 4.2 (22 April 2013). For animal ID, TI documents an ISO/IEC 11784/11785-compliant half-duplex (HDX) transponder with an activation carrier of 134.2 kHz, not exactly 134 kHz, in SCBS837 (October 2001). An animal-ID reader must support the tag's protocol, including HDX or full-duplex B (FDX-B), as well as the carrier frequency.

HF RFID uses 13.56 MHz. Relevant communication standards include ISO/IEC 14443 proximity and ISO/IEC 15693 vicinity technologies. NFC uses the same carrier and overlaps the HF standards: the NFC Forum technology overview identifies ISO/IEC 14443 A/B and ISO/IEC 15693 among its supported technologies. An HF tag can also be an NFC tag, but phone support depends on tag formatting, NFC Data Exchange Format (NDEF) records for content such as URLs, and the modes a phone exposes.

UHF inventory systems use regional Electronic Product Code (EPC) Gen2 / ISO/IEC 18000-63 bands to read many tagged items across larger areas. Select a legal channel plan for the deployment region because a radio's tuning range does not determine which frequencies are permitted. The ThingMagic Nano guide, Rev 09172018, documents regional configuration and protocol support.

LF, HF, NFC, and UHF RFID comparison

Table 1. RFID and NFC specifications for PCB design

Reading distance depends on the tag, antenna, reader, and surrounding materials. The UHF range below comes from one manufacturer's test setup and should not be used as a predicted range for a custom PCB.

Table notes: HF rate and carrier cells derive from DS10925 Rev 11, "RF communication". NFC carrier and rate derive from NT3H2111_2211 Rev 3.6.

The UHF range is the manufacturer's example in TM_Nano-UG Rev 09172018, p. 41, not a tested range for your PCB. EIRP means effective isotropic radiated power.

Choose LF RFID if…

• You must interoperate with an installed LF credential system.
• Animal identification specifies ISO 11784/11785 and a particular duplex mode.
• Phone access is unnecessary, or an external reader is acceptable.
• You can accommodate the coil and test reading distance with the intended tags and enclosure materials.
• Your firmware team can implement the selected decoder and validate real tags.

The LF front end below also needs animal-ID protocol firmware for HDX or FDX-B.

Choose HF RFID if…

• Your installed tags specify ISO/IEC 14443 or ISO/IEC 15693.
• You need controlled presentation rather than a wide inventory portal.
• Access control requires cryptographic credentials and managed reader keys.
• Your tag memory needs go beyond an immutable identifier.
• You can select reader firmware around the exact communication protocol, not just the carrier.

For phone compatibility, also specify the NFC tag type and NDEF message format so the intended app can read the tag.

Choose NFC if…

• A phone should configure the product with a tap.
• Pairing should deliver an address or commissioning token to an app.
• You want a dynamic tag connected to the host microcontroller (MCU).
• Field detection should trigger host wakeup or a configuration workflow.
• Authentication should use a cryptographic tag and a provisioned backend.

A pairing record provides an address or token for device discovery, but the app should authenticate the device before accepting commissioning commands. Protect such commands in the application protocol.

Choose UHF RFID if…

• Many moving items must be inventoried without individual presentation.
• The read zone extends beyond an intentional phone tap.
• You can use an external antenna and plan the antenna's polarization and coverage.
• Your supply and enclosure can support transmitting-reader operation.
• You can test tags on metal or liquid-filled products and configure the reader for the deployment region.

Validate missed tags, unintended reads, and reader interference under realistic inventory traffic.

Design considerations before capturing the schematic

Reader, passive tag, or connected tag?

The board role determines the required components:

• Reader: Generates the radio field, commands tags, and receives replies. A compatible phone can perform the NFC reader role.
• Passive tag: Harvests power from the reader's field and sends stored information.
• Connected or dynamic tag: Also exposes memory or transfer functions to the host MCU.

NXP NT3H2111W0FHKH, a connected NTAG I2C plus chip for phone interaction, provides optional password protection and configurable open-drain field detection, useful for synchronization or waking connected circuitry. Neither feature provides cryptographic product authentication.

Antenna inductance, tuning, matching, and Q

Measure a loop's equivalent inductance, resistance, and parasitic capacitance in the final mechanical assembly. The quality factor (Q) describes how sharply the loop resonates. Tune the resonance, then match the reader's driver and receiver paths for the measured loop. Capacitor values from a demo board may not suit a different antenna.

Excessive Q narrows bandwidth and affects modulation waveforms. AN11564 Rev 1.1, NXP's PN7120 antenna matching guide, explains the measurement-and-matching workflow. Its numerical targets apply to the PN7120 reader. Prefer C0G/NP0 capacitors in the RF tuning network: NXP's PN7160 guide AN13219 specifies that dielectric for matching capacitors.

Nearby metal also affects antenna tuning. Keep copper planes, batteries, mounting hardware, and metal enclosures away from an unshielded loop. Nearby metal changes inductance and loss through eddy currents. Ferrite can help, but it also changes the equivalent circuit: measure and tune with the ferrite installed, as AN11564 directs.

A UHF reader module instead connects to an antenna through a controlled RF transmission path. Use the chosen module's reference impedance and routing guidance. The PCB impedance control guide explains how the board stackup determines the required trace width.

Host interfaces and power

The host MCU communicates with the reader or connected tag.

The ST25R3916-AQET is an HF/NFC reader chip. It supports Serial Peripheral Interface (SPI) and Inter-Integrated Circuit (I2C). The interfaces share pins, and I2C_EN selects the active bus. The dynamic-tag examples use I2C, whereas the Nano reference uses a universal asynchronous receiver/transmitter (UART) (TM_Nano-UG Rev 09172018, p. 34).

Assign interrupts, interface selection, reset, and sleep controls during schematic planning. When using an ESP32 host, consult the ESP32 pinout guide before allocating bus signals and wake-capable GPIOs, then check the exact MCU datasheet.

Budget transmitting, listening, polling, and sleep states separately. A field-detection output can wake the host when a reader approaches without continuous software polling. For example, the ST25DV general-purpose output (GPO) can report field changes, RF activity, and transfer events. Energy harvesting from the NFC field depends on coupling and reader behavior and may not supply enough power for the host.

Memory, authentication, and phones

Tag memory and cryptographic authentication have different purposes.

Do not authorize an unlock from unique identifier (UID) equality or treat an NDEF URL as proof of authenticity. Older MIFARE Classic badges rely on Crypto1, a broken legacy cipher. NXP's current guidance directs security-relevant applications toward newer DESFire or Plus credential chips. Attacks on older cards are documented by Keysight's security analysis, 27 August 2024.

DESFire EV3, a secure HF credential chip for access control, supports cryptographic credential systems. For product authentication, NTAG 424 DNA supplies authenticated dynamic NFC messages. Both systems require non-default, diversified keys, protected backend secrets, and revocation and anti-replay behavior. A valid message authentication code alone does not tell the backend whether a previously accepted message is being reused. NXP's AN12653 Rev 1.1 discusses diversification, transaction counters, and backend fraud detection.

Phone NFC compatibility also depends on software. NDEF read/write and low-level tag access are different capabilities. Android's NFC documentation makes MIFARE Classic support optional, while Apple Core NFC requires supported hardware, appropriate sessions, and entitlements. Writable memory, app permissions, tag technology, and OS behavior all matter. Ordinary phone NFC hardware is not a native LF or UHF reader.

Minimal reference-circuit descriptions

The reference circuits below cover the required reader or tag IC, host, and antenna connections. They are schematic examples, not tested boards or final component values.

LF: coil front end and MCU decoder

For LF reader designs, use EM Microelectronic EM4095HMSO16B+ as a library-available LF front end. Follow EM4095 Version 4.2, "Typical Operating Configuration": antenna-driver outputs feed the resonant coil network, DEMOD_OUT and RDY/CLK reach MCU inputs, and MCU outputs control MOD and SHD. Include local supply decoupling and the documented demodulator network. Animal-ID duplex modes also require suitable protocol firmware.

HF: reader and tuned loop

For an HF credential reader, use STMicroelectronics ST25R3916-AQET, a host MCU, supply decoupling, the documented clock arrangement, and a tuned loop. Route RFO1/RFO2 through the driver matching network and implement the receiver paths at RFI1/RFI2. Connect the selected SPI or I2C interface plus interrupt/control signals to the MCU. Secure-credential software also requires authentication beyond RF transport.

NFC: phone-facing dynamic tag

For phone-tap configuration, use NXP NT3H2111W0FHKH for a Type 2 connected tag, with the antenna at its RF terminals, host I2C with suitable pull-ups, and host supply/decoupling. To notify the MCU of a phone tap, connect open-drain FD to an interrupt input with a pull-up to a compatible host logic rail, as shown in NT3H2111_2211 Rev 3.6, Figure 12. Optional energy harvesting takes power from the reader's field.

Alternatively, STMicroelectronics ST25DV04K-JFR8D3 is an ISO/IEC 15693 / NFC Forum Type 5 dynamic tag chip. Connect the antenna coil exclusively between AC0 and AC1. Add host I2C, the appropriate supplies, and GPO according to the selected package. Do not attach unrelated DC or AC paths to the antenna pins. ST marks the ST25DV04K family as not recommended for new designs.

UHF: reader-module carrier

For UHF inventory, the ThingMagic/JADAK M6E-NANO guide supplies a practical carrier-board reference: host UART, regulated supply with active-transmit margin, ENABLE control, and a matched RF feed to an external antenna. Start from its carrier drawing rather than an NFC loop.

BOM checklist

Include the reader/tag IC, antenna, C0G tuning passives, decoupling, clock components where required, interface/FD pull-ups, supplies, and a UHF RF connector where applicable. Check supply voltage, current capability, logic compatibility, and RF-component ratings against the exact device and antenna design. Do not invent margins or reuse untested reference values.

FAQ

Is NFC the same as RFID?

What is the difference between an NFC vs RFID tag?

UHF RFID vs NFC: which works for inventory?

125 kHz vs 13.56 MHz RFID: can one reader read both?

Can my phone read every RFID tag?

Is a dynamic NFC tag automatically secure?

Sources, library verification, and limitations

• ST25R3916-AQET, STMicroelectronics: DS12484 Rev 8 supports interfaces and RF connections.
• NT3H2111W0FHKH, NXP: NT3H2111_2211 Rev 3.6, 21 July 2023 supports carrier, rate, password, and FD claims.
• ST25DV04K-JFR8D3, STMicroelectronics: DS10925 Rev 11 supports RF rates and antenna connections. The family is currently NRND.
• EM4095HMSO16B+, EM Microelectronic: EM4095 Version 4.2, 22 April 2013, LF carrier and application topology.
• Additional manufacturer documents: TI SCBS837, October 2001, animal-ID carrier; ThingMagic TM_Nano-UG Rev 09172018, UART/carrier/range; NXP NT4H2421Gx Rev 3.0, 31 January 2019, cryptographic tag; MFDFLFEV3 REV0, 19 May 2020, DESFire security; AN11564 Rev 1.1, 18 April 2016, antenna/ferrite; AN13219, capacitor dielectric; AN12653 Rev 1.1, 5 May 2021, system security.

Scope note: LF/HF ranges and LF/UHF data rates vary by implementation. Actual PCB ranges and reference component values require testing with the chosen tags, antenna, and enclosure. The conceptual circuits are not tested hardware.

RFID operating bands, permitted radiated power, antenna restrictions, and exposure obligations depend on region. Plan emissions and product compliance testing with the finished antenna and enclosure. Using an ISM frequency or following a module carrier circuit does not certify the finished product.

For an NFC vs RFID board project, start a schematic in Flux and select the reader, tag, antenna, and host interface for the intended application.