Name: QR for Agent
Author: QR for Agent

Most QR code generators give you static codes. You scan them, they work. But if you need to change where they point, you’re stuck. The URL is baked into the QR code matrix itself, so changing the destination means generating a new image and replacing it everywhere.

If you’re building software that uses QR codes, this creates problems fast. Dynamic QR codes fix this by using a redirect. The QR code points to a short URL that you control, and that URL redirects to whatever destination you want. Change the destination server-side, and every printed code instantly points somewhere new.

What is a Static QR Code?

A static QR code encodes data directly into its matrix pattern. When you generate a QR code for “https://example.com/page”, that exact URL becomes part of the dots and squares you see.

Static QR Code → Encodes "https://example.com/page" → Scans to that exact URL

This works fine for permanent content. Business cards, product packaging, museum exhibits. The data never needs to change, so there’s no problem.

But here’s what you can’t do with static codes:

Change the encoded data after generating the image
Track scan counts, locations, or device types
Test different landing pages with the same printed code
Fix broken links after you’ve printed 10,000 flyers

That last one has killed more than a few marketing campaigns.

What is a Dynamic QR Code?

A dynamic QR code encodes a short redirect URL instead of your final destination. When someone scans it, they hit your redirect service first, which sends them to the actual target URL.

Dynamic QR Code → Encodes "https://qr.link/abc123" → Redirects to current destination

The QR code image stays the same forever. You update the destination through an API or dashboard, and all existing codes immediately point to the new URL.

This gives you:

Destination updates without regenerating images
Scan analytics (time, location, device, referrer)
A/B testing by rotating destinations
Link expiration with automatic fallbacks
Conditional routing (iOS to App Store, Android to Play Store)

Key Differences

Feature	Static QR Code	Dynamic QR Code
Data encoding	Final destination in matrix	Short redirect URL in matrix
Editable destination	No	Yes
Scan tracking	No	Yes
Works offline	Yes	Requires internet for redirect
File size	Smaller (less data)	Slightly larger
Best for	Permanent content	Marketing, apps, events

The offline thing matters in specific cases. Static QR codes work without internet because all data is in the code itself. Dynamic codes need a network request to resolve the redirect. For marketing and product development, this tradeoff is almost always worth it.

Why Developers Choose Dynamic

If you’re generating QR codes programmatically, static codes create technical debt. Every time a destination changes, you have to regenerate the image, update your database, notify users, and hope they replace the old code.

Dynamic codes skip all of that. The code becomes an addressable resource with a stable ID. You update the destination via API, and every printed code works with the new URL immediately.

I’ve seen this solve problems in:

Event platforms where venue details change after tickets print
E-commerce where product URLs shift with inventory
Real estate where yard signs get reused across listings
Restaurant menus where specials update weekly
Campaigns where broken links need emergency fixes

How to Create a Dynamic QR Code with an API

Dashboard tools work fine for one-off codes, but they don’t scale. You need programmatic access.

Here’s how to create a dynamic QR code with QR for Agent:

curl -X POST https://api.qrforagent.com/api/qr \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "url",
    "data": {
      "url": "https://example.com/promo"
    },
    "options": {
      "dynamic": true,
      "name": "Spring Sale Campaign",
      "style": {
        "dotShape": "rounded",
        "gradient": {
          "type": "linear",
          "colors": ["#667eea", "#764ba2"]
        }
      }
    }
  }'

Response:

{
  "id": "qr_abc123xyz",
  "shortUrl": "https://qr.link/abc123",
  "imageUrl": "https://cdn.qrforagent.com/abc123.png",
  "destination": "https://example.com/promo",
  "scans": 0,
  "createdAt": "2026-03-03T10:00:00Z"
}

The shortUrl is what gets encoded in the QR code matrix. To update the destination later:

curl -X PATCH https://api.qrforagent.com/api/qr/qr_abc123xyz \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "data": {
      "url": "https://example.com/summer-sale"
    }
  }'

Same QR code image. New destination. Every scan resolves to the updated URL.

When to Use Static vs Dynamic

Use static QR codes when:

The destination will never change (Wikipedia articles, historical markers)
You need offline functionality (museum exhibits without WiFi)
You’re encoding non-URL data that’s inherently static (WiFi credentials, vCards)
Cost or infrastructure makes dynamic codes impractical

Use dynamic QR codes when:

You might need to update the destination later
You need scan analytics
You’re building software that generates codes programmatically
You want to test different landing pages

If you’re writing code that generates QR codes, start with dynamic unless you have a specific reason to go static. The flexibility is worth the redirect overhead.

Getting Started

QR for Agent gives you both static and dynamic QR code generation through one API. The free tier includes 10 dynamic codes and 1,000 scans per month, which is enough to prototype and test before you scale.

Every QR code type (URL, vCard, WiFi, event) supports both modes. Just set "dynamic": true in the options object.

Create your first dynamic QR code in under 5 minutes. No credit card required.

Dynamic vs Static QR Codes: What's the Difference?