惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Stack Overflow Blog
Stack Overflow Blog
L
LangChain Blog
人人都是产品经理
人人都是产品经理
酷 壳 – CoolShell
酷 壳 – CoolShell
T
Tailwind CSS Blog
N
Netflix TechBlog - Medium
Microsoft Security Blog
Microsoft Security Blog
J
Java Code Geeks
博客园 - 【当耐特】
量子位
有赞技术团队
有赞技术团队
Jina AI
Jina AI
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
博客园_首页
C
Check Point Blog
B
Blog RSS Feed
M
MIT News - Artificial intelligence
H
Help Net Security
雷峰网
雷峰网
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
博客园 - 聂微东
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
A
About on SuperTechFans
腾讯CDC

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Why QR Codes Expire (It's Not the Code — It's the Server)
Nacho Gonzál · 2026-05-11 · via DEV Community

Nacho González

Most explanations of QR code expiration say "your subscription expired" as if that's the full story. It's not. QR codes don't expire — the redirect infrastructure that dynamic codes depend on gets switched off, and every scan after that moment hits a dead server instead of your content.

Here's how it works at the architecture level, and why it matters if you're building anything that touches physical print.

Static vs dynamic: two completely different architectures

A static QR code encodes your destination URL directly into the pixel pattern using the ISO/IEC 18004 standard. No server, no lookup, no dependency. Scan it and the camera decodes the URL from the image itself. It will keep working as long as the physical print is readable and the destination URL is live.

A dynamic QR code encodes a short URL owned by the QR platform — something like qrtg.io/abc123. The camera sends an HTTP GET to that short URL. The platform's redirect server looks up where abc123 maps to and returns a 302 to your real destination.

Scan → GET https://qrtg.io/abc123 → 302 → https://yoursite.com/landing-page

Enter fullscreen mode Exit fullscreen mode

That redirect server is what expires. The QR image never changes. The infrastructure behind it does.

The four ways the redirect stops working

1. Subscription cancellation

Payment fails or you cancel → platform downgrades your account → redirect server stops responding for your codes. On most platforms this is instant. No grace period. A billing failure at 2 AM means codes are dead before your staff shows up at 8 AM.

2. Trial end

You created codes during a 30-day evaluation. Didn't convert. Codes created during the trial deactivate on day 31. If you printed those codes before deciding not to subscribe, the materials are already broken.

3. Scan cap hit

Free tiers usually cap dynamic codes by scan count. As of April 2026:

  • QR Tiger free: 500 total scans per code
  • Flowcode free: 2 active codes, 500-scan analytics limit

Hit the cap and the redirect returns an error, even if your account is fully active. The counterintuitive part: a high-traffic QR code burns through its cap faster. Success triggers failure.

4. Platform shutdown

The redirect domain goes offline permanently. Every QR code that ever pointed at platform.io/r/... is unrecoverable. The QR code industry saw real consolidation in 2023–2024 — smaller platforms shut down or got acquired, and physical materials printed with those platforms' short URLs became permanently dead.

Why this is a harder problem than it looks

The subscription cycle and the physical materials lifecycle operate on completely different timescales.

A business prints 10,000 product boxes with a QR code. The boxes have an 18-month shelf life. Annual subscription renews fine the first year. Card gets updated, auto-renewal misses, subscription lapses six months before the last box ships.

Every box still on shelves now has a broken QR code. No one on the vendor's side knows. The platform sends no notification. The brand finds out when a customer mentions it.

Our support ticket data at QR Nova shows the average gap between a dynamic code going offline and the owner finding out via a customer report is 4 days. That's 4 days of scans hitting error pages for a product that's physically present and being handled by end users.

The silent failure mode is the real problem. When a code dies:

  • The scanner gets a generic 404 Not Found or a platform error page
  • No message saying "this QR code is deactivated"
  • The user assumes their phone has a bug, or the product is broken
  • The brand takes the hit invisibly

What actually matters when choosing a QR platform for print

If you're embedding QR codes in anything physical — packaging, signage, product inserts, printed menus — the most important question isn't "what features do you offer." It's:

What happens to my codes if I cancel tomorrow?

A platform that immediately deactivates all dynamic codes on subscription change is a liability for print use cases. A platform with a grace period or permanent code retention is not.

Other things worth checking:

  • Scan cap alerts — does the platform email you before you hit the cap, or after?
  • Custom redirect domain — if you can point your own domain at the redirect service, you can migrate platforms without reprinting anything
  • Export options — can you get your redirect rules out if the platform shuts down?
  • Operating history — a platform that's been running for several years with a clear business model is meaningfully less likely to disappear than a well-funded startup with no obvious revenue

The architectural choice that avoids the problem

For any destination that won't change, skip dynamic codes entirely. Static QR codes have no server dependency. The URL is baked into the image. There's nothing to cancel.

For destinations that need to be editable — campaign URLs, seasonal redirects — dynamic codes are necessary, but the redirect service itself doesn't have to be gated by billing state. That's an architectural choice platforms make, not a technical necessity.

At QR Nova, we built the redirect service so codes stay active regardless of billing status. The redirect lookup is not coupled to account state. It's a simpler system to operate and it removes the liability for anyone printing QR codes on anything physical.

Static codes are free with no account required. Dynamic codes keep working after you close the tab.


Originally published on QR Nova