nfc label capacity selected: from 144 to 800 bytes
Point 1: First, find out which chip is the 144/504/888 byte
The most used NFC tag chip in industry is the NTAG series of NXP, and three mainstream models correspond to user-usable spaces of 144 bytes (NTAG213), 504 bytes (NTAG215) and 888 bytes (NTAG216). These numbers refer to areas in the chips where data on NDF (NFC Data Exchange Forum, NFC Data Exchange format) can really be written, without UID, locking position, CC (Capability Container, Capable Packer) systems are distributed.
If the data exceeds this range, such as a longer vCard, a combination of Wi-Fi setup data and device credentials, or a direct H5 page link with a token, you generally need to move up to NTAG I²C (1 KB+) or ST25 (2–4 KB). The unit price is about twice as high. Most projects therefore choose between 144 and 888 bytes.
Element 2: Dissociate NDEF content from bytes
Many candidates have a capacity to slap their heads, like "144 for each URL should be enough." But the NDEF has to have format costs, each record with a type, length, payload structure, plus an external message TLV (Tag-Length-Value, Type-Long-value) envelope, which actually allows space to be smaller than the nominal. Here are some of the general uses of common content:
- Short URL only (e.g., https://t.co/xxxx): 30-50 bytes
- Long URL (with token and redirect parameters): 80-150 bytes
- WiFi web-based records (SSID+ password+encrypt): 60-100 bytes
- Basic vCard (name + phone + mailbox): 150-300 bytes
- Full vCard (with company, address, header URL): 400-700 bytes
- Smart Poster (URL with title + action): 120-200 bytes
We had a smart-housewich network project that thought it was enough to write a WiFi 50-bit file, and then we added the MQTT server address, the device MAC, the equipment certificate summary, which ran to 210-bit, 144-file NTAG213 was not plugged in, and finally it was put into 504.
Point 3: set aside 20 to 30% of the balance, not to be capped
The label chip is labelled as a physical limit, and several losses are considered when actually writing:
- The capability container (CC) occupies exactly 4 bytes on NTAG213, NTAG215, and NTAG216.
- NDEF message TLV tops 1-3 bytes
- Total head of each record (MB, ME, CF, SR, TNF, TYPE_LEN, PAYLOAD_LEN) 3-10 bytes
- If you want to add a record later (e.g. write URLs and sign them) then leave dozens more bytes.
Experience values are estimated at 70% of the nominal value for available space, 144 sets of NDF content that actually stabilizes is about 100 bytes, 504s about 350 bytes, 888s about 620 bytes. With URL Token, signed trace records, encrypted documents such as possibly iterative content, prioritize higher one to be more secure.
Element 4: Read-and-write frequency and lock-in strategy influence final selection
If the label is one-time, lifelong only (e.g., anti-false traceability, marketing jumps), it can be smaller and 144 bytes sufficient to cover savings.
If the tags need to be grafted repeatedly (e.g., shift of posts, loan of equipment, temporary voucher issuance), the number of plasters in NTAG213 is marked at 100,000, 215/216 equals 100,000, which is generally sufficient. But if writing is particularly high (for example, dozens of times a day), it is recommended to go straight to the top, so that you don't write down some Page at the end of the day and make it readable as a whole -- because NDEF is stored on an ongoing basis, and the middle one is draging all the contents behind.
NTAG213, NTAG215, and NTAG216 all have lock settings with 32-bit password protection. Locking a tag immediately after writing (set PWD_AUTH) prevents later rewriting but also takes away room for updates. With redirect tags for marketing campaigns, if shoppers need to see different content after a tag is locked, new tags must be issued. The 888-byte tier is typically chosen in that case to allow room for expansion.
Point 5: Scan by scene, don't be blind.
The demand for label capacity varies widely from operation to operation, with the following recommended types of several common scenarios:
| scene | Typical data volume | Recommended Model |
|---|---|---|
| Micro-Credit Scheme Short Chain | 30-60 bytes | NTAG213(144) |
| Product trace H5 page URL+ batch number | 80-150 bytes | NTAG213(144) |
| WiFi Net+Equitation Certificate | 150-350 bytes | NTAG215(504) |
| Full electronic business card vCard | 300–700 bytes | NTAG216(888) |
| Iot pair with signature certificate | 400-800 bytes | NTAG216(888) |
The price gap is considerable: NTAG 213, naked, approximately 0.4-0.6 yuan/s, NTAG 215 at 0.9-1.2 and NTAG216 at $1.5-2.0 (2024 domestic channel reference price, significant amount). One million orders, possibly hundreds of thousands to millions more per one set, are better costed than "a little bit larger" on the basis of choice.
Point 6: Read-and-write distance and cell phone compatibility before the next order
The right size is only the first step, and there are several practical problems to verify when small quantities of test production:
- The reading distance varies widely from NFC antennas to iPhone 7-14, usually 3-5 cm, and the Android type is 5-10 cm.
- The big-volume label (888 bytes) sometimes results in certain old types not identifying the full NDF
- Metal surface labelling requires labels with a magnetosphere or a tablet of iron oxygen, otherwise the capacity is too large to read.
- The compatibility of the writing tools is also tested, such as ACR122U, NFC Tools Pro, and the different levels of support for password protection and locking by the manufacturer's own App.
Shanghai-based Cheeky Way Technologies, when they label their customers with NFC, usually uses 50 to 100 samples to do a physical test, and then all target models are tested over and over again, and then the single production is confirmed, so that "capacity selections are avoided."
Summary: an optional list
- Count NDEF content by character length, plus TLV and record header costs.
- Inverse slotting required by 70 per cent of nominal value
- If you change it repeatedly or need a password lock, leave a balance.
- Compare unit prices and volume size to avoid paying for unusable space
- Small batch tests to re-formulate after delivery, covering mainstream machines of more than 3 paragraphs
This process generally works for selecting tags from 144 to 888 bytes. If your project needs a special NDEF structure or compatibility with both ISO 14443 and ISO 15693, spend extra time defining the data format or review it with a supplier experienced in NFC tag mass production.

Ms. Lei
Mr. Pang