NFC NTAG213 Cards: Encoding, Printing and Ordering Guide

time :2026-11-17 author :CBT scanning :

An NTAG213 card is the entry-level building block of many tap-to-anything programmes: business cards, review cards, event badges, product authentication labels, and simple access credentials. Its 144 bytes of user memory look small on a datasheet, and they are — which is exactly why the specification has to be planned before artwork is approved. This guide covers the decisions a buyer actually makes: chip tier, payload budget, encoding model, card construction, print and finish, read behaviour, failure modes, and order terms. For the chip's general features and applications, see our NTAG213 card overview.

1. What an NTAG213 Card Is, and Where It Fits

NTAG213 is an NXP chip family member compliant with NFC Forum Type 2 and ISO/IEC 14443 Type A. It operates at 13.56 MHz with a 106 kbit/s air interface, carries a factory-programmed 7-byte UID, and offers 144 bytes of user read/write memory inside a 180-byte EEPROM organised in 45 pages of four bytes.

That memory map matters in production, not only in design. Pages 0–2 hold the UID, internal data and static lock bytes; page 3 holds the capability container that declares how much NDEF space is available; pages 4–39 are user memory; pages 40–44 hold dynamic lock bytes, configuration, the 32-bit password and the password acknowledge value.

Where it fits: one payload per tap, read by a phone. Where it does not: multi-record business cards, stored images, offline databases, or anything that needs cryptography on the chip.

2. NTAG213 vs NTAG215 vs NTAG216: Choose by Payload, Not by Habit

The three chips share the same air interface, the same 7-byte UID, the same command set and the same phone compatibility. The difference is memory, and that is the whole decision.

ChipEEPROMUser memoryNDEF capacity after formattingSuitable payload
NTAG213180 bytes144 bytesAbout 137 bytesOne short URL, an ID, a single action
NTAG215540 bytes504 bytesAbout 496 bytesURL plus vCard, or several NDEF records
NTAG216924 bytes888 bytesAbout 872 bytesLong text, multi-record sets, larger media

A practical rule from production: choose by the payload you will need in year three, not the one you need at launch. Moving from 213 to 215 costs a little per card; moving a printed batch is a full reprint. If the plan includes a contact card with name, title, phone, email and links, NTAG215 is the honest starting point.

3. 144 Bytes in Practice: What an NDEF Record Actually Holds

The number buyers need is not 144 but roughly 130 characters of URL, because NDEF formatting consumes header bytes and the common prefixes are compressed into a single code.

  • A short link such as a landing page or a review page: fits with room to spare.
  • A link carrying a campaign parameter plus a serial number: fits if the URL stays compact.
  • A vCard with full contact details: does not fit; encode a redirect link instead.
  • Stored text in two languages: does not fit on 213; move to 215.

Two engineering notes: reserve bytes for the password feature if you plan to use it, and do not design to the last byte, because a future redirect change may need a longer URL than the original.

4. Which Devices Can Read It

Any NFC-enabled phone can read an NDEF-formatted NTAG213 card: Android devices with NFC, and iPhones from the model generations that added background tag reading. Desktop USB readers built for ISO/IEC 14443A work as well, which is what many encoding stations use.

  • iPhones read NDEF content without an app, but writing usually needs an app with the right entitlement.
  • Older Android devices and some low-cost readers may fail on tags with very small antennas.
  • Metal-backed phones and thick cases shift the coupling point; the tap position moves.

Test on the phones your users actually carry, not on the one on your desk. This is a frequent pilot failure.

5. NTAG213 vs MIFARE Classic: Memory Chip or Security Chip

These two are often compared for the wrong reason. NTAG213 is a data carrier with a light password feature; MIFARE Classic is a memory card with sector keys.

NTAG213MIFARE Classic 1K
Memory144 bytes user1 KB, 16 sectors
Typical useTap-to-URL, ID, simple actionLegacy access control, stored value
Security model32-bit password, lock bitsCrypto1 authentication, publicly broken
Phone-readableYes, NDEFYes, with app support

If the requirement is "a phone should open a link", NTAG213 is the right part. If the requirement is "a door should open only for this card", neither chip is a full answer — the reader and controller decide, and a cryptographic chip such as DESFire sits above both. Our MIFARE Ultralight article covers the neighbouring tier.

6. Password Protection, Lock Bits and UID Mirroring

Three features are frequently specified and frequently misunderstood.

  • 32-bit password (PWD/PACK): protects write access, or read access if configured that way. It stops casual rewriting by another phone; it does not encrypt the payload and does not stop a determined reader from reading open pages.
  • Static and dynamic lock bits: make specified pages read-only. This is irreversible — once locked, the page cannot be unlocked, so lock only after the final payload is verified.
  • UID ASCII mirror: appends the tag's 7-byte UID into the NDEF payload automatically, which is useful for serialised URLs without writing the UID into every record.

State clearly which of the three you need. "Password protected" on a purchase order can mean any of them.

7. Card Construction: PVC, Paper, Epoxy and Anti-Metal

FormatTypical buildSuitable for
Standard cardPVC, 0.76 mm, CR80Business cards, membership, events
Paper or stickerPaper face with inlay, adhesive backPosters, packaging, review stickers
Epoxy tagChip and antenna under resinKeyrings, harsh handling
Anti-metalFerrite layer between inlay and metalEquipment, metal furniture

The constraint that catches projects late is metal. An NTAG213 inlay placed directly on a metal surface detunes; the read range collapses. An anti-metal build adds a ferrite sheet, which costs more and adds thickness. Decide that at the sampling stage, because it changes the card structure, not only the artwork.

For stock formats and card builds, see RFID cards and blank cards.

8. Printing and Finish: What a Tap Card Needs on the Surface

A tap card is a printed product before it is an electronic one, and the finish affects read behaviour.

  • Offset litho handles fine detail and Pantone matching at volume.
  • Digital UV suits short runs and variable data, at a higher unit cost.
  • Silkscreen holds dense ink on dark stock, with coarser detail.
  • Soft-touch matt and frosted finishes look premium; heavy metallic foil over the antenna area can reduce read range.

Two production details matter more than the design: keep the antenna window free of foil or metallic ink, and keep the print registration stable so the "tap here" mark sits over the coil rather than beside it. Printed options are listed under printed cards.

9. Encoding Models: URL, vCard, Serialised ID

Four models cover many orders:

  1. Blank: the buyer encodes in-house, keeping the scheme private.
  2. URL written, same for all cards: a campaign or product page.
  3. Serialised URL or UID-mirrored records: each card is unique, usually shipped with a matching CSV.
  4. Structured NDEF with multiple records: for example a URL record plus a text record for the tenant name.

Encoding and printing must agree: the number printed on the card should be the number the reader returns. Ask for a read-back report for the production batch, not just for the sample. Where a password is used, agree the PWD and PACK values in writing and keep them out of email threads.

10. Read Range: Antenna Size, Phone Position and Interference

For a CR80 NTAG213 card, a realistic read distance with a phone is a few centimetres, commonly quoted as 2–10 cm depending on the reader and antenna. Smaller formats — a 30 mm sticker, a keyring tag — trade range for size.

Three factors move that number: the antenna area inside the card, the phone's coil position, and nearby metal. Thick phone cases, magnetic mounts, and a card kept in a wallet with other cards all reduce the working distance. The chip datasheet's operating temperature is −25 °C to 85 °C; a finished PVC card is limited by the PVC body, which softens well below that upper figure.

11. Where NTAG213 Cards Fail in the Field

  • Payload changed after lock: the page is read-only and cannot be rewritten; the card is scrap.
  • URL too long: the NDEF message does not fit and encoding fails at the station, often late in the run.
  • Metal underneath: the read range drops to a few millimetres, which reads as "defective tag" in the field.
  • Antenna cut by a slot or punch: intermittent reads, worst at the edge of range.
  • Print wear over the tap mark: users tap the wrong spot and report a "dead" card.
  • Password set but not documented: the next owner cannot update the card.

Each of these is a specification error rather than a chip defect, which is why the build sheet matters more than the datasheet.

12. MOQ, Sampling, Lead Time and Cost Structure

Cost is driven by four things: card construction, print method, encoding model, and quantity per design. Setup — plates, proofs, encoding profiles — is fixed per artwork, so unit price falls between a 500-piece and a 5,000-piece run.

A sequence that avoids reprints: approve the card build and chip on a physical sample, verify it on the target phones, confirm the NDEF payload length, then release bulk. CBT holds standard stock for 24-hour sampling, runs its own PVC sheet line, and publishes capacity and yield figures under capacity and quality.

13. FAQ: NTAG213 Card Questions Buyers Ask

Q1: How much data does an NTAG213 card hold?

144 bytes of user memory, of which about 137 bytes remain usable for an NDEF message — enough for a short URL or an ID, not for a full vCard.

Q2: Can an NTAG213 card be read by iPhone and Android?

Yes. Both read NDEF content natively; writing from a phone usually requires an app with the right permission.

Q3: Can I upgrade an NTAG213 card to NTAG215 later?

Not on the same card. The chip is fixed at production, so choose 215 or 216 at the sampling stage if the payload may grow.

Q4: Is NTAG213 secure enough for access control?

It suits low-risk, phone-tap scenarios. For doors, the reader and controller carry much of the security; high-value sites should use a cryptographic chip.

Q5: What does the 32-bit password actually protect?

Write access, or read access if configured that way, against casual rewriting. It does not encrypt the payload.

Q6: Can the card be locked so it cannot be changed?

Yes, using lock bits, and the change is irreversible. Lock only after the final payload has been verified on the target phones.

Q7: Will it work attached to metal?

Not directly. A standard inlay on metal detunes; an anti-metal build with a ferrite layer is required.

Q8: What is the typical read distance?

A few centimetres with a phone, commonly 2–10 cm, depending on antenna size, phone model and nearby metal.

Q9: Do you encode the URL before shipping?

Yes. Blank, uniform URL, serialised URL, or multi-record NDEF are all available, with a matching data file and a batch read-back report.

Q10: What is the minimum order?

Printed runs typically start in the hundreds to low thousands per design depending on print and encoding; blank stock can ship in smaller quantities.

14. Talk to Us Before You Lock the Payload

Send the intended payload, the target phone models, the card format and the quantity to info@chipbond.com, and our engineers will reply within one business day with a build sheet and a sample proposal — engineering answers rather than a template quotation.

CBT has manufactured RFID products since 1996, consumes 800 million chips a year, produces 1.5 million pieces a day at a 99.8% yield, and holds standard stock for 24-hour sampling. Two production bases, in China and Thailand, give you capacity redundancy in peak season, a legitimate alternative origin where Chinese-origin goods face extra duty, shorter logistics to your warehouse or port, and one IQC/QA standard across both plants.

Tell us the destination country and we will quote from whichever base gives you the better landed cost.

Popular
Posts
Recommend Products