QR Codes vs NFC Tags: Which One Should You Actually Use?

What a QR code is versus what an NFC tag is

A QR code is not a physical object — it's a pattern of black and white squares that encodes text. Anyone with a printer can put one on paper, plastic, glass, fabric or metal, because it's ink or etching, not electronics. There's no battery, no chip, no manufacturing cost beyond whatever you're printing it on. A phone camera reads the pattern optically, the same way it reads a barcode, just with more data capacity and built-in error correction.

An NFC tag is a physical component: a tiny chip (usually from the NTAG21x family) bonded to a coil of copper wire, sealed into a sticker, card, or embedded into a keychain or plastic disc. It stores data in onboard memory and communicates with a phone over a short-range radio field when the two are held close together — there's no camera, no line of sight needed, and no ambient light requirement.

The practical distinction: QR codes are free to reproduce infinitely (a design file), while NFC tags are a physical good that has to be purchased, individually programmed, and physically affixed to every surface you want to activate. That single fact drives almost every other trade-off in this comparison.

Cost per unit: pennies versus tens of cents

A QR code generated with a free browser tool like QRPixel costs nothing beyond the ink and paper (or vinyl, or laser-etching) it's printed on. Print a thousand table tents with a QR code and the QR itself adds zero incremental cost — you were printing the table tent anyway.

NFC tags are bought as physical inventory. Blank NTAG213 stickers in bulk (500-1000 units) typically run somewhere in the range of 8-25 cents each depending on size, adhesive quality and memory capacity; small branded NFC cards or coins cost more, often $0.50-$3 each in low volumes. On top of the sticker cost, someone has to program each tag with an NFC writer app or a bulk encoding service before it's usable, which adds labor time that a QR code never requires — you just export the PNG.

For a hundred restaurant tables, that's the difference between a free PDF you print at home and a purchase order with a lead time, a minimum order quantity, and a programming step. For a single business card or a one-off event, the gap narrows, but it never disappears.

Read range and how each one gets scanned

QR codes work at a distance — anywhere from a few centimeters up to several meters for a large-format code, as long as there's enough light and the phone's camera can focus. This makes them usable on billboards, storefront windows, bus-stop posters and other surfaces the user never touches.

NFC only works at a range of roughly 0-4cm; realistically the phone has to be nearly touching the tag. That rules out any application where the target audience is more than an arm's length away — a poster on a wall, a banner, a shop window facing the street. NFC is a deliberate, close-contact action: someone has to walk up and tap.

This makes the two genuinely complementary rather than competing in most physical retail and hospitality settings — a QR code catches people from across the room, an NFC tag serves the person already standing right there.

iOS and Android behave differently with both technologies

For QR codes, every iPhone since iOS 11 and every modern Android phone can scan directly from the native camera app — no separate scanner app is needed, and this has been true long enough that 'download an app to scan this' is no longer a reasonable ask of a customer.

NFC support is less uniform. iPhones from the XS onward can read NFC tags just by holding the phone near them, with the read triggering a system notification without opening any app — but this 'background tag reading' only works when the phone screen is unlocked or actively being used, and some older iPhones (XR and earlier NFC implementations) require opening the Control Center's NFC scanner or a third-party app.

Android NFC support varies more by manufacturer: most Android phones with NFC turned on will detect a tag and prompt an action automatically, but the setting is occasionally toggled off by default or buried in settings, and some budget Android devices ship without an NFC chip at all. QR scanning has no equivalent hardware gap — every camera works.

Durability: printed surfaces versus embedded chips

A printed QR code degrades the way any print degrades — fading in direct sun, peeling if laminated poorly, scratching on a high-touch surface like a table. Laminating it or using UV-resistant ink solves most of these problems cheaply, and even a partially damaged QR code often still scans thanks to Reed-Solomon error correction covering up to 30% of the pattern.

NFC tags are more physically robust once installed — the chip itself has no moving parts and isn't affected by fading, glare or dirt covering it, since it doesn't rely on optical reading. However, NFC has a specific weakness: metal surfaces detune the antenna coil and can block the tag from working entirely unless it's a metal-rated tag with a ferrite shielding layer, which costs more. Standard NFC stickers slapped directly onto a stainless steel counter or an aluminum sign often fail intermittently or not at all.

Liquids and humidity affect both, but differently. A laminated QR code shrugs off spills. An NFC tag's adhesive can fail in high-humidity environments over months, and repeated exposure to commercial dishwashing (for a reusable table tent with an embedded tag, for example) can eventually corrode contacts on cheaper tags.

Changing what the code or tag points to later

A QR code generated with QRPixel encodes whatever text or URL you gave it directly into the pattern — it's static and can't be edited after printing. If you need to update where it points without reprinting, you need a dynamic QR service that redirects through a short link you can retarget later. QRPixel itself is a free, browser-only generator with no accounts and no tracking, so any QR you make with it points straight to your content with no redirect layer in between — perfect when the destination is stable, less convenient when you expect to change it often.

NFC tags are rewritable at the hardware level (most NTAG213/215/216 chips can be reprogrammed hundreds of thousands of times with any NFC-writing phone app), so in principle you can change what a physical tag does without replacing it. In practice, most small businesses never touch a deployed tag again after installation, because reprogramming means physically visiting every tag with a phone and a writer app — there's no remote update.

Neither technology gives you free, no-effort content updates. QR codes require reprinting (cheap, fast); NFC tags require physical re-tapping with a writer (no reprint cost, but manual labor per tag).

What actually fits on each one

A QR code can hold up to about 4,296 alphanumeric characters at the lowest error-correction level, though anything encoding more than a couple hundred characters becomes visually dense and harder to scan reliably — in practice, most real-world QR codes just encode a short URL and let the destination page hold the real content.

NFC tags store far less: an NTAG213 holds 144 usable bytes, an NTAG215 holds 504 bytes, and an NTAG216 holds 888 bytes. That's enough for a short URL, a Bluetooth pairing handoff, a vCard's core fields, or a small text payload — not enough for anything content-rich. Most commercial NFC deployments simply store a URL on the tag and, like a QR code, rely on the linked page for the actual content.

Restaurant scenario: menus, ordering and payment

For a printed menu at every table, a QR code wins decisively on cost and reach — a hundred tables need a hundred printed table tents you're already producing, and the QR adds nothing to that print run. Diners can scan from across the table without picking anything up, and it works identically whether they have an iPhone or an Android phone.

NFC becomes attractive at the point of payment or for a 'call the waiter' tap-to-order style interaction where a single dedicated unit (like a small NFC disc bolted near the till) gets tapped repeatedly by staff or return customers rather than printed fresh for every table. It's a better fit for a fixed, durable touchpoint than for disposable print collateral.

Museum and exhibit scenario: information plaques

Museums increasingly use QR codes on exhibit plaques because visitors can scan from a comfortable, non-contact distance without touching a shared surface — relevant both for hygiene and for protecting fragile display cases from wear. A large QR printed at a readable size also works for visitors who can't get close due to crowding or accessibility barriers.

NFC has a role in interactive exhibits where a visitor is meant to physically engage with an object — a tap-to-hear-audio-guide feature embedded in a handrail or a hands-on kiosk — but it's a poor fit for a plaque mounted behind glass or roped off, since visitors physically can't get within the required few centimeters.

Accessibility: which one works better for which visitors

QR codes require the visitor to aim a camera, get the frame in focus, and often read a small on-screen preview before tapping through — a real barrier for users with low vision or limited fine motor control, and QR codes carry no inherent audio or haptic feedback.

NFC's tap gesture is arguably more accessible for users with visual impairments, since there's no need to aim a camera or read anything on-screen — many phones give an audible or haptic confirmation on a successful tap, and screen-reader users can navigate the resulting page normally once it opens. For a public space serving a broad accessibility need, offering both isn't redundant — it's genuinely inclusive design.

When to use both together instead of choosing one

The strongest deployments don't pick a side — they use QR for reach and NFC for convenience at the exact point of interaction, both pointing to the same destination. A product package might carry a printed QR code for shelf browsing and warehouse scanning, while a companion NFC tag inside the retail box lets a customer who already has the product in hand tap for setup instructions without hunting for a camera angle.

A conference badge is a common example: a QR code printed on the badge lets any attendee's phone scan it from a normal handshake distance for a quick LinkedIn-style connection, while an embedded NFC chip lets exhibitors with dedicated NFC readers capture the same contact details instantly at a booth. Same underlying data, two different physical interaction models serving two different moments.

The decision isn't really QR versus NFC in the abstract — it's about matching the interaction distance and hardware cost tolerance of your specific touchpoint. Printed, disposable, distance-readable surfaces lean QR. Fixed, durable, close-contact touchpoints where you're willing to buy hardware lean NFC.

Getting started without buying anything

If your use case involves printed material at any distance — menus, posters, packaging, business cards, event signage — a QR code is the lower-friction, lower-cost starting point, and you can be testing one in under a minute with a free browser-based generator like QRPixel: no signup, no app install, no tracking, and no per-unit hardware cost to budget for.

Save NFC for the specific moments where a tap genuinely beats a scan: a fixed payment terminal, a reusable interactive kiosk, or a product already in someone's hand. Buying and programming tags is a real, recurring line item, so it's worth confirming the interaction pattern actually needs contact-range tapping before committing budget to hardware a QR code could have handled for free.

Frequently asked questions