In UHF RFID tag specifications, you'll often see the "TID Memory" field, such as "EPC 96 bits + TID 96 bits + User 512 bits". For purchasing personnel new to RFID, TID can easily be confused with EPC. In reality, they serve different purposes: EPC is typically used to identify the item to which the tag is attached, while TID is used to identify the RFID chip or the tag itself.
What Does TID Memory Contain?
TID is an abbreviation for Tag Identification, belonging to Memory Bank 10 of UHF RFID Gen2 tags. According to the structure of EPC Gen2/ISO 18000-63, TID must at least contain information capable of identifying the chip type and related tag capabilities; the actual chip may also contain manufacturer-assigned model information, a unique serial number, and extended tag identification data. The number of TID bits that a specific chip can provide is determined by the chip manufacturer and the specific model.
Therefore, TID 96 bits, TID 128 bits, or other capacities in the specification sheet do not mean that these spaces can be freely written to by the customer like User Memory. The main function of TID is to describe and identify the tag itself; its content is usually determined during the chip manufacturing stage and is permanently locked.
TID Memory vs. EPC Memory
The simplest way to understand TID is to compare it with EPC. EPC identifies the tagged object; TID identifies the tag itself. For example, a box of products has a UHF RFID tag attached. The company can write the product number, logistics code, or asset number into the EPC, allowing the software system to find the corresponding product record through the EPC. The TID, however, comes from the RFID chip itself and exists during the tag manufacturing stage, used to identify this specific tag chip.
This means that even if two tags are written into the same EPC, their TIDs may still be different.
| Memory | Main Purpose | Typically Controlled By |
|---|---|---|
| Reserved | Kill / Access Password | Tag manufacturer / system |
| EPC | Identify the tagged object | User / system integrator |
| TID | Identify the RFID tag and chip | Chip manufacturer |
| User | Store additional application data | User / system |
This distinction is crucial in RFID system design. If the business system requires an asset number that can be re-encoded according to company rules, an EPC should generally be used, rather than treating the TID as a programmable business field.
Can TID Memory Be Changed?
Generally not. The design purpose of a TID dictates that it shouldn't be a data area that users can repeatedly modify. A TID describes a fixed characteristic of the RFID tag itself, and therefore is typically written by the tag manufacturer during the production stage and permanently locked.
This is one reason why TIDs are valuable in certain RFID anti-counterfeiting and tag authenticity verification scenarios. Companies can associate a tag's TID with the EPC, product serial number, or backend database records. When a tag is read, if the EPC appears normal, but the TID doesn't match the original production record, it can reveal issues such as tag replacement, duplication, or abnormal coding.
However, a TID alone cannot be equated with "anti-counterfeiting functionality." The ability to establish a reliable RFID authentication mechanism also depends on chip security features, access control, encryption authentication, and the design of the backend database.
Why Is TID Important in RFID Applications?
In typical inventory management, the system may only care about the EPC, so operators rarely read the TID directly. However, in high-value asset management, RFID tag lifecycle management, product anti-counterfeiting, supply chain traceability, and tag quality control, TID can provide additional tag-level identity information.
For example, RFID tag manufacturers can record the TID of each chip at the time of manufacture and establish a correspondence between TID + EPC + Product ID during the tag initialization phase. During subsequent inventory checks or identity verification, the system can not only confirm "what this product number is," but also "whether the currently used RFID tag is still the original one."







