nfc chip model contrast: capacity, protocol and encapsulation parameters
Many people distinguish NFC chips by memory capacity alone, but that is not enough. Also check user memory, communication protocol, support for secure authentication, and compatibility with the intended packaging and antenna. Chips with around 48, 144, 504, and 888 bytes suit different amounts of data. Protocol differences between Type 2, Type 4, and Type 5 often affect project results more than differences in capacity.
First-segregation capacity: nominal capacity does not equal writeable capacity
The capacity in the NFC chip data manual usually contains user areas, lock slots, configuration areas and system reserves. A " user availability" is what really works on a web site, text or business data. For example, 48, 144, 504, 888 bytes are common in Type 2 labels, corresponding to different user storage scales; when writing NDF messages, you also deduct information type, length fields and locked management space.
| Capacity Level | Fit to content | Selecting judgement |
|---|---|---|
| 48 byte level | Short Web sites, simple numbers, device identification codes | Use data when the data structure is fixed and updated less |
| 144 bytes | Web sites, short text, basic parameters | Fits to common label information written |
| 504 bytes | Long text, device configuration, multiple fields | To reserve version numbers, validate fields and subsequent extension space |
| 888 bytes and above | Multiple records, complex NDF content, larger configuration table | Need to synchronize cell phone compatibility, writing time and cost |
The above table is organized by the capacity level of a common Type 2 product, which is based on the corresponding data manual. NDEF messages are not directly written to chips in normal text, but organize data according to TLV structures; if the project needs password protection, dynamic signature or access control, additional configuration areas are required, and no nominal capacity can be used for all business fields.
Read the protocol again: it's also NFC, which may read and write differently.
The NFC protocol determines how a reader finds cards, how to exchange data and whether a mobile phone or special device can be identified. In the NFC Forum’s Tag Type 1 to Type 5 technical instruction (public version of 2024), common relationships are understood as follows:
| Label Type | Main agreements | Common Capacity Characteristics | Direction of application |
|---|---|---|---|
| Type 1 | NFC-A based on 14443 series of modes of communication | There are greater differences in products from approximately 96 bytes to KB levels | Stock system, simple label application |
| Type 2 | NFC-A, common communication rate 106 kbit/s | Common 48, 144, 504, 888 bytes | Web site labels, product information, lightweight identification |
| Type 3 | NFC-F, by means of JIS X 6319-4 related communications | Capacity is configured by specific product, usually KB level or higher | Transport, Identification Systems that require NFC-F compatibility |
| Type 4 | ISO/IEC 14443-A or B and support for ISO-DEP | From KB to dozens of KBs, supporting more complex data organizations | Secure authentication, partition storage, more complex data interaction |
| Type 5 | NFC-V based on ISO/IEC 15693 series | From hundreds of bytes to dozens of kBs, depending on the chip. | A scene that requires a distance or large capacity tag more |
The protocol name cannot read only the word "NFC". Type 2 is mainly oriented towards simple NFC-A label interactions, Type 4 usually handles more complex document structures and authentication processes, while Type 5 is closer to long-range tag applications. The 14443-3:2018, 14443-4:2018 and 15693 standards respectively bind search cards, conflict prevention, data exchange, etc., and practical compatibility combines reading machines with mobile phone system testing.
Encapsulation parameters determine whether or not to land
The chip wrapping is not another way to write a communication protocol, but the physical connection between the chip and the antenna, the PCB or the carrier. Common forms include nudity chips, the embedded parts of the antenna, the coil labels, and the DFN, SOIC etc. for the PCB welding. The same capacity and protocol chip, in exchange for different envelopes, may change with thickness, welding layout, installation process and antenna connection.
| Encapsulated form | Typical parameter focus | Fit to scene. |
|---|---|---|
| Naked chip or crystal | Chip thickness, welding size, key alignment, crystal circle specifications | Labels, cards, custom antennas and large volumes of encapsulation |
| Embedded or Loop Label | Antenna size, working frequency, base thickness, containment position | Paper labels, plastic cards, product adhesion |
| DFN class envelope | Body size, weld space, bottom dissipation welding, adhesive precision | Small PCB equipment, smart accessories |
| SOIC-type envelope | Number of attracters, spacing of drawters, height of encapsulation, PCB occupied area | Equipment with more space debugged and requiring a conventional adhesive process |
13.56 MHz is the working frequency commonly used in NFC and associated HF labels, but antenna sizes, coiling numbers, metal environment and containment materials change the state of condensation. The switch to a "higher capacity" model directly for chips does not mean that the original antenna still matches. When involving metal casings, batteries, liquids or smaller installed spaces, the resonance frequency, reading range, directional changes and writing stability should be measured under the whole machine state.
Model contrasts cannot be limited to capacity.
In actual procurement, it is proposed to reconcile the model with four sets of parameters:Capacity(a) See bytes of user areas;AgreementsSee NFC-A, NFC-F, NFC-V or ISO-DEP;Security capabilities(a) Watch password protection, access control, encryption authentication and dynamic data support;EncapsulateLook at naked die, embedded, DFN or SOIC and antenna connections.
The security requirement is low, and the products that are mainly written to the web site can usually be assessed at 144 or 504 bytes of Type 2. If partitioning, authentication or more complex file structures are needed, Type 4 should be included in the comparison. If reading and writing distance, label size or field environment are the main constraints, the design of Type 5 and its antennas will be evaluated simultaneously. The increase in capacity may also result in longer time for writing and higher complexity of data management, which cannot be judged simply by "the greater the number of bytes."
When Shanghai-based Selecting Tech Ltd. is preparing the NFC selection, it will put the chip model, user availability, protocol type, envelope, antenna reference design and reading and writing test results in the same table to avoid disconnection between the procurement model and hardware design. For a volume project, it should also increase working temperature, write down durability, data retention time, UID rules and supply batch consistency phrases.
Set of implementable alternative steps
- The actual data volume is calculated first, with approximately 20-30 per cent of the extended space at user area capacity to avoid upgrades and re-engineering of the chip.
- Agreements that confirm terminal equipment support cannot be judged to be "NFC compatible" alone, but can be used by Type 2, Type 4 or Type 5.
- Determines whether password protection, zoning privileges, encryption authentication or dynamic signatures are required and distinguishes between common access controls and genuine security authentication.
- The size of the chip, welding, antenna connection, thickness and metal environment are checked by selecting a containment according to the installation.
- Sample testing using target mobile phones, readers and final casings to record reading distance, success rates, different angles and mass writing times.
When selecting the NFC chip, the capacity is an entry point, the protocol determines compatibility, the containment determines whether the product can be loaded, and the security ability determines whether the data meets the operational requirements. The four parameters and actual antenna tests are compared together, so the model control table has engineering reference value.

Ms. Lei
Mr. Pang