The short answer
No, QR codes are not dead — they are past the hype cycle and quietly settled into infrastructure. The post-pandemic doom claims (“QR codes are over”, “nobody scans them anymore”) were the usual backlash that follows any technology that gets over-exposed in a single year. The actual data tells the opposite story: scan volume kept climbing after the pandemic peak, every modern phone scans QR codes natively without an app, and the use cases that stuck (menus, payments, packaging, reviews, WiFi, business cards) are now ordinary. The honest outlook is that QRs stopped being exciting and started being plumbing — which is the most durable kind of technology.
What changed is not the code — the 1994 spec still scans today, unchanged — but how it is used. The visible shift is from one-off static codes (a printed link that never changes) to dynamic codes that store a short redirect link on a server, which makes the destination editable and the scans countable. Around that mechanic sit the newer integrations: wallet and pass-style payments, AR anchors, and the analytics dashboards that turn a printed square into a measurable channel. Our qr code history guide covers the origin, and the static vs dynamic QR guide covers the mechanic that drives most of the change.
The “QR is dead” misconception
The “QR codes are dead” narrative arrives every couple of years, usually after a hype spike. In 2020 contactless menus, payments, and tickets flooded every surface, and when the world partially reopened some of those codes went stale or unused — which got reported as “the fad is over.” That conflates two things: a few badly-deployed pandemic codes going stale, and the underlying format. The format did not go anywhere. It is an open ISO standard, royalty-free since 1994, that any phone camera reads natively with no app to install. A free, universal, hardware-free bridge from physical to digital does not die just because a handful of 2020 menus rotted.
The reliable signal is not the news cycle but the device base and the behaviour. iOS 11 (2017) added native camera QR scanning, Google Lens did the same on Android, and once every phone in a pocket could scan with no app, the friction dropped to zero — and stayed there. The behaviour that picked up in 2020 (point a phone at a square, get an action) did not reverse after the pandemic; it normalised. Our how to scan a QR code guide covers the device side, and the do QR codes expire guide explains why a printed code going stale is a destination problem, not a format problem.
What actually changed
Three shifts, none of which are about the printed square itself. First, the static-to-dynamic shift: a dynamic code prints only a short redirect link and keeps the real destination on a server, which means you can change where a printed code points without reprinting it, and every scan gets logged. That is the single biggest structural change in the QR world since 1994, and it is the thing that turns a one-off print into a managed channel. Our dynamic QR code guide covers the mechanism and qr code tracking covers what gets measured.
Second, the money layer. QR payments moved from a niche to a mainstream rails in several regions (UPI in India, Alipay and WeChat Pay in China, Pix in Brazil, wallet-based transfers elsewhere), so the same printed square increasingly triggers a payment rather than just a web page. Third, the AR and content layer: codes anchor physical objects to digital overlays, packaging links to instruction videos, and posters link to interactive experiences. None of these change the QR spec — they all just change the destination behind a scannable link. The code stays the boring, reliable constant.
What didn’t change — the 1994 code still scans
The defining evidence that QR is infrastructure, not a fad, is backwards compatibility. A code printed in 1994 scans on a phone made in 2025 with zero migration, format conversion, or “legacy support.” The spec is fixed: three finder patterns, a data grid, Reed-Solomon error correction, eight masks. Nothing about the format has been deprecated, forked into incompatible dialects, or moved behind a licence. A static code is still a self-contained printed string that the phone decodes locally with no server in the loop — the property that makes it free, private, and immortal, covered in our what is a QR code guide and our how does a QR code work guide.
That backwards compatibility is the real answer to “will QR codes last.” A technology where every artifact ever made keeps working, on hardware everyone already carries, with no platform owner that can deprecate it, is not a trend — it is a standard. The risk to longevity is never the format; it is the destination (a URL moves, a domain lapses) or, for dynamic codes, the redirect server. That is a link-rot problem, not a QR problem, and it is the subject of our do QR codes expire guide.
The honest outlook: infrastructure, not a fad
Predicting “the future of QR codes” is mostly a category error. QRs are not a product with a roadmap or a company with a pivot; they are an open standard for putting a machine-readable link on a physical surface. Asking whether QRs will still be around is closer to asking whether printed URLs or barcodes will still be around. The honest outlook is that the visible surface (a square on a menu, a sticker, a card) will keep being ordinary, the underlying mechanic will keep quietly gaining capability (dynamic redirects, analytics, payments, AR anchors), and the failure modes will stay the same ones they have always been — link rot, low contrast, and badly-sized prints, all covered in our common QR code mistakes guide.
The part that will genuinely evolve is the dynamic layer, not the code. Short redirect links behind printed squares will get more measurable, more editable, and more routable (A/B, device-based, geo-based), and the analytics will get more privacy-aware as regulation tightens. The static code — the free, offline, immortal default — will keep doing exactly what it does today, because there is nothing to improve about a printed string that scans forever. Our qr code tracking and qr code analytics guides cover where the dynamic layer is heading.
Where QR use is heading — a glance
A summary of what is settled (infrastructure) versus what is still moving (the dynamic layer and the integrations around it). The left column is the durable baseline; the right column is where the actual change happens.
| Area | Settled / static | Still moving / dynamic |
|---|---|---|
| The format itself | Fixed ISO spec since 1994; every old code still scans. | Not changing — backwards compatibility is a feature. |
| Device support | Native camera scan on iOS 11+ and Android, no app needed. | Done — friction is at zero and will stay there. |
| Static codes | Free, offline, immortal; the safe default for anything permanent. | No roadmap needed — a printed string that scans forever. |
| Destination management | Static: reprint to change, baked into the ink. | Dynamic: editable redirect on a server you control. |
| Measurement | Static: zero analytics by construction. | Dynamic: scan counts, coarse geo, device, time-of-day dashboards. |
| Payments & passes | Printed QR triggering a wallet/P2P transfer in many regions. | Expanding rails and standardisation, still region-fragmented. |
| AR & content anchors | A code linking a physical object to a digital overlay. | Use cases growing; the code is just the entry point. |
| Failure modes | Link rot, low contrast, bad sizing, glossy surfaces. | New risk for dynamic: the redirect server as a single point of failure. |
How QRForge is positioned
QRForge ships the durable baseline for free: self-contained static codes that work forever with no server, no subscription, and no provider to outlive. Every content type (URL, text, WiFi, vCard, SMS, email, event), full styling (gradients, per-eye and per-module shapes, centered logo with level H, frames), and vector SVG / EPS plus PNG export — the things that do not change and that nobody should have to pay for. The free decode helper confirms any exported image round-trips to the exact payload before you print, and the qr best practices guide keeps the scannability bar high.
The part that is still moving — editable destinations and scan analytics — is the planned paid dynamic tier, built on the same redirect mechanic described in our qr code redirect guide and measured as in our qr code tracking guide. The deliberate sequencing is the honest one: prove the static placement first (free, forever, no lock-in), then step up to dynamic only when editability or measurement is the actual lever — never as a default, because a dynamic code is a dependency that can break every printed copy at once if the server lapses. The future of QR is more capability behind the square, with the square itself staying exactly as boring and reliable as it has been since 1994.
Frequently asked questions
Are QR codes dead in 2026?
No. The “QR is dead” narrative is the usual post-hype backlash. Scan volume kept climbing after the 2020 pandemic peak, every modern phone scans QR codes natively with no app, and the use cases that stuck (menus, payments, packaging, WiFi, reviews, business cards) are now ordinary. QRs settled from a trend into infrastructure, which is the most durable state for a technology.
What is the future of QR codes?
The printed square stays the same — the 1994 spec still scans unchanged. What evolves is the layer behind it: dynamic redirects that make a printed destination editable, scan analytics dashboards, QR-triggered payments, and AR anchors. The static, free, offline code keeps doing what it does; the dynamic layer is where capability gets added.
Will QR codes last?
Yes, because they are an open ISO standard, royalty-free since 1994, that every phone camera reads with no app and no platform owner. A code printed in 1994 scans on a phone made in 2025 with zero migration. The only thing that can “expire” a QR is the destination moving or, for dynamic codes, the redirect server going down — a link-rot problem, not a format problem.
What changed about QR codes after the pandemic?
The biggest structural change is the static-to-dynamic shift: instead of baking the destination into the printed code, a dynamic code prints only a short redirect link and keeps the real destination on a server, so it is editable after printing and every scan is countable. Around that mechanic sit newer integrations — wallet payments, AR anchors, analytics dashboards. The code itself did not change; how it is used did.