HomeGuidestechnicalHow Dynamic QR Codes Work: Redirects, Scan Tracking and Reliability Explained
technical

How Dynamic QR Codes Work: Redirects, Scan Tracking and Reliability Explained

A technical but readable explanation of what happens between a scan and a web page with a dynamic QR code: short links, HTTP and client-side redirects, scan counting, privacy, failure points, and how to check where a dynamic code leads.

Updated Oct 30, 2026
Advertisement

Dynamic QR codes are often described as "QR codes you can edit after printing." That's true, but it hides what's actually going on. Once you understand the mechanism, which is mostly ordinary web redirects, it becomes much easier to judge which service to trust, why a code might fail, what data gets collected, and how to check where a code really goes.

The Printed Code Never Changes

The squares on a printed QR code can't change. A QR code is a way of writing text (usually a web address) in a pattern that cameras can read. Whatever text was encoded at printing time is what every phone will read, forever.

So how can a dynamic code be "edited"? By encoding an address that doesn't host your content, but forwards visitors to it. The forwarding rule is stored on a server, and that's what you change.

For example, a dynamic code might encode:

https://qr-helper.com/r/AbC123

On the QR service's side, a database record says something like "code AbC123 currently goes to https://example.com/spring-menu." Change the record to https://example.com/summer-menu, and the next scan goes there instead.

Step by Step: What Happens When Someone Scans

  1. The camera decodes the pattern. The phone reads the text and, recognizing a web address, offers to open it. Most phones show a preview of the domain at this point: the QR service's domain, not your final destination.
  2. The browser requests the short link. The phone's browser connects to the QR service's server over HTTPS.
  3. The service looks up the code. It finds the record for that code ID and checks that it exists and is active.
  4. The scan is recorded (on most services). Typically a timestamp and some technical details about the request.
  5. The browser is sent onward to the destination using a redirect.
  6. The destination page loads. From here, it's just a normal website visit.

All of this usually takes well under a second on a decent connection.

Types of Redirects

There's more than one way to forward a browser, and the choice affects speed and behaviour.

Server-side HTTP redirects

The server replies with a status code such as 301 (moved permanently) or 302 / 307 (temporary) and a Location header pointing to the destination. The browser follows it immediately, before downloading any page.

  • 301 tells browsers and search engines the move is permanent; browsers may cache it, which is a problem for a code you might change later. Dynamic QR services generally prefer temporary redirects for this reason.
  • 302 and 307 say "go here for now," so each scan checks with the server again. That's what makes editing work reliably.

Client-side redirects

Alternatively, the server sends a small web page that runs a script, or uses a meta-refresh tag, to send the browser onward. This is slightly slower, because the page has to load first, but it lets the service run in a purely static hosting environment, and it can show a brief message such as "Redirecting…".

QR Helper uses a client-side approach: the /r/ page loads, looks up the code in our database, records the scan, and then replaces the current page with the destination so that the back button doesn't bounce people back to the redirect.

Interstitial pages

Some services show an intermediate page, sometimes with advertising, before sending people on. This is common on free tiers of some generators. It's slower and can look suspicious to scanners. If you're choosing a service, test a code and see exactly what scanners experience.

How Scan Counting Works

Because every scan passes through the service, it can count them. What's recorded varies a lot between services. Common fields include:

  • Time of the scan.
  • User agent: a string the browser sends describing the browser and operating system, which allows rough breakdowns by device type.
  • Referrer: where the request came from, often empty for QR scans.
  • IP address, from which approximate location can be estimated. Some services store this; others don't.

Things to know about scan counts:

  • They count requests, not people. One person scanning twice is two scans. Link previews and security scanners that fetch links automatically can add extra requests on some services.
  • Some scans aren't counted. If a browser blocks scripts, or if the scan request fails partway, a client-side counter may miss it.
  • Approximate location is approximate. IP-based location is often only accurate to the city or region, and mobile networks can be far off.

For transparency, here's what QR Helper stores per scan of a dynamic code: the timestamp, the browser's user-agent string (trimmed), and the referrer if any. We don't store names, IP addresses or precise locations in scan records. Our privacy policy has the full details.

Where Dynamic Codes Can Fail

Understanding the chain makes it easy to see the failure points:

Failure point What scanners see Fix
Service down or offline Page won't load or times out Wait, or move to a more reliable service
Plan or trial ended "Inactive" or upgrade page Reactivate or replace; see what happens when a dynamic code expires
Code paused or deleted "Not found" or "inactive" message Reactivate in your dashboard, or recreate
Destination removed Error on the destination site Update the destination
Scanner has no data connection Nothing loads Nothing to fix; static codes for Wi-Fi or contacts don't need data
Account compromised Code leads somewhere you didn't choose Secure the account, reset the destination

That last row is worth emphasising. Whoever controls the account controls where every printed copy of the code goes. Use a strong, unique password and keep account access limited to people who need it.

Security: Dynamic Codes and Scams

Dynamic codes aren't inherently dangerous, but their structure has two side effects that scammers exploit:

  1. The visible domain isn't the destination. When a phone previews a short link, scanners can't tell where they'll end up. Scammers use short links and redirect chains for the same reason: to hide the final address.
  2. The destination can change after the code is checked. A code that led to a harmless page yesterday could lead somewhere else today.

As a scanner, you can protect yourself by checking where a code leads before opening it. QR Helper's QR code checker shows the encoded content, and our guide to seeing where a QR code goes before scanning explains the techniques. As a business, you can help customers trust your codes by printing your brand and the destination address near them, and by checking regularly that no one has stuck a fake code over yours. See protecting your business QR codes from tampering.

Can You Make Your Own Dynamic Code?

Yes, and for businesses with a website it's often the most robust approach. Two ways:

  • A redirect on your own domain. Create a short address like yourbusiness.com/go/menu and configure your website or hosting to redirect it to wherever you want. Encode that address in a static QR code. You can change the redirect at any time, and the code never depends on a third party.
  • A page you update. Point a static code at a page you own, then change the page's content when needed.

You give up built-in scan counts unless your website analytics records visits to that address, which most do.

Choosing a Dynamic QR Service

Questions worth asking:

  • What happens to codes if I stop paying? Some services deactivate them; QR Helper Pro codes keep working after a downgrade.
  • Is there an expiry or scan cap?
  • What scan data is stored, and for how long?
  • Is there an interstitial or ad page?
  • Can I export my codes and destinations?
  • Does the service use HTTPS for short links? All modern services should.

For a broader comparison, read static vs dynamic QR codes.

Frequently Asked Questions

Does a dynamic code make scanning slower? Slightly, because there's an extra step. On a normal mobile connection, it's usually not noticeable.

Can I change a dynamic code from a link to Wi-Fi details? No. Dynamic codes only forward web addresses. Wi-Fi, contact cards and similar data must be encoded directly as static codes.

Will Google or other search engines index my short link? Generally not in any meaningful way. What matters for search is your destination page.

Is a dynamic code more secure than a static one? Neither is inherently more secure. Dynamic codes add a dependency and an account to protect; static codes can't be changed if something goes wrong.

Advertisement