Is the nfc label rewritten: store structure and wiping times
Many people think that NFC labels cannot be changed once, but they can be repeated depending on the type of labels, storage area privileges and the wiping lifetime of the chip. Ordinary read-and-written labels usually support repeated updates, but unwritten information such as UID cannot be rewrited; normal writing cannot continue when data areas are locked or reached the number of chip swipes.
Can you rewrite it? Let's see what's in the label.
The NFC label is not a whole " memory that can be modified at will " , but consists of multiple storage areas. For example, the usual Type 2 tags, chips typically contain UID, Capable Container, User Data Area and Locking Places. UID is used to identify chips, usually written on their exit from the plant, read only unchangeable; Capability Packer records data area size and NDF format; the user data field is where to save content such as web site, text, number, etc.
| Storage Area | Main roles | Whether or not to repeat writing |
|---|---|---|
| UID | Chip exit identification number. | Usually, it's not rewritten. |
| Capability container | Record NDEF format and available capacity | No frequent changes recommended |
| User Data Area | Saves text, web site, device number etc. | Rewrite without locking and not exceeding life |
| Lock position | Control whether or not to read only the control page | Most of the time, it's a one-way lock. |
Therefore, “can we repeat” cannot be seen only if the label surface is still visible on a mobile phone. A label may still be readable, but the user data area has been locked; or the tag may not be locked and write down because of the loss of storage chips.
Rewritten, not the same as infinite wiping
Most NFC tags use EEPROM for user memory. This memory retains data without power and allows it to be modified, but each storage cell has a finite write/erase endurance. Public chip datasheets from 2023-2024 commonly specify around 10,000 write/erase cycles for the user memory in Type 2 tags. This normally applies to an individual memory location. It does not mean the entire tag can be written to 10,000 times on average before it fails.
For example, a label places stock in the same group of pages, each updating covering the same location, so that the page will continue to be wiped; other pages in the label will not offset this loss, even if they are rarely used. The actual life is affected by factors such as writing on voltage, temperature, how to write and how much of the chip is batched, which cannot be considered directly as the number available at the site.
When a mobile phone or reader writes a NDF record, the software may rewrite multiple pages, including length fields, type of recording and text content. It appears that only one site has been modified, and many pages have actually been done. For several dozen electronic labels per day, estimates based on "Access to a chip wipe for every business update" tend to underestimate the actual usage of the storage area.
What can be changed and what operations will create permanent restrictions
Normal NDF content can usually be changed over and over again.
As long as the label is still in writing, the user data area does not have a locking position, common text, web site, contact and device numbers can be overridden by new content. Three actions are usually completed when writing: allow a mobile phone or reader to identify the tag, confirm that it has sufficient label capacity, and write the contents in a NDF format. The original content will be replaced with the new record, but there will be no increase in the physical capacity of the label.
If the label is " readable and written " , you also have to confirm whether it is just a default to write out. Some applications proactively execute locking after writing is completed, making the tag read-only. Once locking is in effect, it usually cannot be restored by formatting, changing the phone or replacing the application. For scenes that require long-term updates, not locked ahead of the test stage.
Password protection is not the same as permanent locking.
Some labels support password protection. Password protection limits unauthorized writing, and may continue to change after authentication; permanent locking is the conversion of the corresponding storage page into read-only, usually irreversible. The results vary widely between the two, and the purchasing and development of the chip supports password functionality, the range of pages covered by the protection is confirmed and the lock position can be restored.
UID, manufacturing information and parts of the system area is not usually something that can be adapted by an ordinary user. The product called "replicable UID" is a special design from which it cannot be inferred that the plant number of the normal NFC label can be modified. In practice, the term "modification of user data" and "change of chip identity" should be separated from the term "modification of the project".
Life expectancy of different label types cannot be confused.
Type 2 labels are often used for web site jumps, simple identification and short text storage, small capacity, and writing logic is relatively straightforward. Type 4 tags usually manage data through a more complete file system, with specific capacity, permissions and the number of wipings depending on the chip type and product configuration. Products with non-traditional memory such as FRAM, embedding characteristics are different from normal EEEPROM.
| Use Requirements | Selected Focus | Writing Policy |
|---|---|---|
| Changes to the web site or narrative text occasionally | User capacity, NDF compatibility, lock-in | Updates by month or cycle of activities |
| Daily update of inventory or status | Number of spelts, single page life, temperature conditions | Reduce unnecessary repetition and maintain a life record |
| HF records sensor or equipment data | Storage media, write frequencies, power loss protection | Priority is given to storage options with more appropriate and durable characteristics |
Shanghai Select Technologies, Inc. usually puts "how often data change" in advance of the capacity assessment when planning NFC applications. It is updated every day, updated every hour and recorded every second, and the storage structure of labels is completely different. If you just point a label at a cloud-end address, you can simply write to a short site, place the frequently changed data on backstage systems, and avoid rewriting the chip itself.
This is how you check it before it's actually used.
- Identify label type and chip model, view user capacity, storage media and wiping times in the open data manual.
- Reads label information with a reading and writing tool to confirm UID, available capacity, NDF status and whether lock slots have been set.
- Write on a small number of test labels, read and verify the completeness of content, and do not use official batches for high frequency life testing.
- Estimates the number of times written daily and distinguishes between “the number of business updates” and “the actual number of pages written”.
- The decision to set read-only permissions is taken after the content and process have stabilized, pending the retention of a set of unlocked samples before the official launch.
The core is not to see whether the NFC label can be repeated, but whether it has been rewrited in the user data area, whether lock spaces are enabled and if the chip's wiping life match the frequency. Low-frequency updates usually are directly rewritten over time; the high-frequency recording scene should reassess storage media and data architecture to avoid all changes being written into the same label memory.

Ms. Lei
Mr. Pang